date:20150309

This bug was fixed in the package init-system-helpers - 1.22ubuntu4

---
init-system-helpers (1.22ubuntu4) vivid; urgency=medium

  * init: Switch preferred alternative to systemd, and update package
description to make sense for Ubuntu. (LP: #1427654)
 -- Martin PittSun, 08 Mar 2015 12:26:24 +0100

** Changed in: init-system-helpers (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 Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Vivid:
  Fix Released
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 1429734] [NEW] invoke-rc.d ignores dependencies in degraded mode

Public bug reported:

Our CI test VMs often start in degraded mode as jobs like systemd-
modules-load.service commonly fail. This causes invoke-rc.d to start
services with --job-mode=ignore-dependencies, which causes e. g.
openvswitch-nonetwork to not start up.

We need to relax that to allow degraded mode, too.

** Affects: sysvinit (Ubuntu)
 Importance: High
 Assignee: Martin Pitt (pitti)
 Status: In Progress

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

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

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

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

Title:
  invoke-rc.d ignores dependencies in degraded mode

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  Our CI test VMs often start in degraded mode as jobs like systemd-
  modules-load.service commonly fail. This causes invoke-rc.d to start
  services with --job-mode=ignore-dependencies, which causes e. g.
  openvswitch-nonetwork to not start up.

  We need to relax that to allow degraded mode, too.

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

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

[Touch-packages] [Bug 1416186] Re: Periodically loss of backlight control

2015-03-09 Thread Jonathan Brier

The behavior is the lighting control works upon initial boot, but after
leaving the computer on for multiple hours at some point the backlight
ceases to respond and backlight controls are never regained until a
shutdown or reboot of the system. I haven't tracked the exact pattern of
actions that cause this. The on screen indicator shows the graphic of
the dimming, but the actual behavior of reducing brightness does not
function upon key press.

I noticed when the backlight was lost the following is added to dmesg,
but I don't know how long before or after the loss that this message
appeared:

[ 9231.171766] usb 5-1: USB disconnect, device number 4
[11481.272220] perf interrupt took too long (2515 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5
[20859.513041] atkbd serio0: Unknown key pressed (translated set 2, code 0xab 
on isa0060/serio0).
[20859.513049] atkbd serio0: Use 'setkeycodes e02b ' to make it known.
[20859.533404] atkbd serio0: Unknown key released (translated set 2, code 0xab 
on isa0060/serio0).
[20859.533413] atkbd serio0: Use 'setkeycodes e02b ' to make it known.
[20859.832244] atkbd serio0: Unknown key pressed (translated set 2, code 0xab 
on isa0060/serio0).
[20859.832253] atkbd serio0: Use 'setkeycodes e02b ' to make it known.

Each press of the brightness key results in additional "atkbd serio0:
Unknown key pressed (translated set 2, code 0xab on isa0060/serio0)"
values to be added to dmesg.  May be related to resuming control after
the screen goes blank after inactivity or other activity while idle?

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

Title:
  Periodically loss of backlight control

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Periodically there is a loss of control of the backlight control where
  trying to brighten the screen or dim it with the keyboard controls
  does not function and remains in its current state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 21:05:25 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:198a]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] 
[1002:6600] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-01-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015)
  MachineType: Hewlett-Packard HP ENVY TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed 
root=UUID=1cc26cb0-3476-4abf-a12e-acac53ba8537 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 198A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.14
  dmi.chassis.asset.tag: 5CG32129MN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd11/06/2014:svnHewlett-Packard:pnHPENVYTS15NotebookPC:pvr088810305B032:rvnHewlett-Packard:rn198A:rvrKBCVersion03.14:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY TS 15 Notebook PC
  dmi.product.version: 088810305B032
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 20:59:15 2015
  xserver.configfile: default
  xserver.erro

[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work

2015-03-09 Thread Anthony Wong

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => walimis (walimis)

** Changed in: linux (Ubuntu Trusty)
 Assignee: walimis (walimis) => Liming Wang (wangliming)

** Changed in: xserver-xorg-input-synaptics (Ubuntu Trusty)
 Assignee: (unassigned) => Liming Wang (wangliming)

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

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

** Changed in: xserver-xorg-input-synaptics (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: hwe-next
   Status: Confirmed => In Progress

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

Title:
  [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  In Progress
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New
Status in libinput source package in Trusty:
  New
Status in linux source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  New
Status in xserver-xorg-input-synaptics source package in Trusty:
  Confirmed
Status in libinput source package in Utopic:
  New
Status in linux source package in Utopic:
  New
Status in systemd source package in Utopic:
  New
Status in xserver-xorg-input-synaptics source package in Utopic:
  New

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions

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

[Touch-packages] [Bug 1429736] Re: upstart crashed with SIGSEGV

2015-03-09 Thread Apport retracing service

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

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 #1419393, 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/1429736/+attachment/4338538/+files/CoreDump.gz

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

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

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

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

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

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

** 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 upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1429736

Title:
  upstart crashed with SIGSEGV

Status in upstart package in Ubuntu:
  New

Bug description:
  after rebooting, popups this error

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: upstart-bin 1.13.2-0ubuntu9
  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: Thu Mar  5 13:57:05 2015
  ExecutablePath: /sbin/upstart
  InstallationDate: Installed on 2015-03-03 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150224)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=c8ac14f5-b6c9-4080-9eaf-b50a94e3a591 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x104d0:   mov%edi,0x18(%esi)
   PC (0x000104d0) not located in a known VMA region (needed executable region)!
   source "%edi" ok
   destination "0x18(%esi)" (0x404a) not located in a known VMA region 
(needed writable region)!
   Stack pointer not within stack segment
  SegvReason:
   executing unknown VMA
   writing NULL VMA
  Signal: 11
  SourcePackage: upstart
  Stacktrace:
   #0  0x000104d0 in ?? ()
   No symbol table info available.
   #1  0x0001012d in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame inner to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  Title: upstart crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups:
   
  modified.conffile..etc.console.setup.compose.ISO.8859.1.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.13.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.14.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.15.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.2.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.3.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.4.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.7.inc: [modified]
  modified.conffile..etc.console.setup.compose.ISO.8859.9.inc: [modified]
  modified.conffile..etc.console.setup.compose.VISCII.inc: [modified]
  modified.conffile..etc.console.setup.remap.inc: [modified]
  mtime.conffile..etc.console.setup.compose.ISO.8859.1.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.13.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.14.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.15.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.2.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.3.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.4.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.7.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.ISO.8859.9.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.console.setup.compose.VISCII.inc: 2015-03-03T20:32:59
  mtime.conffile..etc.consol

[Touch-packages] [Bug 1429734] Re: invoke-rc.d ignores dependencies in degraded mode

** Tags added: systemd-boot

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

Title:
  invoke-rc.d ignores dependencies in degraded mode

Status in sysvinit package in Ubuntu:
  In Progress

Bug description:
  Our CI test VMs often start in degraded mode as jobs like systemd-
  modules-load.service commonly fail. This causes invoke-rc.d to start
  services with --job-mode=ignore-dependencies, which causes e. g.
  openvswitch-nonetwork to not start up.

  We need to relax that to allow degraded mode, too.

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

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

[Touch-packages] [Bug 1429734] Re: invoke-rc.d ignores dependencies in degraded mode

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

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

Title:
  invoke-rc.d ignores dependencies in degraded mode

Status in sysvinit package in Ubuntu:
  Fix Committed

Bug description:
  Our CI test VMs often start in degraded mode as jobs like systemd-
  modules-load.service commonly fail. This causes invoke-rc.d to start
  services with --job-mode=ignore-dependencies, which causes e. g.
  openvswitch-nonetwork to not start up.

  We need to relax that to allow degraded mode, too.

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

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

[Touch-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd

It is in place, this is working fine here and for other people. After a
suspend/resume cycle, can you please run

  journalctl -b -u NetworkManager > /tmp/nm.log

and attach /tmp/nm.log here?

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

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

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 601555] Re: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.

2015-03-09 Thread Tomas Pospisek

Hello Alan,

first, thanks for caring about this bug. Second, I'd be very happy if you 
could tell me where this was fixed. Was it fixed upstream in some specific 
version/git? In which version or which commit?

I'm asking, because I'm running Debian these days and so if I could 
pinpoint the fix to some commit or version then I could also check it as 
done for Debian.

Thanks again and best greetings,
*t

On Sun, 8 Mar 2015, Alan Pater wrote:

> ** Changed in: exiv2 (Ubuntu)
>   Status: New => Fix Released
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/601555
>
> Title:
>  Error: Directory NikonPreview, entry 0xb3b2 has invalid size
>  3115890614*1; skipping entry.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gimp/+bug/601555/+subscriptions
>

-- 
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 1421938] Re: asked for permission to unmount partition while extracting file with file-roller

2015-03-09 Thread Tim

no I was not looking at an ISO, just extracting an archive. obviously
the unmount failed since I clicked cancel, but I have no idea what
caused it in the first place

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

Title:
  asked for permission to unmount partition while extracting file with
  file-roller

Status in tracker package in Ubuntu:
  New

Bug description:
  I just tried to extract a file using file-roller and was then asked
  for permission to umount a partition, seems kind of fishy to me, will
  attach output of journalctl, but   not currently booted with debug (I
  don't think)

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

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

[Touch-packages] [Bug 1429734] Re: invoke-rc.d ignores dependencies in degraded mode

** Changed in: sysvinit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  invoke-rc.d ignores dependencies in degraded mode

Status in sysvinit package in Ubuntu:
  Fix Committed

Bug description:
  Our CI test VMs often start in degraded mode as jobs like systemd-
  modules-load.service commonly fail. This causes invoke-rc.d to start
  services with --job-mode=ignore-dependencies, which causes e. g.
  openvswitch-nonetwork to not start up.

  We need to relax that to allow degraded mode, too.

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

-- 
Mailing list: https://launchpad.net/~touch-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-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "patch" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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 1327419] Re: Infographic's language not updated until the metric value is changed

2015-03-09 Thread Noemí

@Pat done. Here is the new one:
https://bugs.launchpad.net/barajas/+bug/1429752

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

Title:
  Infographic's language not updated until the metric value is changed

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Music application for Ubuntu devices:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in libusermetrics package in Ubuntu:
  Fix Released
Status in libusermetrics package in Ubuntu RTM:
  Fix Released

Bug description:
  1) Start the music app
  2) Play a track for more than 10 seconds to trigger the metric update
  3) Lock and unlock to show the infographic
  4) Note, for example, "1 song played today" appears (double tap to cycle 
through to find music if required)
  5) Goto system settings and change the language
  6) Restart the device
  7) Note the infographic's language has not been updated and it still states 
'1 song played today'
  8) Start the music app
  9) Play a track for more than 10 seconds to trigger the metric update
  10) Lock and unlock to show the infographic
  11) Now notice the infographic's language is now correct, for example "2 
Morceaux joues aujourd'hui"

  It was expected that step 7 the infographic would show the correct
  language.

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

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

[Touch-packages] [Bug 1429415] Re: Unable to enter password in the lock screen after using Qtcreator to run apps on the device

2015-03-09 Thread Benjamin Zeller

I'm not sure the lockup of the screen is actually a qtcreator-plugin-ubuntu
bug, since its not
present on krillin as you said.

If a SSH connection to the device is active or not does not change the device
connection
state, because USB is used to detect if a device is attached or not. However
the new policies
for ADB when the device is locked might make connections to the device fail. In
that case
ADB will just refuse connections, thats also the reason why the device will not
be detected
when its locked and attached for the first time.

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

Title:
Unable to enter password in the lock screen after using Qtcreator to
run apps on the device

Status in qtcreator-plugin-ubuntu package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New

Bug description:
I have noticed consistently that after upgrading the phone to vivid,
while developing apps and running them on the device via Qtcreator,
after a few runs, when the device locks (due to timeout, or manual
locking) it is no longer possible to unlock the device by typing in
the password in the lock screen since when I type the password, the
passphrase characters are not typed into the textfield. It is sort of
like the lock screen does not take any input. The only way to fix the
solution is to reboot the phone since I cannot adb into the device
without unlocking it first to do any unity8 reboots.

I noticed that I get the following output line on Qtc, Connection to
127.0.0.1 closed by remote host. I tried using 2 other cables and have
noticed the connection closed by remote host. But despite the remote
host closing the connection, QtC still displays the device status in
green indicating it is detected and available. However on trying to
run the app again, I get the error "Could not conenct to host:
Connection refused. Is the device still connected and set up network
access?"

This connection is terminated by remote host after few seconds even if
I let the app be idle during that time.

Steps to reproduce the issue:
1. Connect the phone to the laptop.
2. Open any app in Qtcreator and set it to run the app on the device.
3. Run the app on the device.
4. Close the app on the phone and lock the device.
5. Try unlocking the device.

What happens:
Device is locked and the lock screen textfield does not accept any input.
Pressing on the keypad buttons doesnt do anything

Note: The lockscreen issue happens only on vivid. But the connection
being terminated by the remote host happens both on vivid and rtm.

System Information:
Laptop: Ubuntu 14.04.2 LTS
Nexus 4(Mako) running vivid img 125
qtcreator-plugin-ubuntu: 3.1.1+15.04.20150224-0ubuntu1~0trusty1

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

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

[Touch-packages] [Bug 1429756] [NEW] FTBFS: test_job_process fails in majority of cases

Public bug reported:

As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
adt-upstart/?, upstart's test fail almost all the time, on

ok 53 - with single line command writing fast and exiting
not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
1..153
FAIL: test_job_process

Sometimes they succeed on one architecture, and with lots of luck on
both, but this is way too flaky to be an useful test. This keeps
blocking the propagation of other packages from -proposed.

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

** Affects: upstart (Ubuntu Vivid)
 Importance: High
 Status: New

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

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

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

[Touch-packages] [Bug 1341623] Re: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL

2015-03-09 Thread alex_b

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

I am still having this bug. I do not think that it is actually a
duplicate of bug #1342586 since the later one is fixed.

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

Title:
  systemd-logind assert failure: alloc.c:315: Assertion failed in
  nih_free: ptr != NULL

Status in systemd:
  Won't Fix
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: systemd 204-12ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4
  Uname: Linux 3.16.0-3-lowlatency x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: alloc.c:315: Assertion failed in nih_free: ptr != NULL
  Date: Mon Jul 14 09:39:48 2014
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2014-04-27 (78 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   nih_free () from /lib/x86_64-linux-gnu/libnih.so.1
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind assert failure: alloc.c:315: Assertion failed in 
nih_free: ptr != NULL
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

This is also reproducible on a package build in sbuild locally.

** Summary changed:

- test_job_process fails in majority of cases
+ FTBFS: test_job_process fails in majority of cases

** Also affects: upstart (Ubuntu Vivid)
   Importance: High
   Status: New

** Tags added: autopkgtset qa-daily-testing

** Tags removed: autopkgtset
** Tags added: autopkgtest

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

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

[Touch-packages] [Bug 1429734] Re: invoke-rc.d ignores dependencies in degraded mode

This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu11

---
sysvinit (2.88dsf-53.2ubuntu11) vivid; urgency=medium

  * service, invoke-rc.d: Don't ignore systemd unit dependencies in "degraded"
mode. (LP: #1429734)
 -- Martin PittMon, 09 Mar 2015 08:25:11 +0100

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

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

Title:
  invoke-rc.d ignores dependencies in degraded mode

Status in sysvinit package in Ubuntu:
  Fix Released

Bug description:
  Our CI test VMs often start in degraded mode as jobs like systemd-
  modules-load.service commonly fail. This causes invoke-rc.d to start
  services with --job-mode=ignore-dependencies, which causes e. g.
  openvswitch-nonetwork to not start up.

  We need to relax that to allow degraded mode, too.

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

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

[Touch-packages] [Bug 1421671] Re: Implement wifi hotspot status

The linked spec implies that hotspot status should *not* be in the
indicator -- "Using your phone as a hotspot is handled entirely in
System Settings". Did you mean to link to an indicator spec elsewhere?

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

Title:
  Implement wifi hotspot status

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Implement the wifi hotspot status in the indicator per the [1] spec

  1. https://wiki.ubuntu.com/Networking#hotspot

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

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

autoconfig for ALC3661: line_outs=2 (0x14/0x18/0x0/0x0/0x0) type:speaker
speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) hp_outs=2 (0x15/0x16/0x0/0x0/0x0)
mono: mono_out=0x0 inputs: Mic=0x19 Internal Mic=0x12

==> lo_type=2, wired=1, mio=1, badness=0x20
 multi_outs = 15/16/0/0 : 2/3/0/0 (type HP)
 out path: depth=3 '02:0c:15'
 out path: depth=3 '03:0d:16'
 spk_outs = 14/18/0/0 : 4/4/0/0
 spk path: depth=3 '04:0e:14'
 spk path: depth=3 '04:0e:18' 
==> lo_type=2, wired=1, mio=0, badness=0x20
 multi_outs = 15/16/0/0 : 2/3/0/0 (type HP)
 out path: depth=3 '02:0c:15'
 out path: depth=3 '03:0d:16'
 spk_outs = 14/18/0/0 : 4/4/0/0
 spk path: depth=3 '04:0e:14'
 spk path: depth=3 '04:0e:18' 
==> lo_type=2, wired=0, mio=1, badness=0x20
 multi_outs = 15/16/0/0 : 2/3/0/0 (type HP)
 out path: depth=3 '02:0c:15'
 out path: depth=3 '03:0d:16'
 spk_outs = 14/18/0/0 : 4/4/0/0
 spk path: depth=3 '04:0e:14'
 spk path: depth=3 '04:0e:18' 
==> lo_type=2, wired=0, mio=0, badness=0x20
 multi_outs = 15/16/0/0 : 2/3/0/0 (type HP)
 out path: depth=3 '02:0c:15'
 out path: depth=3 '03:0d:16'
 spk_outs = 14/18/0/0 : 4/4/0/0
 spk path: depth=3 '04:0e:14'
 spk path: depth=3 '04:0e:18' 
==> lo_type=1, wired=1, mio=1, badness=0x20
 multi_outs = 14/18/0/0 : 2/3/0/0 (type SP)
 out path: depth=3 '02:0c:14'
 out path: depth=3 '03:0d:18'
 hp_outs = 15/16/0/0 : 4/4/0/0
 hp path: depth=3 '04:0e:15' hp path: depth=3 '04:0e:16' 
==> lo_type=1, wired=1, mio=0, badness=0x20
 multi_outs = 14/18/0/0 : 2/3/0/0 (type SP)
 out path: depth=3 '02:0c:14'
 out path: depth=3 '03:0d:18'
 hp_outs = 15/16/0/0 : 4/4/0/0
 hp path: depth=3 '04:0e:15'
 hp path: depth=3 '04:0e:16' 
==> lo_type=1, wired=0, mio=1, badness=0x20
 multi_outs = 14/18/0/0 : 2/3/0/0 (type SP)
 out path: depth=3 '02:0c:14'
 out path: depth=3 '03:0d:18'
 hp_outs = 15/16/0/0 : 4/4/0/0
 hp path: depth=3 '04:0e:15'
 hp path: depth=3 '04:0e:16' 
==> lo_type=1, wired=0, mio=0, badness=0x20
 multi_outs = 14/18/0/0 : 2/3/0/0 (type SP)
 out path: depth=3 '02:0c:14'
 out path: depth=3 '03:0d:18'
 hp_outs = 15/16/0/0 : 4/4/0/0
 hp path: depth=3 '04:0e:15'
 hp path: depth=3 '04:0e:16' 
==> restoring best_cfg 
==> Best config: lo_type=2, wired=1, mio=1
 multi_outs = 15/16/0/0 : 2/3/0/0 (type HP)
 out path: depth=3 '02:0c:15'
 out path: depth=3 '03:0d:16'
 spk_outs = 14/18/0/0 : 4/4/0/0
 spk path: depth=3 '04:0e:14'
 spk path: depth=3 '04:0e:18'

this is not best config since assign speaker and subwoofer to same DAC
mean no spearate volume control for subwoofer and you need those config
(type SP) which DACs are assigned to speaker and subwoofer

the easy way is to change the headset as [N/A] by hdajackretask

or

change badness of those config (type SP)


CTRL: add: Headphone Playback Volume:0 
CTRL: add: Headphone Playback Switch:0 
CTRL: add: Headphone Playback Volume:1 
CTRL: add: Headphone Playback Switch:1 
CTRL: add: Speaker Playback Volume:0 
CTRL: add: Speaker Playback Switch:0 
CTRL: add: Bass Speaker Playback Switch:0 
CTRL: add: Mic Playback Volume:0 
CTRL: add: Mic Playback Switch:0 
CTRL: add: Auto-Mute Mode:0 
CTRL: add: Capture Volume:0 
CTRL: add: Capture Switch:0 
CTRL: add: Mic Boost Volume:0 
CTRL: add: Master Playback Volume:0 
CTRL: add: Master Playback Switch:0 
CTRL: add: Mic Jack:0 JACK created Mic, type 2 JACK report Mic, status 0 
CTRL: add: Internal Mic Phantom Jack:0 
CTL Notify: Internal Mic Phantom Jack:0, mask=1 
CTRL: add: Headphone Front Jack:0 JACK created Headphone Front, type 1 JACK 
report Headphone Front, status 0 CTRL: add: Headphone Surround Jack:0 JACK 
created Headphone Surround, type 1 JACK report Headphone Surround, status 0 
CTRL: add: Speaker Front Phantom Jack:0 CTL Notify: Speaker Front Phantom 
Jack:0, mask=1 
CTRL: add: Speaker Surround Phantom Jack:0 CTL Notify: Speaker Surround Phantom 
Jack:0, mask=1 
CTRL: add: Playback Channel Map:0 
CTRL: add: Capture Channel Map:0 JACK report Headphone Front, status 0 JACK 
report Headphone Surround, status 0 JACK report Mic, status 0

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

[Touch-packages] [Bug 1429766] [NEW] Alt+Left/RightArrow switches from graphic into text virtual console (Vivid)

2015-03-09 Thread Wladimir Mutel

Public bug reported:

After some dist-upgrades of my Vivid testing system I noticed that
Alt+Left/Right started to switch from GUI into prev/next text virtual
console (as well as prev/next web page in Web browser which I used to
using). I would like to restore their function back as expected (web
page navigation only, not VConsoles). Please advise on what to
reconfigure or downgrade.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu2
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: KDE
Date: Mon Mar  9 11:08:19 2015
InstallationDate: Installed on 2009-11-01 (1953 days ago)
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu 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/1429766

Title:
  Alt+Left/RightArrow switches from graphic into text virtual console
  (Vivid)

Status in xorg package in Ubuntu:
  New

Bug description:
  After some dist-upgrades of my Vivid testing system I noticed that
  Alt+Left/Right started to switch from GUI into prev/next text virtual
  console (as well as prev/next web page in Web browser which I used to
  using). I would like to restore their function back as expected (web
  page navigation only, not VConsoles). Please advise on what to
  reconfigure or downgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  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: KDE
  Date: Mon Mar  9 11:08:19 2015
  InstallationDate: Installed on 2009-11-01 (1953 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  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/1429766/+subscriptions

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

[Touch-packages] [Bug 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails

2015-03-09 Thread Alex Botev

On 14.04 experiencing the same problem. After I try to connect to my VPN
in a matter of a few seconds after the successful connection I get
disconnected. Following this post http://tdanas.blogspot.co.uk/2015/01
/ubuntu-vpn-connects-successfully-and.html I decide to see what are my
routing tables while the connection is on. Results are:

Destination  Gateway  Genmask Flags Metric Ref  
  Use Iface
default   * 0.0.0.0 
 U 0  00 ppp0
cyrano2.cs.ucl.172.17.31.1 255.255.255.255   UGH   0  00 
wlan0
cyrano2.cs.ucl.172.17.31.1 255.255.255.255   UGH   0  00 
wlan0
winvpn11.cs.ucl  * 255.255.255.255   UH  0  0   
 0 ppp0
172.17.31.0  * 255.255.255.0U 9 
 00 wlan0

I do not know how it works but having a duplicate entry in the routing
table might be the cause of the problem.

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

Title:
  VPN Connects Successfully & Then Shortly Thereafter Fails

Status in NetworkManager-PPTP:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am able to successfully establish a PPTP VPN connection in Ubuntu
  12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to
  1.5 minutes it will fail.  During the connection time I am only able
  to load about 1-2 webpages and then they freeze and I cannot access
  resources on the VPN network.  I do not believe this is related to my
  VPN server as I am able to establish VPN connections with my Windows
  machines and Smartphones all day long with no problems.  Is there a
  solution to this problem?

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  network-manager: 0.9.4.0-0ubuntu3

  Here is the syslog:

  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  Starting VPN 
service 'pptp'...
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN service 'pptp' 
started (org.freedesktop.NetworkManager.pptp), PID 15069
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN service 'pptp' 
appeared; activating connections
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN plugin state 
changed: starting (3)
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:  VPN connection 
'Schaefer Law Group' (Connect) reply received.
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin 
/usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
  Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 
log[main:pptp.c:314]: The synchronous pptp option is NOT activated
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 
'Outgoing-Call-Request'
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's 
call ID 0).
  Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded
  Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless 
compression enabled
  Apr 30 00:17:55 satellite-p755 pppd[15073]: local  IP address 192.168.1.20
  Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1
  Apr 30 00:17:55 satellite-p755 pppd[15073]: primary   DNS address 8.8.8.8
  Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  VPN connection 
'Schaefer Law Group' (IP Config Get) reply received.
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  VPN Gateway: 
75.75.79.330
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Tunnel Device: ppp0

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

2015-03-09 Thread James Hunt

'mk-sbuild vivid' currently gives an error:

You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 systemd-sysv : Conflicts: upstart but 1.13.2-0ubuntu9 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a 
solution).

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

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

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

2015-03-09 Thread Christopher M. Penalver

Hồng Quân, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1193238/comments/13
regarding you no longer have the laptop. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

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)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

2015-03-09 Thread Christopher M. Penalver

Christoph, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1425891/comments/5
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  Invalid

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 1429214] Re: [Scopes] Departments not behaving consistently when navigating too/from a Scope

2015-03-09 Thread Albert Astals Cid

It is not moving away from a scope that resets the department, it is
starting a search that resets it.

As far as i understood that is how it is specified. And i think it's the
scopes plugin that does that.

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Scopes] Departments not behaving consistently when navigating
  too/from a Scope

Status in Ubuntu UX bugs:
  Triaged
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Departments are currently not cleared for Apps (as well as other Scopes) when 
navigating away/too a Scope. However, if a user selects a department and then 
conducts a search, navigating away/too the scope clears the search AND resets 
the department (tested in the Amazon and Ebay Scopes). 
  Additionally, opening the department drop-down shows the previously selected 
department as still being active/applied.

  Recommendation:
  Apps Scope is a special case where we should clear searches and reset 
departments (including within the department drop-dow) when a user navigates 
away from the scope.

  All other scopes should preserve both the department and (where
  relevant) filters, but clear searches (which are easily accessible by
  beginning a new search and selecting from the recent search list).

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

-- 
Mailing list: https://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-09 Thread Iain Lane

On Sun, Mar 08, 2015 at 06:50:58PM -, Martin Pitt wrote:
> 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)

OK, just checked with upstart - poweroff is fine there.

Seems session start is fine too: I just tried 10 times under both and
that works too.

-- 
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 868713] Re: [2 new] Mono: up/down triangles for Byobu terminal multiplexer

** Tags added: uff-dm-new

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

Title:
  [2 new] Mono: up/down triangles for Byobu terminal multiplexer

Status in Ubuntu Font Family:
  Triaged
Status in ubuntu-font-family-sources package in Ubuntu:
  Triaged

Bug description:
  Monospace unicode characters of the Ubuntu font are overrunning other
  characters and some things are just unreadable :-(

U+25B2 BLACK UP-POINTING TRIANGLE (▲)
U+25BC BLACK DOWN-POINTING TRIANGLE (▼)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/868713/+subscriptions

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

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

@James: that was due to a set of priority mismatches, these got fixed
now. Try again?

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

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

[Touch-packages] [Bug 724022] Re: [21 new] Allow use of Ubuntu Mono as .psf console-setup font

** Tags added: uff-dm-new

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

Title:
  [21 new] Allow use of Ubuntu Mono as .psf console-setup font

Status in Ubuntu Font Family:
  Confirmed
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  The text-mode console (Ctrl-Alt-F1) currently uses the default
  system/VGA font but a hinted version of Ubuntu Mono would be lovely to
  have loadable on the Linux console when it's finished.

  Converting a TTF so that it is usable as bitmap Linux console font
  appears to be a two-stage process;  first rasterising to a BFD bitmap
  font file (bitmap with metrics), and then from that into a rawform,
  equal width PSF bitmap console font:

    otf2bdf 
/usr/share/fonts/truetype/ubuntu-font-family/UbuntuBetaMono-R-R21.ttf > 
UbuntuBetaMono-R-R21.bdf
    bdf2psf UbuntuBetaMono-R-R21.bdf /usr/share/bdf2psf/standard.equivalents 
/usr/share/bdf2psf/required.set+/usr/share/bdf2psf/useful.set 256 
UbuntuBetaMono-R-R21.psf
    setfont -h17 UbuntuBetaMono-R-R21.psf

  The R21 Mono Beta has a cell bounding box of 482×1000 (including
  necessary leading and advance); this leads to bounding box of 8x17
  rather than the traditional 8x16 and this is what the "-n17" forces
  upon loading.  The result useful but very ugly because of the lack of
  manual hinting.

  We probably also want to make sure that at least all of the codepoints listed 
in the 'required.set' file are present and populated if we're going to replace 
the current default.
  =
  Eventually (11.10?) we should try to apply the Ubuntu fonts to the console as 
well. Steps 12–14 are blocked waiting for the Ubuntu Monospace to be released 
and available in the archive.

   11) gfxboot-theme-ubuntu (Proportional) - bug #732854
   12) Bterm (d-i) (Monospace) -
   13) Grub2 (Monospace) - bug #729470
   14) Console-setup (Monospace) - bug #724022 (this bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/724022/+subscriptions

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

2015-03-09 Thread Albert Astals Cid

Have been using https://codereview.qt-project.org/#/c/103738/ (and all
the pre-requisite patches) for a while and they seem to fix the issues
i've been having with dbus deadlocks

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

Title:
  unity8 sometimes hangs on boot

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  The following gdbus call is failing with a "Error: Timeout was
  reached" message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  
  This is being seen on krillin devices starting with image 106 from 
ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've 
seen it 3 times from about 12 tests. On the most recent failure, I grabbed a 
console and tried repeatedly to run the command from the shell, even after 2 
hours the timeout was still being returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

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

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

[Touch-packages] [Bug 820034] Re: [742 new] Miscellaneous Symbols and Pictographs (Emoji)

** Tags added: uff-dm-new

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

Title:
  [742 new] Miscellaneous Symbols and Pictographs (Emoji)

Status in Ubuntu Font Family:
  Triaged
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  This is a wishlist item.

  Please introduce Unicode character 'PILE OF POO' (U+1F4A9) in future versions 
of the Ubuntu font.
  It could be quite useful for changelogs, or for certain email communications.

  Ref.:
  http://www.fileformat.info/info/unicode/char/1f4a9/index.htm
  http://babelstone.blogspot.com/2009/11/whats-new-in-unicode-60.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/820034/+subscriptions

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

[Touch-packages] [Bug 1429214] Re: [Scopes] Departments not behaving consistently when navigating too/from a Scope

2015-03-09 Thread Pawel Stolowski

As Albert says, it's typing a search query that resets department and
filters. This works as designed, i.e. departments and filters are only
shown in surfacing/browsing mode and disappear as soon as user enters a
search query.

So, if I undestand it right, the problem to be addressed is to special-
case Apps, so that navigating to/from Apps resets departments and
filters in Apps, correct?

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

Title:
  [Scopes] Departments not behaving consistently when navigating
  too/from a Scope

Status in Ubuntu UX bugs:
  Triaged
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Departments are currently not cleared for Apps (as well as other Scopes) when 
navigating away/too a Scope. However, if a user selects a department and then 
conducts a search, navigating away/too the scope clears the search AND resets 
the department (tested in the Amazon and Ebay Scopes). 
  Additionally, opening the department drop-down shows the previously selected 
department as still being active/applied.

  Recommendation:
  Apps Scope is a special case where we should clear searches and reset 
departments (including within the department drop-dow) when a user navigates 
away from the scope.

  All other scopes should preserve both the department and (where
  relevant) filters, but clear searches (which are easily accessible by
  beginning a new search and selecting from the recent search list).

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

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

[Touch-packages] [Bug 433897] Re: Console/VT font is (randomly) not set (sometimes) on some machines. Stuck with the default VGA BIOS font.

2015-03-09 Thread Daniel van Vugt

Still happening in vivid :(

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

Title:
  Console/VT font is (randomly) not set (sometimes) on some machines.
  Stuck with the default VGA BIOS font.

Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Precise:
  Confirmed
Status in console-setup source package in Quantal:
  Won't Fix

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has 
started, the font is no longer set at bootup. This results in unreadable user 
prompts, whenever applications output non-ascii characters to screen and it 
also affects graphic box characters used by ncurses, such as for debconf 
dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

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

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

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

2015-03-09 Thread James Hunt

mk-sbuild now fails with a different error:

Setting up udev (219-4ubuntu3) ...
A chroot environment has been detected, udev not started.
/var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst: 
update-initramfs: not found
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

But back to the test failure... this  test has been running successfully
on all platforms for a long time (3+ years). It's possible that the test
itself is racy and that a recent change in a different package has
exposed that. Do we know when this test first started failing (and
ideally what changes triggered it (kernel/libc))?

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

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

[Touch-packages] [Bug 724022] Re: [21 new] Allow use of Ubuntu Mono as .psf console-setup font

2015-03-09 Thread Daniel van Vugt

Beware of bug 433897. For many of us, the console font is (randomly)
never set (on random machines).

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

Title:
  [21 new] Allow use of Ubuntu Mono as .psf console-setup font

Status in Ubuntu Font Family:
  Confirmed
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  The text-mode console (Ctrl-Alt-F1) currently uses the default
  system/VGA font but a hinted version of Ubuntu Mono would be lovely to
  have loadable on the Linux console when it's finished.

  Converting a TTF so that it is usable as bitmap Linux console font
  appears to be a two-stage process;  first rasterising to a BFD bitmap
  font file (bitmap with metrics), and then from that into a rawform,
  equal width PSF bitmap console font:

    otf2bdf 
/usr/share/fonts/truetype/ubuntu-font-family/UbuntuBetaMono-R-R21.ttf > 
UbuntuBetaMono-R-R21.bdf
    bdf2psf UbuntuBetaMono-R-R21.bdf /usr/share/bdf2psf/standard.equivalents 
/usr/share/bdf2psf/required.set+/usr/share/bdf2psf/useful.set 256 
UbuntuBetaMono-R-R21.psf
    setfont -h17 UbuntuBetaMono-R-R21.psf

  The R21 Mono Beta has a cell bounding box of 482×1000 (including
  necessary leading and advance); this leads to bounding box of 8x17
  rather than the traditional 8x16 and this is what the "-n17" forces
  upon loading.  The result useful but very ugly because of the lack of
  manual hinting.

  We probably also want to make sure that at least all of the codepoints listed 
in the 'required.set' file are present and populated if we're going to replace 
the current default.
  =
  Eventually (11.10?) we should try to apply the Ubuntu fonts to the console as 
well. Steps 12–14 are blocked waiting for the Ubuntu Monospace to be released 
and available in the archive.

   11) gfxboot-theme-ubuntu (Proportional) - bug #732854
   12) Bterm (d-i) (Monospace) -
   13) Grub2 (Monospace) - bug #729470
   14) Console-setup (Monospace) - bug #724022 (this bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/724022/+subscriptions

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

[Touch-packages] [Bug 1221172] Re: [Gallery app] Deleted photos displayed as empty squares in 'Photos' tab

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

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

Title:
  [Gallery app] Deleted photos displayed as empty squares in 'Photos'
  tab

Status in Ubuntu UX bugs:
  Fix Released
Status in gallery-app package in Ubuntu:
  Incomplete

Bug description:
  Current situation:
  Previously deleted photos still display as empty squares in 'Photos' tab only.
  Screenshot attached.

  Desired solution:
  Deleted photos should not be displayed at all.

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

-- 
Mailing list: https://launchpad.net/~touch-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-09 Thread Alberto Salvia Novella

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

-- 
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 1368808] Re: [camera]+[gallery] Accessing photo roll could be more discoverable

** 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 camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1368808

Title:
  [camera]+[gallery] Accessing photo roll could be more discoverable

Status in Camera App:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu RTM:
  Fix Released

Bug description:
  "Some participants tried locate a picture icon option on the camera to
  link them to the photo they just had taken.  Not finding it, they left
  the camera and looked for the photo somewhere else, in the gallery. "

  Investigate visual aides to help users understand how to access photo
  roll

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

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

[Touch-packages] [Bug 1221174] Re: [Gallery app] Timeline displays year '-4714'

** Changed in: ubuntu-ux
   Status: Triaged => Incomplete

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

Title:
  [Gallery app] Timeline displays year '-4714'

Status in Ubuntu UX bugs:
  Incomplete
Status in gallery-app package in Ubuntu:
  Incomplete

Bug description:
  Current:
  Under 'Event's timeline displays year '-4714'. Trigger unknown.
  Screenshot attached.

  Desired:
  Timeline should not display date/years beyond when photos were taken.

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

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

[Touch-packages] [Bug 1229125] Re: [share-service] share options are not revealed

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

Title:
  [share-service] share options are not revealed

Status in Share App:
  New
Status in Ubuntu UX bugs:
  Fix Released
Status in share-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Current situation
  Share options isn't displayed: 
https://docs.google.com/a/canonical.com/file/d/0B3ChmfHLAGxBZTJFV01OZmY5UDg/edit

  Desired solution
  New designs is to have the expansion pattern instead of the pop-over. Please 
refer to: 
https://dl.dropboxusercontent.com/u/2536265/content_picker_gallery3.html

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

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

[Touch-packages] [Bug 1229663] Re: Unselected tab names too dark in "Dark" theme

** 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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1229663

Title:
  Unselected tab names too dark in "Dark" theme

Status in Ubuntu UI Toolkit:
  Invalid
Status in Ubuntu UX bugs:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Current situation:

  In the dark theme (for example, in an open indicator screen) if you
  tap the tabs header to see other available tabs, the ones that are not
  selected are too dark, hard to see

  Solution:

  The unselected tab colour in dark theme should be #f3f3e7, 0.2 opacity

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

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

[Touch-packages] [Bug 1333187] Re: [TOPBLOCKER] [Dash] [design] Preview images display as black thumbnails

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

Title:
  [TOPBLOCKER] [Dash] [design] Preview images display as black
  thumbnails

Status in The Savilerow project:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  If the image is large, the Ubuntu shape rounded corners become very
  little, hardly noticable.

  REQUESTED UX SOLUTION
  Updated spec so images only zoomable once full screen.

  For all other instances of ubuntu shape, SDK documentation should be
  used (see link from Jouni in comments)

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

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

[Touch-packages] [Bug 1373517] Re: [sdk] invoked "search" in apps should display "<" for BACK and not "X"

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

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

Title:
  [sdk] invoked "search" in apps should display "<" for BACK and not "X"

Status in Address Book App:
  In Progress
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Invalid
Status in Ubuntu UX bugs:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Address Book or Messaging apps
  2. Tap in the main landing view(s) the "Search" icon
  3. Actual result: a "X" icon is displayed on the left hand side for 
cancelling the search action

  4. Expected result: a "<" BACK icon should be displayed, as currently
  on the dash

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1373517/+subscriptions

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

[Touch-packages] [Bug 1324442] Re: Replace all gradients with plain colors

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Replace all gradients with plain colors

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The updated designs aim to stop using gradients. To avoid having to
  change all apps, it should be doable to replace the two colors each
  with the same value.

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

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

[Touch-packages] [Bug 1356779] Re: [SDK] MainView.backgroundColor is not usable any more

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

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

Title:
  [SDK] MainView.backgroundColor is not usable any more

Status in Ubuntu UX bugs:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  Since the latest SDK updates, MainView.backgroundColor is not usable
  any more. It completely messes up the whole theming:

  For example setting a dark background causes:

  * Text in Dialogs to be unreadable
  * Header Popovers (the new ones) to turn purple(!)
  * Active ListItem's text color to be unreadable

  And the situation seems to get worse with each uitk update... Maybe
  the *color properties of the MainView should just be removed? If you
  think that should be kept but all the places that break should be
  fixed instead to make it work again, please let me know and I'll do my
  best to collect all the places it broke.

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

-- 
Mailing list: https://launchpad.net/~touch-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] SRU request for lp#1214352

2015-03-09 Thread Norbert

Dear Ubuntu Bug Control team!

There is a bug in Glib in Ubuntu 12.04.5 - bug 1214352
.

If it possible please apply an SRU for it.


With best regards,
Ubuntu user,
Norbert.

-- 
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 1373517] Re: [sdk] invoked "search" in apps should display "<" for BACK and not "X"

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

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

Title:
  [sdk] invoked "search" in apps should display "<" for BACK and not "X"

Status in Address Book App:
  In Progress
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Invalid
Status in Ubuntu UX bugs:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Address Book or Messaging apps
  2. Tap in the main landing view(s) the "Search" icon
  3. Actual result: a "X" icon is displayed on the left hand side for 
cancelling the search action

  4. Expected result: a "<" BACK icon should be displayed, as currently
  on the dash

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1373517/+subscriptions

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

[Touch-packages] [Bug 1356864] Re: [SDK] Button with strokeColor does not change font colour

Is this still an issue?

We would like devs to be able to choose the colour of the stroke and the
text inside independently

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

Title:
  [SDK] Button with strokeColor does not change font colour

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Given the attached QML, there is no way to change the font color
  inside the button, which should basically be the same as the stroke
  color.

  I don't think it's necessary to allow overriding the font color alone
  in the case of a stroke button, everything should be the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.1.1181+14.10.20140806-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 14 14:49:47 2014
  SourcePackage: ubuntu-ui-toolkit
  SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 
'system-image-cli'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1406047] Re: Poor contrast between text and background in ProgressBar

It should indeed turn white, looks like a problem with RTM. Tim are you
able to fix?

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

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

Title:
  Poor contrast between text and background in ProgressBar

Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  I'm not sure if this is an issue for everyone, or just for people with
  colour blindness but I find the dark grey text showing the progress
  percentage very difficult to read against the Ubuntu orange colour.
  Switching to a light colour like white would be more readable once the
  current progress covers the text.

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

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

[Touch-packages] [Bug 1408643] Re: Header divider is invisible on very dark backgrounds

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

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

Title:
  Header divider is invisible on very dark backgrounds

Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The color for the header divider is calculated by
  Qt.darker(backgroundColor). If backgroundColor is already very dark or
  black, this leads to an invisible header divider. Probably it needs to
  check for a certain darkness threshold and use
  Qt.lighter(backgroundColor) instead.

  Ideally the app developer could also override the color for the
  divider so that it can match the foregroundColor, meaning the divider
  would be the same color as the text and icons inside the header.

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

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

[Touch-packages] [Bug 1350893] Re: [sdk] Allow header background customization per page

Makes sense to allow developers to change the header colour by page if
someone really wants to

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

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

Title:
  [sdk] Allow header background customization per page

Status in Ubuntu UI Toolkit:
  Incomplete
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Each Page should have the ability to customize a few things about the
  look of the header, these changes should take affect when the page
  becomes the top page in a PageStack or the current tab in Tabs.

  headerColor: Set the background color of the Header
  headerGradient: Same as headerColor, only using a Gradient object instead of 
a single color
  headerImage: Set a background Image on the Header, resized to fit based on 
fillMode
  headerBorderImage: Same as headerImage, but using a BorderImage

  follow-up of this bug: https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1315884 which I changed to only include header foreground
  color customization.

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

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

[Touch-packages] [Bug 1379379] Re: [SDK] Popover tip is not rendered properly

Saw some chatter about the new ubuntu shape last week - is this going to
be landing?

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

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

Title:
  [SDK] Popover tip is not rendered properly

Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The tip of the popover is not rendered properly

  - dropshadow is different
  - small horizontal line should not be there

  Actual appearance here in the SDK dropbox folder
  https://www.dropbox.com/sh/7fnssmbsyuc6c8l/AADiZ5i-pZbDcPaFBUKPmjaUa?dl=0

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

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

[Touch-packages] [Bug 1425593] Re: trivial app fails to appear in shell and crashes it on close

2015-03-09 Thread Albert Astals Cid

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

Title:
  trivial app fails to appear in shell and crashes it on close

Status in Qt integration with the Mir display server:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Take this code:

  #include 
  #include 

  int main(int argc, char *argv[])
  {
  QApplication app(argc, argv);
  QWidget *w = new QWidget();
  w->showMaximized();
  return app.exec();
  }

  
  and this Qt pro file:

  QT   += core gui widgets
  TARGET = simple-qwidget
  TEMPLATE = app
  SOURCES += main.cpp

  and build on the device. On unity8 run with:

  ./simple-qwidget --desktop_file_hint=/usr/share/applications
  /mediaplayer-app.desktop

  You'll see the splash screen appear, but you'll never see a frame from the 
app.
  When I Ctrl+C the app, unity8 crashes

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

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

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

It started failing around Feb 27. It roughly coincides with
https://launchpad.net/ubuntu/+source/glibc/2.19-15ubuntu2 (but that
looks unlikely), the most likely candidate is the upgrade of linux from
3.18 to 3.19: https://launchpad.net/ubuntu/+source/linux/3.19.0-7.7


** Description changed:

  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on
  
  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
-   wrong value for bytes, expected 3145728 got 3018027
-   at tests/test_job_process.c:3886 (test_start).
+  wrong value for bytes, expected 3145728 got 3018027
+  at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process
  
  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.
+ 
+ This was most likely triggered by the kernel update from 3.18 to 3.19.

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

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

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

I think we need a small drop shadow on the text on these screens.

Can we use http://doc.qt.io/qt-5/qml-qtgraphicaleffects-dropshadow.html

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

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

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

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

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

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

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

2015-03-09 Thread eezacque

I would appreciate if you could add yourself as an affected user.

-- 
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 1416048] Re: [media player] Expected to be able to pause a video by tapping on anywhere of the video

I agree with Jim's suggestion - let's make the first tap show controls

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

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

Title:
  [media player] Expected to be able to pause a video by tapping on
  anywhere of the video

Status in Media Player App:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Tapping anywhere on the video that is playing should pause it and vice
  versa.

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

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

[Touch-packages] [Bug 1429784] [NEW] Battery level stuck overnight

You have been subscribed to a public bug:

Test case.
- Leave the device locked overnight.
- On the next morning, go to System Settings > Battery.

Expected result.
- Battery should report a lower level.

Actual result.
- A plain graph is shown.

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

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


** Tags: qa-exploratory touch
-- 
Battery level stuck overnight
https://bugs.launchpad.net/bugs/1429784
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

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

[Touch-packages] [Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses

2015-03-09 Thread LocutusOfBorg

thanks Norbert, I missed that :)

https://launchpad.net/~costamagnagianfranco/+archive/ubuntu
/locutusofborg-ppa

package with the fix above uploaded here, can you please test it?

-- 
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 1260978] Re: [Greeter] should be able to control music service while greeter locked

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

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

Title:
  [Greeter] should be able to control music service while greeter locked

Status in Media Hub:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Opinion
Status in ubuntu-music-app package in Ubuntu:
  Opinion
Status in ubuntu-settings-components package in Ubuntu:
  Opinion

Bug description:
  Not sure what component to file this against-- please reassign as
  desired.

  I use my phone to play music on random while I'm driving. This works
  great except when I want to advance or pause the song, where I have to
  go through the greeter first to access the player. This can either
  take my attention away from driving or I need to wait until the next
  stop light to advance the song. This is less of a concern when the
  greeter can just be swiped with one gesture, but is a big concern if
  you enable the passcode lock where you have to add the passcode to
  access the player.

  If the music is playing, the greeter should allow rudimentary
  manipulation of the music, eg, pause/play and forward/back. Other
  platforms seem to allow for this (eg android).

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1260978/+subscriptions

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

** Attachment added: "debdiff"

https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1214352/+attachment/4338685/+files/debdiff

--
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 1429784] Re: Battery level stuck overnight

2015-03-09 Thread Sebastien Bacher

settings only displays the recording done by upower, that's an upower or
kernel issue, not a settings one

** Package changed: ubuntu-system-settings (Ubuntu) => upower (Ubuntu)

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

Title:
  Battery level stuck overnight

Status in upower package in Ubuntu:
  New

Bug description:
  Test case.
  - Leave the device locked overnight.
  - On the next morning, go to System Settings > Battery.

  Expected result.
  - Battery should report a lower level.

  Actual result.
  - A plain graph is shown.

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

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

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

[Touch-packages] [Bug 1424588] Re: unable to center popover in caller

2015-03-09 Thread Christian Dywan

These designs appear to assume the context menu component we don't yet
have, which would have this different positioning behavior.

** Summary changed:

- unable to center popover in caller
+ Need a context menu component

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

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

Title:
  Need a context menu component

Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The design for the browser app’s contextual menu requires the popover
  to be centered inside its caller (the webview). See
  
https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g34608d763_079
  for reference. The popover is opened using PopupUtils.open(…).

  I’ve tried two different approaches to achieve that, but none actually
  works:

   - passing the webview as the caller
   - passing no caller parameter at all

  In both cases, the popover is horizontally centered, but it’s anchored
  to the top of the scene.

  I’m attaching a standalone example that demonstrates the issue.

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

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

[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

2015-03-09 Thread Nils Toedtmann

Note that situation #1089195 is another possible outcome of this bug.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

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

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

[Touch-packages] [Bug 1325899] Re: evince is excruciatingly slow on some documents

2015-03-09 Thread madbiologist

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

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

Title:
  evince is excruciatingly slow on some documents

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

Bug description:
  Evince is excruciatingly slow when displaying the book available for download 
at http://www.safetty.net/publications/pttes
  Scrolling can take several seconds and will often just display empty pages. 
(And it is even worse with the 2009 version of the book you can still find on 
several places on the internet), while xpdf has no problems at all with 
instantly switching to the next page.

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

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

[Touch-packages] [Bug 1373607] Re: Switching the camera from rear to front to rear facing causing the controls to disappear

** Branch linked: lp:~fboucault/qtvideo-node/fix_rotate_z_order

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

Title:
  Switching the camera from rear to front to rear facing causing the
  controls to disappear

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Confirmed
Status in camera-app package in Ubuntu:
  In Progress
Status in camera-app package in Ubuntu RTM:
  In Progress

Bug description:
  $ system-image-cli -i
  current build number: 254
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-09-24 16:38:15
  version version: 254
  version ubuntu: 20140924
  version device: 20140923.1
  version custom: mako-0.6

  What happened:
  1) Start the camera app, note the contols at the bottom (video mode, capture 
photo, switch camera)
  2) Select switch camera to change to the front facing, note the controls are 
still there
  3) Select switch camera again to switch back to rear facing
  4) Notice that the controls have disappeared and that the user has to touch 
the screen for the controls to appear again.

  What was expected:
  At step 4 for the controls to be visible

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

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

[Touch-packages] [Bug 1429809] [NEW] ATI HDMI audio: echoing and crackling sound

2015-03-09 Thread Le Gluon Du Net

Public bug reported:

Hello,

my computer is connected to my TV screen with HDMI. 
I'm using HDMI displayport audio out in pulseaudio.
I hear crackling and echoing.

If I use this workaround:

echo '# add support for intel audio
options snd-hda-intel vid=8086 pid=8ca0 snoop=0' >> 
/etc/modprobe.d/alsa-base.conf

it works but after several minutes I have an important delay between
video and audio.

Thank you for your help.

LGDN.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  magneto1830 F pulseaudio
 /dev/snd/pcmC1D3p:   magneto1830 F...m pulseaudio
 /dev/snd/controlC1:  magneto1830 F pulseaudio
 /dev/snd/controlC0:  magneto1830 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar  9 12:30:14 2015
InstallationDate: Installed on 2014-06-19 (263 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [All Series, ATI R6xx HDMI, Digital Out, HDMI] Underruns, dropouts or 
crackling sound
UpgradeStatus: Upgraded to utopic on 2015-03-09 (0 days ago)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: GRYPHON Z87
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.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1429809

Title:
  ATI HDMI audio: echoing and crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  my computer is connected to my TV screen with HDMI. 
  I'm using HDMI displayport audio out in pulseaudio.
  I hear crackling and echoing.

  If I use this workaround:

  echo '# add support for intel audio
  options snd-hda-intel vid=8086 pid=8ca0 snoop=0' >> 
/etc/modprobe.d/alsa-base.conf

  it works but after several minutes I have an important delay between
  video and audio.

  Thank you for your help.

  LGDN.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  magneto1830 F pulseaudio
   /dev/snd/pcmC1D3p:   magneto1830 F...m pulseaudio
   /dev/snd/controlC1:  magneto1830 F pulseaudio
   /dev/snd/controlC0:  magneto1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  9 12:30:14 2015
  InstallationDate: Installed on 2014-06-19 (263 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [All Series, ATI R6xx HDMI, Digital Out, HDMI] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to utopic on 2015-03-09 (0 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z87
  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.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage

Re: [Touch-packages] [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up

2015-03-09 Thread Goth Queen

Dear Christopher,

Thanks for getting back to me on it.

Short answer is yes, it is still an issue. It was gone for a while, and I 
suspect it had something to do with a cairo update we got. However, that is my 
impression, I'm no dev of course, but we all thought it funny that this update 
came and our bug seemed to be gone. However, after a while the bug returned, 
and I guess since a month or so, the issue seems to have worsened, where now 
all the desktop icons reset themselves to default position (starting complete 
left top, and lining additional icons below it) on every (re)boot on all 3 
boxes we have here. I already have done some digging on it, and have seen there 
are more people who are experiencing this bug. 
As with the 1st bug I reported (no icon placement on right screen of dual 
screen setup - #1316090) it seems to be connected to the icons.screen0.XXX.rc 
files in ~/.config/xfce4/desktop. A fix seems to have been upstreamed but I 
haven't seen it yet 
(https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1335492, 
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1307251).

To come back to your specific question: I think we are fine for now just
being patient, and see if the situation changed when the fixes from
1335492 and 1307251 come through. If that doesn't change a thing, it
won't be a big deal for us. However, if we can help you guys with
development and want me to send a diagnosis anyway, please just let me
know. I'd be more than happy help with the great job you guys are doing
(if I can ;-)

Thanks again and greetz,

Natalia

> Date: Mon, 2 Mar 2015 00:33:25 +
> From: christopher.m.penal...@gmail.com
> To: artistbr...@hotmail.com
> Subject: [Bug 1316090] Re: Unable to drop/ place files and links on second 
> screen in dual screen set up
> 
> Goth Queen, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
> 
> If it remains an issue, could you please run the following command in
> the development release from a Terminal as it will automatically gather
> and attach updated debug information to this report:
> 
> apport-collect -p xorg 1316090
> 
> Please ensure you have xdiagnose installed, and that you click the Yes
> button for attaching additional debugging information.
> 
> As well, given the information from the prior release is already
> available, testing a release prior to the development one would not be
> helpful.
> 
> Thank you for your understanding.
> 
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
> 
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
> 
> ** Changed in: xorg (Ubuntu)
>Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1316090
> 
> Title:
>   Unable to drop/ place files and links on second screen in dual screen
>   set up
> 
> Status in xorg package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   After updating from Xubuntu 13.10 (amd64) to Xubuntu 14.04 LTS (amd64)
>   I have encountered a bug with my dual screen set up.
> 
>   Running the XOrg screen driver (xserver-xorg-video-nouveau), it is
>   possible to place/ drag and drop files and links on my left screen
>   desktop. This is also the desktop that contains the system icons (e.g.
>   removable drives, rubbish bin).
> 
>   However, I I try to drag and drop a file or link on the right screen
>   desktop, it will not "stick" and "fly back" to its original location
>   on the left screen. Additionally, I noticed that, when dragging the
>   file over the troubled desktop, the "placement squares" don't show up.
>   They do on the functioning left screen.
> 
>   Although I have a NVIDIA Corporation GK107 [GeForce GTX 650] Geforce I
>   do run the XOrg driver since it gives me the best results with the
>   software I'm using frequently. However, when I tested this during my
>   initial install of Trusty, I noticed that I did not encounter this bug
>   with the proprietary NVidia 304.117 driver (331.38 did not work for me
>   at all). Running the NVidia 304.117 driver, it was possible to drag
>   and drop/ place files and links on both screen desktops. Also the
>   "placement squares" appeared on both screens when a file was dragged
>   over it.
> 
>   After returning to the XOrg driver, the problem reoccurred, and
>   placement on the right screen was again not possible.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316090/+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/1316090

Title:
  Unable

[Touch-packages] [Bug 1350891] Re: [Scopes] Suru Background should scroll

2015-03-09 Thread Alex Milazzo

The dash background remains fixed and not scrolling with the content

** Changed in: ubuntu-ux
   Importance: High => Low

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

Title:
  [Scopes] Suru Background should scroll

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  On the dash, the Suru paper folds stays fixed at the bottom, while it
  should rather scroll away.

  We should also 'tile' the background, so the paper fold is displayed
  again after scrolling a certain amount of vertical space.

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

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

[Touch-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files

2015-03-09 Thread selex

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

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

Title:
  ImageIO crashes (core dumped) while reading many image files

Status in OpenJDK:
  Invalid
Status in lcms2 package in Ubuntu:
  New
Status in openjdk-7 package in Ubuntu:
  Confirmed

Bug description:
  Code that uses ImageIO.read() to read many image files (on my system:
  270 files, totalling 522.9 MiB) crashes the JVM.

  ~~~ My system information:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 11.10
  Release:  11.10
  Codename: oneiric

  $ uname -a
  Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  $ javac -version
  javac 1.7.0_147

  $ java -version
  java version "1.7.0_147-icedtea"

  ~~~ To reproduce the error:

  $ javac BugIIO.java

  $ ulimit -c unlimited # to enable core dump

  $ java BugIIO

  ~~~ Terminal output that signifies the error:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752
  #
  # JRE version: 7.0_147-b147
  # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea7 2.0
  # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1
  # Problematic frame:
  # C  [liblcms2.so.2+0x121f8]  cmsSaveProfileToIOhandler+0x38
  #
  # Core dump written. Default location: /home/joshua/core or core.4978
  #
  # An error report file with more information is saved as:
  # /home/joshua/hs_err_pid4978.log
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  #
  Dibatalkan (core didump)

  ~~~ PS
  When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the 
program finishes normally (no crash).

  To clarify:
  1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on 
oneiric).
  2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested 
on oneiric).

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

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

[Touch-packages] [Bug 1428087] Re: Need (some) Autopilot tests to run in different orientations

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/orientationManual

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

Title:
  Need (some) Autopilot tests to run in different orientations

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

Bug description:
  We've had regressions in behavior and at least one crash recently due
  to the lack of testing under different orientations. Evidently even
  manual testing doesn't cover basic use cases judging by the nature of
  those issues - which may be in part due to development images
  receiving less QA attention, which makes it even more problematic.

  1. We need ways to execute Autopilot tests under different orientations.
  2. A test needs to be able to change orientation mid-way.

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

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

[Touch-packages] [Bug 1429822] [NEW] Cannot examine bug locally: apport-retrace is not installed

2015-03-09 Thread Ville Ranki

Public bug reported:

On a Ubuntu 14.10 system, when i try to examine bug locally i get error:

Failed to execute child process "apport-retrace" (No such file or
directory)

This is because package apport-retrace is not installed by default.

Suggested solution: ask "apport-retrace is needed but is not installed. Install 
it?" from user
and continue after it has been installed.

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

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

Title:
  Cannot examine bug locally: apport-retrace is not installed

Status in apport package in Ubuntu:
  New

Bug description:
  On a Ubuntu 14.10 system, when i try to examine bug locally i get
  error:

  Failed to execute child process "apport-retrace" (No such file or
  directory)

  This is because package apport-retrace is not installed by default.

  Suggested solution: ask "apport-retrace is needed but is not installed. 
Install it?" from user
  and continue after it has been installed.

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

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

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

2015-03-09 Thread James Hunt

It does indeed seem to be related to the kernel. I've just run that
specific test 77 times on an amd64 system running a 3.18.0-11 kernel
with no failures. Once the broken deps issue is resolved, I'll retest on
the same system running the latest 3.19 kernel.

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

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

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

[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting

2015-03-09 Thread Lars Uebernickel

I have the same issue. Attaching my fstab and crypttab.

** Attachment added: "fstab"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338777/+files/fstab

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

Title:
  Systemd takes very long to boot with error in swap mounting

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My system boots almost instantly with upstart. Today i tried booting with 
systemd via the additional grub option.
  However, with systemd it takes really long to boot but – so long that i 
forced a reboot once because i thought i got stuck.

  Looking in to boot journal, i found the following error concerning the swap:
  Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, 
code=exited status=255
  Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition.
  Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state.

  And this concerning nvidia-persistenced
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433)
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA 
devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and 
that user 116 has read and write permissions for thos
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced

  I checked that /dev/sda3 exists and is a swap partition and i check for the 
/dev/nvidia files:
  $ ls -Alst /dev/nvidia0
  0 crw-rw-rw- 1 root root 195, 0 Mär  7 09:29 /dev/nvidia0

  However, the interesting part is here, where nothing seems to happen for a 
minute: (see the timestamps):
  Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization.
  Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 timed out.
  Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap.
  Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 
'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes.
  Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with 
result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 failed with result 'timeout'.
  Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  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.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  7 09:31:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-05 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 
init=/lib/systemd/systemd systemd.debugshell
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: H97 Performance
  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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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

[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting

2015-03-09 Thread Lars Uebernickel

** Attachment added: "crypttab"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338779/+files/crypttab

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

Title:
  Systemd takes very long to boot with error in swap mounting

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My system boots almost instantly with upstart. Today i tried booting with 
systemd via the additional grub option.
  However, with systemd it takes really long to boot but – so long that i 
forced a reboot once because i thought i got stuck.

  Looking in to boot journal, i found the following error concerning the swap:
  Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, 
code=exited status=255
  Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition.
  Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state.

  And this concerning nvidia-persistenced
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433)
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA 
devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and 
that user 116 has read and write permissions for thos
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced

  I checked that /dev/sda3 exists and is a swap partition and i check for the 
/dev/nvidia files:
  $ ls -Alst /dev/nvidia0
  0 crw-rw-rw- 1 root root 195, 0 Mär  7 09:29 /dev/nvidia0

  However, the interesting part is here, where nothing seems to happen for a 
minute: (see the timestamps):
  Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization.
  Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 timed out.
  Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap.
  Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 
'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes.
  Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with 
result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 failed with result 'timeout'.
  Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  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.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  7 09:31:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-05 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 
init=/lib/systemd/systemd systemd.debugshell
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: H97 Performance
  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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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.

To manage noti

[Touch-packages] [Bug 1424864] Re: Xorg crash

2015-03-09 Thread Galen Thurber

dmesg reports this after being kicked out back to login manager
[27339.253612] NVRM: Xid (0002:00): 5, Ch  M 032c D 00024040 intr 
0100

and the bug is happening under kernel
3.2.0-76-generic 
as well

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashing out & back into login manager
  and apport failed 
  This problem report is damaged and cannot be processed.

  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is
  truncated: expected core file size >= 75243520, found: 6356992.',)

  
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...

  (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **:
  g_variant_new_string: assertion `string != NULL' failed

  (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **:
  Failed to register client:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations

  
  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32:
  assertion `G_IS_FILE_INFO (info)' failed

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: 
assertion `G_IS_FILE_INFO (info)' failed
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Mon Feb 23 19:14:16 2015
  InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140205)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting

2015-03-09 Thread Lars Uebernickel

** Attachment added: "udevadm"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429354/+attachment/4338780/+files/udevadm

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

Title:
  Systemd takes very long to boot with error in swap mounting

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My system boots almost instantly with upstart. Today i tried booting with 
systemd via the additional grub option.
  However, with systemd it takes really long to boot but – so long that i 
forced a reboot once because i thought i got stuck.

  Looking in to boot journal, i found the following error concerning the swap:
  Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, 
code=exited status=255
  Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition.
  Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state.

  And this concerning nvidia-persistenced
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433)
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA 
devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and 
that user 116 has read and write permissions for thos
  Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced

  I checked that /dev/sda3 exists and is a swap partition and i check for the 
/dev/nvidia files:
  $ ls -Alst /dev/nvidia0
  0 crw-rw-rw- 1 root root 195, 0 Mär  7 09:29 /dev/nvidia0

  However, the interesting part is here, where nothing seems to happen for a 
minute: (see the timestamps):
  Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization.
  Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 timed out.
  Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 
messages.
  Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap.
  Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 
'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start 
failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes.
  Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with 
result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  Mär 07 09:29:29 darw1n systemd[1]: Job 
dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start
 failed with result 'timeout'.
  Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  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.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  7 09:31:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-05 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 
init=/lib/systemd/systemd systemd.debugshell
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: H97 Performance
  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.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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.

To manage notifi

[Touch-packages] [Bug 1429838] [NEW] Some (internal) test programs should be split up and filenames are not consistent

2015-03-09 Thread Tim Peeters

Public bug reported:

The various tests in tests/resources/navigation/header.html should be
put in separate files to make them easier to read and maintain. Also a
the filenames in tests/resources/* and some unit tests are not
consistent (use different capitalizations, and/or underscores in
filenames).

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Low
 Assignee: Tim Peeters (tpeeters)
 Status: In Progress

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Medium => Low

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

Title:
  Some (internal) test programs should be split up and filenames are not
  consistent

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

Bug description:
  The various tests in tests/resources/navigation/header.html should be
  put in separate files to make them easier to read and maintain. Also a
  the filenames in tests/resources/* and some unit tests are not
  consistent (use different capitalizations, and/or underscores in
  filenames).

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

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

[Touch-packages] [Bug 1422762] Re: Camera should not change behavior when rotation lock is on

2015-03-09 Thread Florian Boucault

** Changed in: camera-app (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: camera-app
   Status: New => In Progress

** Changed in: camera-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  Camera should not change behavior when rotation lock is on

Status in Camera App:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  (from mailing list)

  On Bq 4.5 running RTM r17

  1) enable screen rotation lock
  2) take a photo horizontally
  3) disable screen rotation lock
  4) rotate the phone in any way, the photo is rotated incorrectly, as
  if it was originally taken vertically

  I think that the camera application should ignore the rotation lock or
  at least, implant the actual (correct) orientation into the taken
  photo.

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

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

[Touch-packages] [Bug 1424864] Re: Xorg crash

2015-03-09 Thread Galen Thurber

apport-collect does not work for current vivid

Linux ubuntu 3.19.0-7-generic #7-Ubuntu SMP Thu Feb 26 20:19:34 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ apport-collect
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
ubuntu@ubuntu:~$ apport-bug

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashing out & back into login manager
  and apport failed 
  This problem report is damaged and cannot be processed.

  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is
  truncated: expected core file size >= 75243520, found: 6356992.',)

  
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...

  (polkit-gnome-authentication-agent-1:9183): GLib-CRITICAL **:
  g_variant_new_string: assertion `string != NULL' failed

  (polkit-gnome-authentication-agent-1:9183): polkit-gnome-1-WARNING **:
  Failed to register client:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations

  
  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32:
  assertion `G_IS_FILE_INFO (info)' failed

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: 
assertion `G_IS_FILE_INFO (info)' failed
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Mon Feb 23 19:14:16 2015
  InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140205)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429383] Re: The keyboard doesn't appear

2015-03-09 Thread Michael Sheldon

Hi Marcel, thanks for reporting this; I've just flashed image 125 and
haven't been able to reproduce this. Is there a crash file in /var/crash
beginning with the name "_usr_bin_maliit-server"? If so could you attach
that file to this bug report? Also, which keyboard layouts do you have
enabled?

Thanks!

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Incomplete

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

Title:
  The keyboard doesn't appear

Status in ubuntu-keyboard package in Ubuntu:
  Incomplete

Bug description:
  Device: mako (NEXUS 4)
  System: 15.04 r125

  I have no keyboard after update this morning!!!

  Clicking in a textfield: The cursor comes, but no textfield.

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

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

[Touch-packages] [Bug 1311706] Re: XU 12.04-4 dual display not working nvidia 173 on nv34 card

2015-03-09 Thread Galen Thurber

12.04.05 LTS is now EOL
that is odd news

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

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

Title:
  XU 12.04-4 dual display not working nvidia 173 on nv34 card

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  hoping to get Precise Pangolin 12.04 LT Xubuntu running dual displays, on VGA 
(CRT) the other smart tv via HDMI.
  as soon as xu goes to login screen I lose DVI to HDMI connection.
  Other distros, sparky, mint, puppy all work fine with dual display

  I run nvidia 173 on a nv34 video card
  /0/100/b/0  display NV34 [GeForce FX 5200]
  /0/100/ebridge  nForce3 250Gb PCI-to-PCI Bridge
  3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
  nvidia config does not show a second display

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

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

[Touch-packages] [Bug 1429838] Re: Some (internal) test programs have too much messy code and filenames are not consistent

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/cleanHeaderTests

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

Title:
  Some (internal) test programs should be split up and filenames are not
  consistent

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

Bug description:
  The various tests in tests/resources/navigation/header.html should be
  put in separate files to make them easier to read and maintain. Also a
  the filenames in tests/resources/* and some unit tests are not
  consistent (use different capitalizations, and/or underscores in
  filenames).

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

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

[Touch-packages] [Bug 1428272] Re: Recording video with rotation lock on results in aspect ratio error in resultant video file

2015-03-09 Thread Florian Boucault

** Changed in: camera-app
   Status: Confirmed => In Progress

** Changed in: camera-app (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: camera-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

Title:
  Recording video with rotation lock on results in aspect ratio error in
  resultant video file

Status in Camera App:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Found on the Krillin...

  If you record video with Rotation Lock 'On' the resulting video file
  is squashed on playback.

  Steps to reproduce.

   - Set rotation lock on

  - record a video in the camera app while holding the phone in
  landscape mode).

  - playback the video

  Result:

  - the video is played back but it is 'squashed' horizontally.

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

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

[Touch-packages] [Bug 1429840] [NEW] Sound - HDA-Intel - HDA ATI SB - 5.1 wont work

2015-03-09 Thread Nikolay

Public bug reported:

About 1 week ago i have installed Ubuntu 14.04.2 LTS for a lightweight
Ruby studying,i also have a 5.1 speaker system wich fully-
exploitable,but linux wont use all speakers fine -  in despite of all
speakers connected,linux see only front right and left speakers whatever
i do.

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

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

Title:
  Sound - HDA-Intel - HDA ATI SB - 5.1 wont work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  About 1 week ago i have installed Ubuntu 14.04.2 LTS for a lightweight
  Ruby studying,i also have a 5.1 speaker system wich fully-
  exploitable,but linux wont use all speakers fine -  in despite of all
  speakers connected,linux see only front right and left speakers
  whatever i do.

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

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

[Touch-packages] [Bug 1429838] Re: Some (internal) test programs should be split up and filenames are not consistent

2015-03-09 Thread Tim Peeters

** Summary changed:

- Some (internal) test programs have too much messy code and filenames are not 
consistent
+ Some (internal) test programs should be split up and filenames are not 
consistent

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

Title:
  Some (internal) test programs should be split up and filenames are not
  consistent

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

Bug description:
  The various tests in tests/resources/navigation/header.html should be
  put in separate files to make them easier to read and maintain. Also a
  the filenames in tests/resources/* and some unit tests are not
  consistent (use different capitalizations, and/or underscores in
  filenames).

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

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

dino99: I guess plymouth wasn't running for you when fsck started,
right?

I conditioned the fact that the messages are sent to plymouth if the pid
file is present (see http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029174.html)

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

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

-- 
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:
  In Progress

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 1411140] Re: systemd-machine-id-commit.service fails on live system

2015-03-09 Thread Didier Roche

Fix proposed at http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029163.html

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

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

Title:
  systemd-machine-id-commit.service fails on live system

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Boot the current live system with systemd: Go to gfxboot, select F6,
  press Esc twice, stay in gfxboot, and append init=/bin/systemd to the
  command line. The live system will come up, but degraded:

  ● systemd-machine-id-commit.service - Commit a transient machine-id on disk
 Loaded: loaded (/lib/systemd/system/systemd-machine-id-commit.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2015-01-15 08:08:47 UTC; 1min 
57s ago
   Docs: man:systemd-machine-id-commit.service(8)
Process: 871 ExecStart=/lib/systemd/systemd-machine-id-commit (code=exited, 
status=1/FAILURE)
   Main PID: 871 (code=exited, status=1/FAILURE)

  Jan 15 08:08:47 ubuntu systemd[1]: Starting Commit a transient machine-id on 
disk...
  Jan 15 08:08:47 ubuntu systemd[1]: systemd-machine-id-commit.service: main 
process exited, code=exited, status=1/FAILURE
  Jan 15 08:08:47 ubuntu systemd[1]: Failed to start Commit a transient 
machine-id on disk.
  Jan 15 08:08:47 ubuntu systemd[1]: Unit systemd-machine-id-commit.service 
entered failed state.
  Jan 15 08:08:47 ubuntu systemd[1]: systemd-machine-id-commit.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 15 09:06:46 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (55 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
  MachineType: LENOVO 2324CTO
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 718635] Re: Error message "Your computer does not have enough free memory" when core dump or stacktrace failed to be created is misleading

2015-03-09 Thread Simon Reed

I got this running warzone2100 (at the very end of the campaign, BTW).
I am using 4.5GB of my 7.8GB available and using 120KB of my 16GB swap
file.

Xubuntu 14.04

Linux simonX64 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux

(Incidentally, I re-loaded the last saved game, finished the campaign
again and there was no crash.)

** Attachment added: "InsufficientMemory_crash.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+attachment/4338791/+files/InsufficientMemory_crash.png

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

Title:
  Error message "Your computer does not have enough free memory" when
  core dump or stacktrace failed to be created is misleading

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  On Unity fully updated, when I login there is a X crash (attached), an apport 
dialog is displayed but complains about:
  ---
  Sorry, the program "Xorg" closed unexpectedly

  Your computer does not have enough free memory to automatically analyze the 
problem and send a report to the developers.
  ---

  You can only close and the report is canceled.

  Of course there's enough memory

  This message is displayed when the core dump or stacktrace can't be
  attached to the report. This should be changed to something closer to
  the real issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.17.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
  Uname: Linux 2.6.38-3-generic i686
  ApportLog:
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741, 
signal 6
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg 
(command line "/usr/bin/X :0 -br -verbose -auth 
/var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7")
  Architecture: i386
  Date: Mon Feb 14 10:54:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US.UTF-8:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_AG.utf8
   SHELL=/bin/bash
  SourcePackage: apport

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

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

[Touch-packages] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic

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

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

Title:
  libosmesa6 conflicts with libglapi-mesa-lts-utopic

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

Bug description:
  [Description]
  libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on 
libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic 
10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not '10.1.3-0ubuntu0.3'.

  [Test Case]
  >sudo aptitude install libosmesa6
  The following NEW packages will be installed:
    libglapi-mesa{a} libosmesa6
  0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,009 kB of archives. After unpacking 3,682 kB 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.
   libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is 
to be installed.

  [Possible solution]
  Include utopic's libosmesa(-dev) in the LTS enablement stack, so versions 
match.

  [Reverse dependencies]
  libosmesa6-dev
  desmume
  crossover
  wine recommends libosmesa6
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 15:45:52 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.5
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.5
  InstallationDate: Installed on 2015-02-08 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: mesa-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1429852] [NEW] It is much too hard to file a bug report

2015-03-09 Thread Tilman Bohl

Public bug reported:

Usability issue: the process of filing a bug report is too hard.

Steps to reproduce:

Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:

(0) look through the application's menus, no hints there how to file a
bug

(1) google how to report a bug, get told to create an account, click through 3 
pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/

(2) wait for verification email

(3) re-type password four 4 times in total

(4) get redirected to the ubuntu-bug utility, which opens up the gnome image 
viewer instead of doing anything useful
(go try it on a fresh install: 
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)

(5) figure out that ubuntu-bug is a command line utility

(6) figure out which command line command corresponds to your
application

(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r  /usr/bin/gnucash /var/lib/dpkg/info/

(8) run it: $ubuntu-bug gnucash

(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid

(10) retype password, fifth time

(11) Type in bug summary (rejoice, finally!)

(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.

(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)

(14) Type in the problem report in this very form here.

Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.

Observed behavior: Lots of time spent on the above procedure. Do you
have a way of knowing how many users give up?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
 664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 
17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
 640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 
17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
 640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 
09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
 600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 
20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar  9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

** Description changed:

  Usability issue: the process of filing a bug report is so convoluted
  that most users' goodwill is depleted along the way.
  
  Steps to reproduce:
  
  Imagine your desktop application (e.g. gnucash) is misbehaving, and you
- want to help Ubuntu. These are the hoops you have to jump through:
+ want to help Ubuntu. These are the steps for a first time bug report:
  
  (0) look through the application's menus, no hints there how to file a
  bug
  
- (1) google how to report a bug, click through 3 pages and lots of text
+ (1) google how to report a bug, get told to create an account, click through 
3 pages and lots of text
  https://help.ubuntu.com/community/ReportingBugs
  https://help.launchpad.net/YourAccount/NewAccount
  https://login.launchpad.net/
  
  (2) wait for verification email
  
  (3) re-type password four 4 times in total
  
- (4) get redirected to the ubuntu-bug utility, which opens up the gnome image 
viewer instead of doing anything useful 
+ (4) get redirected to the ubuntu-bug utility, which opens up the gnome image 
viewer instead of doing anything useful
  (go try it on a fresh install: 
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
  
- (5) figure out ubuntu-bug is a command line utility
+ (5) figure out that ubuntu-bug is a command line utility
  
  (6) figure out which command line command corresponds to your
  application
  
  (7) figure out which package contains your desktop application:
  $ which gnucash
  $ grep -r  /usr/bin/gnucash /v

[Touch-packages] [Bug 1428277] Re: Icon in notification center too small

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

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New => Confirmed

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

Title:
  Icon in notification center too small

Status in Libqtelegram - a qt library to access telegram.:
  Invalid
Status in Ubuntu UX bugs:
  New
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  See image attached. The tappable telegram icon is somewhat small and
  is not trivial to tap, or at least I'm not being able to tap it in a
  way it works in a single tap.

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

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

[Touch-packages] [Bug 1428277] Re: Icon in notification center too small

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

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

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

Title:
  Icon in notification center too small

Status in Libqtelegram - a qt library to access telegram.:
  Invalid
Status in Ubuntu UX bugs:
  New
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  See image attached. The tappable telegram icon is somewhat small and
  is not trivial to tap, or at least I'm not being able to tap it in a
  way it works in a single tap.

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

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

[Touch-packages] [Bug 1428277] Re: Icon in notification may be too small

2015-03-09 Thread Michał Sawicz

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

** Summary changed:

- Icon in notification may be too small
+ Icon in notification center too small

** Description changed:

- See image attached. Icon is somewhat small and is not trivial to tap, or
- at least I'm not being able to tap it in a way it works in a single tap.
+ See image attached. The tappable telegram icon is somewhat small and is
+ not trivial to tap, or at least I'm not being able to tap it in a way it
+ works in a single tap.

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

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

** Also affects: ubuntu-settings-components (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Icon in notification center too small

Status in Libqtelegram - a qt library to access telegram.:
  Invalid
Status in Ubuntu UX bugs:
  New
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  See image attached. The tappable telegram icon is somewhat small and
  is not trivial to tap, or at least I'm not being able to tap it in a
  way it works in a single tap.

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

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

[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()

2015-03-09 Thread Christopher Townsend

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => In Progress

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

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

Title:
  indicator-location-service crashed with SIGABRT in
  internal::ToBackend::exit_module()

Status in indicator-location package in Ubuntu:
  Confirmed
Status in platform-api package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb  5 06:11:38 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service
  InstallationDate: Installed on 2014-10-13 (117 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141012)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: indicator-location
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ua_location_service_create_controller () from 
/usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   UbuntuAppLocController::UbuntuAppLocController() ()
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Title: indicator-location-service crashed with SIGABRT in 
ua_location_service_create_controller()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1428184] Re: Invisible mouse pointer after resume from suspend

2015-03-09 Thread UserError

Hi,
I'm getting this on Xubuntu 14.04 on a Thinkpad T60p..

Mouse works, cursor not visible after closing the lid for a while.

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

Title:
  Invisible mouse pointer after resume from suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Samsung NP305U1A-A05CO laptop. After the computer is
  suspended, either by closing the lid, choosing the option on the menu
  or by itself after the defined time, and then when I wake the computer
  the mouse pointer is invisible, however the hardware itself is working
  as mouse position and clicks continue working, only the pointer is
  invisible.

  WORKAROUND: If I switch to a console with Alt+Shit+F1 and switch back
  to X with Alt+Shift+F7 the mouse pointer appears and is back to
  normal.

  WORKAROUND: After installing fglrx 14.50.2 proprietary AMD driver
  (doing the modification explained in
  http://askubuntu.com/a/543836/378463 to avoid ocl-icd-libopencl1/wine
  conflict) including the Catalyst Control Center, the problem is
  resolved and now I can suspend and resume the computer and the mouse
  pointer is visible after wake up as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Wed Mar  4 10:08:23 2015
  InstallationDate: Installed on 2015-02-12 (20 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()

2015-03-09 Thread Ricardo Mendoza

** Branch linked: lp:~ricmm/platform-api/no-abort-default-dummy

** Changed in: platform-api (Ubuntu)
 Assignee: (unassigned) => Ricardo Mendoza (ricmm)

** Changed in: unity8-desktop-session (Ubuntu)
 Assignee: (unassigned) => Ricardo Mendoza (ricmm)

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

Title:
  indicator-location-service crashed with SIGABRT in
  internal::ToBackend::exit_module()

Status in indicator-location package in Ubuntu:
  Confirmed
Status in platform-api package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb  5 06:11:38 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service
  InstallationDate: Installed on 2014-10-13 (117 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141012)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: indicator-location
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ua_location_service_create_controller () from 
/usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   UbuntuAppLocController::UbuntuAppLocController() ()
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Title: indicator-location-service crashed with SIGABRT in 
ua_location_service_create_controller()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting