date:20150319

Seems possibly to be what I predicted:
https://bugs.launchpad.net/mir/+bug/1415321/comments/3

ldd bin/.mir_demo_client_eglsquare-uninstalled
libmirclient.so.8 => ./lib/libmirclient.so.8 (0x7f58fa14d000)
libmircommon.so.3 => /usr/lib/x86_64-linux-gnu/libmircommon.so.3 
(0x7f58f9ee2000)
libmircommon.so.4 => /home/dan/bzr/mir/dev/build/lib/libmircommon.so.4 
(0x7f58f8f7a000)

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

Title:
  [regression] Client ABI 8 broken in 0.13 series

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  I've just done a little sanity testing of our client ABI changes and
  found we've broken the client 8 ABI at least once, maybe twice in
  series 0.13.

  Test case:
1. Build two trees: r2307 and r2308.
2. Copy client demo binaries from r2307 and expect them to run in the r2308 
tree.

  Expected: client demos still run.
  Observed: client demos fail to start with:
  bin/.mir_demo_client_fingerpaint-uninstalled: relocation error: 
bin/.mir_demo_client_fingerpaint-uninstalled: symbol 
mir_surface_get_buffer_stream, version MIR_CLIENT_8 not defined in file 
libmirclient.so.8 with link time reference

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

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

[Touch-packages] [Bug 1434400] [NEW] [regression] Client ABI 8 broken in 0.13 series

Public bug reported:

I've just done a little sanity testing of our client ABI changes and
found we've broken the client 8 ABI at least once, maybe twice in series
0.13.

Test case:
  1. Build two trees: r2307 and r2308.
  2. Copy client demo binaries from r2307 and expect them to run in the r2308 
tree.

Expected: client demos still run.
Observed: client demos fail to start with:
bin/.mir_demo_client_fingerpaint-uninstalled: relocation error: 
bin/.mir_demo_client_fingerpaint-uninstalled: symbol 
mir_surface_get_buffer_stream, version MIR_CLIENT_8 not defined in file 
libmirclient.so.8 with link time reference

** Affects: mir
 Importance: Critical
 Status: In Progress

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


** Tags: regression

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

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

Title:
  [regression] Client ABI 8 broken in 0.13 series

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  New

Bug description:
  I've just done a little sanity testing of our client ABI changes and
  found we've broken the client 8 ABI at least once, maybe twice in
  series 0.13.

  Test case:
1. Build two trees: r2307 and r2308.
2. Copy client demo binaries from r2307 and expect them to run in the r2308 
tree.

  Expected: client demos still run.
  Observed: client demos fail to start with:
  bin/.mir_demo_client_fingerpaint-uninstalled: relocation error: 
bin/.mir_demo_client_fingerpaint-uninstalled: symbol 
mir_surface_get_buffer_stream, version MIR_CLIENT_8 not defined in file 
libmirclient.so.8 with link time reference

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

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

[Touch-packages] [Bug 1434402] [NEW] package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы

2015-03-19 Thread Gvadik

Public bug reported:

package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade:
зацикливание триггеров, отмена работы

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fontconfig 2.11.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
Date: Fri Mar 20 08:52:32 2015
ErrorMessage: зацикливание триггеров, отмена работы
InstallationDate: Installed on 2015-03-19 (0 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150225)
SourcePackage: fontconfig
Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: 
зацикливание триггеров, отмена работы
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade:
  зацикливание триггеров, отмена работы

Status in fontconfig package in Ubuntu:
  New

Bug description:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade:
  зацикливание триггеров, отмена работы

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fontconfig 2.11.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Fri Mar 20 08:52:32 2015
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2015-03-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150225)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: 
зацикливание триггеров, отмена работы
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434396] [NEW] Xserver does not start, on boot (low-graphics mode)

2015-03-19 Thread LGB [Gábor Lénárt]

Public bug reported:

After upgrading to (32bit) vivid I hadn't got any problem, but since a
day (daily upgraded) booting results in a dialog saying low graphics
mode and a dialog window about this. Choosing running in default mode
causes to boot splash to be shown forever. if I choose exit to console,
log in then service stop then start for lightdm, it works then though.
Maybe is not Xserver bug, but the new init system (systemd) race
condition of starting things, or such?

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.16.2-0ubuntu3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar 20 07:35:37 2015
DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21dd]
InstallationDate: Installed on 2012-03-03 ( days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: LENOVO 5016NW6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago)
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 5016NW6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5016NW6
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
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.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Mar 20 07:25:51 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9196 
 vendor AUO
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: apport-bug compiz-0.9 i386 ubuntu 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/1434396

Title:
  Xserver does not start, on boot (low-graphics mode)

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to (32bit) vivid I hadn't got any problem, but since a
  day (daily upgraded) booting results in a dialog saying low graphics
  mode and a dialog window about this. Choosing running in default mode
  causes to boot splash to be shown forever. if I choose exit to
  console, log in then service stop then start for lightdm, it works
  then though. Maybe is not Xserver bug, but the new init system
  (systemd) race condition of starting things, or such?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 20 07:35:37 2015
  DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Proce

[Touch-packages] [Bug 1430000] Re: [regression] mir_acceptance_tests.NestedServer failure in clang CI

Also, still happening locally with gcc:

The following tests FAILED:
 27 - mir_acceptance_tests.NestedServer.* (SEGFAULT)
Errors while running CTest
Makefile:117: recipe for target 'test' failed


** Changed in: mir
 Assignee: Alan Griffiths (alan-griffiths) => (unassigned)

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

Title:
  [regression] mir_acceptance_tests.NestedServer failure in clang CI

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

Bug description:
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1565/parameters/?
  and
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1567/parameters/?

  have both failed in: 
  Start  26: mir_acceptance_tests.NestedServer.*
   26/287 Test  #26: mir_acceptance_tests.NestedServer.* 
...***Exception: SegFault  0.25 sec

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

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

[Touch-packages] [Bug 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook

** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain

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

Title:
  boot script should run aa-profile-hook in addition to aa-clickhook

Status in Snappy Ubuntu:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Summary says it all. aa-profile-hook does the same sort of thing as
  aa-clickhook and is used on snappy.

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

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

[Touch-packages] [Bug 1434379] [NEW] GPS always active when a scope that uses location is in the background

2015-03-19 Thread Ricardo Salveti

Public bug reported:

current build number: 256
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-03-13 11:19:04
version version: 256
version ubuntu: 20150312
version device: 20150310-3201c0a
version custom: 20150216-561-29-186

(same for arale/vivid as well)

If you happen to have a scope that uses location data in background,
your GPS will always be active, doesn't matter what is in the
foreground.

This is a an issue with krillin (standard channel) as the main scope
(Today's) can easily on background when you're using other apps.

If you move to the apps scopes, then GPS will automatically be disabled,
and this won't happen (same for any other scope that doesn't use
location data).

This is only when the user is actively using the phone, as the GPS gets
automatically disabled once the screen turns off. And there is no
timeout at all, it stays there until you move to another scope or turn
off the screen.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

** Also affects: canonical-devices-system-image
   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/1434379

Title:
  GPS always active when a scope that uses location is in the background

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

Bug description:
  current build number: 256
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-13 11:19:04
  version version: 256
  version ubuntu: 20150312
  version device: 20150310-3201c0a
  version custom: 20150216-561-29-186

  (same for arale/vivid as well)

  If you happen to have a scope that uses location data in background,
  your GPS will always be active, doesn't matter what is in the
  foreground.

  This is a an issue with krillin (standard channel) as the main scope
  (Today's) can easily on background when you're using other apps.

  If you move to the apps scopes, then GPS will automatically be
  disabled, and this won't happen (same for any other scope that doesn't
  use location data).

  This is only when the user is actively using the phone, as the GPS
  gets automatically disabled once the screen turns off. And there is no
  timeout at all, it stays there until you move to another scope or turn
  off the screen.

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

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

[Touch-packages] [Bug 1430000] Re: [regression] mir_acceptance_tests.NestedServer failure in clang CI

Still happening with r2409. The fix supposedly landed in r2403.

https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-
amd64-build/1726/consoleFull

** Changed in: mir
   Status: Fix Committed => Triaged

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

Title:
  [regression] mir_acceptance_tests.NestedServer failure in clang CI

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

Bug description:
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1565/parameters/?
  and
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1567/parameters/?

  have both failed in: 
  Start  26: mir_acceptance_tests.NestedServer.*
   26/287 Test  #26: mir_acceptance_tests.NestedServer.* 
...***Exception: SegFault  0.25 sec

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

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

[Touch-packages] [Bug 951929] Re: Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

2015-03-19 Thread Paul Graydon

Can't say for sure if it's a problem any more or not.  I've long since
given up on Unity, in no small part due to this bug.  The response on
the bug report did little to convince me it was worth continuing to use
it either.  A whole bunch of people experiencing it, and the bug just
constantly being punted off to the next milestone.

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

Title:
  Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  edit: Updated title, its affecting more than gnome-terminal

  1) Description:   Ubuntu precise (development branch)
  Release:  12.04

  2) unity:
    Installed: 5.4.0-0ubuntu2

  3) Gnome-Terminal to show in list of programs to alt+tab to.

  4)  Alt+Tab consistently fails to show gnome-terminal for 'a while' (I
  hate to be vague, I can't figure out what suddenly triggers it to
  appear in the box).  See attached photograph of it occurring.

  I can make it happen at will:

  1) Cold boot into Ubuntu.
  2) Open gnome-terminal.
  3) Open Firefox.
  4) Press alt+tab.  alt+tab window only shows Desktop and Firefox.

  In attached screenshot, note that gnome-terminal has a highlighted
  background and arrow, indicating an instance of it running, as is
  Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sat Mar 10 14:50:09 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 940721] Re: ffmpeg goes berserk when trying to convert this video to mjpeg

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

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

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

Title:
  ffmpeg goes berserk when trying to convert this video to mjpeg

Status in libav package in Ubuntu:
  Expired

Bug description:
  I have a 3gp video of 20 seconds, 10 fps, 480x640 resolution, h264 codec, for 
a file size of about 4 MB; I tried the following command:
  ffmpeg -i VIDEO0024.3gp -vcodec mjpeg -s 300x400 -qmin 0.8 -qmax 0.8 
VIDEO0024.mov
  After several minutes, ffmpeg had processed more than 145357 frames, reported 
a time of 1.62 seconds, had written more than one GIGABYTE of output and was 
still working. I obviously killed it.
  The exactly same command has worked just fine with other video files encoded 
with other codecs.

  I think the problem is that for some reason it by default uses an
  output framerate of about 9 fps. Adding -r 10 for the output fixes
  the issue. But it is still an issue: according to documentation the
  default framerate is 30fps, anyway 9 is certainly not a reasonable
  default.

  I erroneously reported this in the FFmpeg bugtracker and they say it's
  probably fixed in FFmpeg.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: ffmpeg 4:0.7.3-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Feb 25 01:49:11 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (79 days ago)

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

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

[Touch-packages] [Bug 1308607] Re: avconv uses only 1 core Ubuntu 13.10

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

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

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

Title:
  avconv uses only 1 core Ubuntu 13.10

Status in libav package in Ubuntu:
  Expired

Bug description:
  I tried to get a movie transcoded with libx264 and libvorbis instead
  of AC3-DTS but avconv is not using all 4 cores of my computer. The
  original file has the video track plus three audio tracks, one in DTS-
  HD MA, one in DTS and the last one in AC3.

  My command line is this:

  avconv -i MOVIE.mkv -map 0:0 -codec:v libx264 -pass 1 -threads 6
  -coder:v ac -g 240 -keyint_min 23 -bf:v 16 -b_strategy 2 -b-bias 0
  -refs 3 -b:v 11000k -partitions p8x8,b8x8,i8x8,i4x4 -mixed-refs 1
  -me_range:v 20 -me_method:v umh -subq 8 -b-pyramid strict -8x8dct 1
  -direct-pred 1 -weightb 1 -weightp 2 -deblock 0:0 -an -f rawvideo -y
  /dev/null ;

  avconv -i MOVIE.mkv -map 0 -map -0:2 -map -0:3 -codec:s copy -codec:v
  libx264 -pass 2 -threads 6 -coder:v ac -g 240 -keyint_min 23 -bf:v 16
  -b_strategy 2 -b-bias 0 -refs 3 -b:v 11000k -partitions
  p8x8,b8x8,i8x8,i4x4 -mixed-refs 1 -me_range:v 20 -me_method:v umh
  -subq 8 -b-pyramid strict -8x8dct 1 -direct-pred 1 -weightb 1 -weightp
  2 -deblock 0:0 -acodec libvorbis -async 1 -b:a:0 640k -metadata:s:a:0
  title="arc Vorbis 640k 5.1" OUTPUT-MOVIE.mkv

  I tried to do a 1 pass encode with the second pass command (without
  the -pass 2 option) for testing purposes and it didn't use more than 1
  core (total load of avconv remained ~130%, I assume it's 100% of
  libx264 plus some processing for the audio). At times it went up near
  400% but it never didn't stay at full load, most of the time (99% of
  the time) was spent on ~130%. I've also tried with -threads auto,
  -threads 0, -threads 4 but no luck.

  I'm using the avconv available in Ubuntu 13.10 repositories (I'm on
  Kubuntu 13.10): 6:0.8.10-0ubuntu0.13.10.1

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

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

[Touch-packages] [Bug 1290051] Re: avconv crashed with SIGSEGV in malloc_consolidate()

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

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

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

Title:
  avconv crashed with SIGSEGV in malloc_consolidate()

Status in libav package in Ubuntu:
  Expired

Bug description:
  avconv has crashed.

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy libav-tools 
  libav-tools:
Installed: 6:9.11-2ubuntu1
Candidate: 6:9.11-2ubuntu1
Version table:
   *** 6:9.11-2ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libav-tools 6:9.11-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar  9 10:59:27 2014
  ExecutablePath: /usr/bin/avconv
  InstallationDate: Installed on 2013-12-28 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131219)
  ProcCmdline: avconv -i 2014-03-08,\ Cultural\ Program\ at\ Home\ with\ 
Grandma.mp4 -threads 4 -s hd480 -vb 2048k -deadline best -f webm 2014-03-08,\ 
Cultural\ Program\ at\ Home\ with\ Grandma.mp4.webm
  SegvAnalysis:
   Segfault happened at: 0x7fc6523334d5 :   cmp
0x18(%rax),%r12
   PC (0x7fc6523334d5) ok
   source "0x18(%rax)" (0xdfd71a44a5d4f6c1) not located in a known VMA region 
(needed readable region)!
   destination "%r12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libav
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7fc652673760 ) at malloc.c:4165
   _int_malloc (av=0x7fc652673760 , bytes=9296) at malloc.c:3423
   _int_memalign (av=0x7fc652673760 , alignment=32, 
bytes=1459817819648927439, bytes@entry=9216) at malloc.c:4403
   _mid_memalign (alignment=32, bytes=9216, address=) at 
malloc.c:3106
   __posix_memalign (memptr=0x7fff4ec57cf8, alignment=18446744073709551615, 
size=140734514952320) at malloc.c:5016
  Title: avconv crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers

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

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

[Touch-packages] [Bug 1334291] Re: package libswscale-extra-2 (not installed) failed to install/upgrade: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libs

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

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

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

Title:
  package libswscale-extra-2 (not installed) failed to install/upgrade:
  libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not
  co-installable with libswscale-extra-2 which has multiple installed
  instances

Status in libav package in Ubuntu:
  Expired

Bug description:
  i do not undestand

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libswscale-extra-2 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  AptOrdering:
   libswscale-extra-2: Install
   libswscale-extra-2: Configure
   libavfilter-extra-2: Configure
  Architecture: amd64
  Date: Sat Jun 21 10:32:40 2014
  DpkgHistoryLog:
   Start-Date: 2014-06-21  10:32:39
   Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.79'
   Install: libswscale-extra-2:amd64 (9.13-0ubuntu0.14.04.1, automatic)
  DpkgTerminalLog:
   dpkg: error processing archive 
/var/cache/apt/archives/libswscale-extra-2_6%3a9.13-0ubuntu0.14.04.1_all.deb 
(--unpack):
libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not 
co-installable with libswscale-extra-2 which has multiple installed instances
  DuplicateSignature: package:libswscale-extra-2:(not 
installed):libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is 
not co-installable with libswscale-extra-2 which has multiple installed 
instances
  ErrorMessage: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) 
is not co-installable with libswscale-extra-2 which has multiple installed 
instances
  InstallationDate: Installed on 2013-05-24 (397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: libav
  Title: package libswscale-extra-2 (not installed) failed to install/upgrade: 
libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not 
co-installable with libswscale-extra-2 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (55 days ago)

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

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

[Touch-packages] [Bug 1429885] Re: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned

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

** Changed in: shared-mime-info (Ubuntu)
   Status: New => Confirmed

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

Title:
  package shared-mime-info 1.3-1 failed to install/upgrade: triggers
  looping, abandoned

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  I just ran the updater from terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: shared-mime-info 1.3-1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Mon Mar  9 16:49:17 2015
  DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-02-12 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150211)
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434030] Re: [HDA-Intel - HDA Intel, playback] No sound at all

2015-03-19 Thread Raymond

if your computer are desktop, pin default should be [Jack] Line Out at
Ext Rear


Node 0x0d [Pin Complex] wcaps 0x400181: Stereo
  Control: name="Speaker Jack", index=0, device=0
  Pincap 0x173f: IN OUT HP Detect Trigger ImpSense
Vref caps: HIZ 50 GRD 80
  Pin Default 0x01114010: [Jack] Speaker at Ext Rear
Conn = 1/8, Color = Green
DefAssociation = 0x1, Sequence = 0x0
  Pin-ctls: 0x40: OUT VREF_HIZ
  Unsolicited: tag=06, enabled=1
  Connection: 1
 0x02



sys/class/sound/hwC0D0/init_pin_configs:
0x0a 0x2221401f
0x0b 0x22a19020
0x0c 0x01119012
0x0d 0x01114010
0x0e 0x40f000f1
0x0f 0x01113011
0x10 0x01411130
0x11 0x40f000f2
0x15 0x9033012e
0x1b 0x40f000f3

/sys/class/sound/hwC0D0/driver_pin_configs:
0x0a 0x0221401f
0x0b 0x02a19020
0x0c 0x01a19020
0x0d 0x01114010
0x0e 0x408000f0
0x0f 0x01813022
0x10 0x074510a0
0x11 0x40c400f1
0x15 0x9037012e
0x1b 0x40e000f2

/sys/class/sound/hwC0D0/user_pin_configs:

/sys/class/sound/hwC0D0/init_verbs:


!!ALSA/HDA dmesg
!!--

[   16.051876] MPU-401 device not found or device busy
[   16.359747] snd_hda_intel :00:1b.0: irq 40 for MSI/MSI-X
[   16.416785] sound hdaudioC0D0: autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) 
type:speaker
[   16.416804] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   16.416817] sound hdaudioC0D0:hp_outs=1 (0xa/0x0/0x0/0x0/0x0)
[   16.416828] sound hdaudioC0D0:mono: mono_out=0x0
[   16.416838] sound hdaudioC0D0:dig-out=0x10/0x0
[   16.416848] sound hdaudioC0D0:inputs:
[   16.416860] sound hdaudioC0D0:  Front Mic=0xb
[   16.416873] sound hdaudioC0D0:  Rear Mic=0xc
[   16.416884] sound hdaudioC0D0:  Line=0xf
[   16.416894] sound hdaudioC0D0:  CD=0x15


seem pin fix not correct as you still got type:speaker instead of type:lineout

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=dea0a5095b5e21306a81c496567043798fac7815

** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu)

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

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
   Digital Output (SPDIF) Built-in Audio.

  No sound at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prestley   1493 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 19 16:24:34 2015
  InstallationDate: Installed on 2007-01-01 (2999 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prestley   1493 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: PI945GCM
  dmi.board.vendor: Kobian
  dmi.board.version: ECS
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Kobian
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd05/08/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: PI945GCM
  dmi.product.version: 1.X
  dmi.sys.vendor: Kobian

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

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

[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

OK, just assuming it was indeed fixed unless proven otherwise.

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

** Changed in: mir (Ubuntu)
   Status: Incomplete => Fix Released

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

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

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

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

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

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

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

Actually Robert slipped his proposed fix just in time into the 0.11.0
release. And the 0.12 branch inherits from that...


revno: 2287
tags: v0.11.0
committer: Robert Carr 
branch nick: 0.11
timestamp: Mon 2015-02-09 13:07:25 -0800
message:
  Cherrypick lp:~mir-team/mir/catch-exceptions-at-android-driver-boundary


Sadly, this bug was reported against the same release it's meant to be
fixed in. Although it's hard to tell what came first because the pre-
release with the bug and the apparent fix both occurred on the same day.

It's not yet clear if the bug is fixed in any branch yet.

** Changed in: mir
   Status: Fix Committed => Incomplete

** No longer affects: mir/0.12

** Changed in: mir
Milestone: 0.13.0 => 0.11.0

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

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

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

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

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

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

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

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

If it is fixed, then it was fix released in 0.11.0

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

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

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

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

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

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

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

2015-03-19 Thread timothymowens

I can confirm as well that lightdm v1.2.3-0ubuntu2.7 has indeed fixed
this issue for me.  Thank you for the quick turnaround!

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1427205] Re: indicator shows (dozens of) out of range access points

** Branch linked: lp:~mathieu-tl/network-manager/lp1431471

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

Title:
  indicator shows (dozens of) out of range access points

Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  current build number: 129
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-02 07:41:43
  version version: 129
  version ubuntu: 20150302
  version device: 20150210-95b6a9f
  version custom: 20150302

  TEST CASE:
  1. Enable Wifi
  2. Have a walk with the DUT outside in an area with lot of visible access 
points.
  3. Walk in and out of range of these access points.

  EXPECTED RESULT:
  After the walk only the access points that are in range are visible in the 
indicator

  ACTUAL RESULT:
  All the access points the device saw are listed in the indicator (up to 
several dozens)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20150217.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Mon Mar  2 14:02:40 2015
  InstallationDate: Installed on 2015-03-02 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150302-020203)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1427205] Re: indicator shows (dozens of) out of range access points

2015-03-19 Thread Mathieu Trudel-Lapierre

NM also lists these networks, so it's unlikely to be an indicator issue
after all. I'll mark it Incomplete for indicator for now. I have a fix
ready to test for NM in my PPA: ppa:mathieu-tl/nv-build. We can upload
this to a silo in the morning.

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

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

** Changed in: network-manager (Ubuntu)
   Importance: Low => High

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  indicator shows (dozens of) out of range access points

Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  current build number: 129
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-02 07:41:43
  version version: 129
  version ubuntu: 20150302
  version device: 20150210-95b6a9f
  version custom: 20150302

  TEST CASE:
  1. Enable Wifi
  2. Have a walk with the DUT outside in an area with lot of visible access 
points.
  3. Walk in and out of range of these access points.

  EXPECTED RESULT:
  After the walk only the access points that are in range are visible in the 
indicator

  ACTUAL RESULT:
  All the access points the device saw are listed in the indicator (up to 
several dozens)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20150217.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Mon Mar  2 14:02:40 2015
  InstallationDate: Installed on 2015-03-02 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150302-020203)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

Turns out, the suggested --setactivationskip option is not present in
Utopic, as Utopic comes with an LVM version which dates back to 2012
(2.02.98(2) (2012-10-15)), while the feature was implemented in 2013.

Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01).

Activation skip could be a nice workaround if it would be backported.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to "linux", but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues "vgchange -ay" before all the
  PVs come online. This makes sense.

  I already tried to set the "rootdelay" kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 686W1D28
  dmi.board.name: 6150M2MA
  dmi.board.vendor: WinFast
  dmi.board.version: FAB2.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: WinFast
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd0

Re: [Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator

2015-03-19 Thread Ricardo Salveti

On Thu, Mar 19, 2015 at 7:17 PM, Jim Hodapp <1378...@bugs.launchpad.net> wrote:
> Plan is to work on underlying background playlist support this next
> iteration, so this will be possible to re-enable in the next few weeks
> or so.

Right, can only land once the background playlist support is fully
implemented (too big for 14.09/RTM OTA).

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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

[Touch-packages] [Bug 1228575] Re: Slider's tooltip too small sometimes

2015-03-19 Thread Nekhelesh Ramananthan

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Nekhelesh Ramananthan (nik90)

** Branch linked: lp:~nik90/ubuntu-ui-toolkit/fix-slider-bubble-width

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

Title:
  Slider's tooltip too small sometimes

Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  I tried to reimplement Slider's formatValue function this way:

  function formatValue(v) {
  if (v < maximumValue / 3)
  return i18n.tr("Small")
  else if (v < maximumValue / 3 * 2)
  return i18n.tr("Midium")
  else return i18n.tr("Large")
  }

  Result: word "Medium" doesn't fit in tooltip.
  Solution: use something like 
  Math.max(STANDARD_WIDTH, innerLabel.contentWidth)

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

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

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

Got an interesting reply from the Red Hat LVM mailing list:
https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html

Haven't tested the suggestion yet.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to "linux", but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues "vgchange -ay" before all the
  PVs come online. This makes sense.

  I already tried to set the "rootdelay" kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 686W1D28
  dmi.board.name: 6150M2MA
  dmi.board.vendor: WinFast
  dmi.board.version: FAB2.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: WinFast
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr:
  dmi.product.name: 6150M2MA
  dmi.product.version: FAB2.0
  dmi.sys.vendor: WinFast

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

With the knowledge that the hang is caused by snapshots, some googling has 
brought up some duplicates:
https://bugs.launchpad.net/lvm2/+bug/360237
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645

It seems the issue was hanging around since 2009 or earlier.

In Trusty (or probably even earlier distros) it was possible to work
around by setting a sufficiently long rootdelay, and eventually all the
LVs in all VGs came online. But since Utopic, initrd gives up
altogether. No matter how long my rootdelay is, my 2nd VG never gets
activated after the snapshot came online in the 1st VG.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to "linux", but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues "vgchange -ay" before all the
  PVs come online. This makes sense.

  I already tried to set the "rootdelay" kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.vend

[Touch-packages] [Bug 1433382] Re: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback

2015-03-19 Thread Eric Peterson

Attached is the output of "lsusb -"

** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1433382/+attachment/4350374/+files/lsusb.txt

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

Title:
  [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling
  sounds using module-loopback

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I recently hooked up a SB X-Fi Surrount 5.1 Pro external sound card to
  my computer. It has a Line-In port which I wanted to use for playing
  audio from another computer. I enabled the loopback module like so:

 pactl load-module module-loopback

  And although I could then hear sound from Line-In, it was distorted by
  static, crackling sounds. I took the advice I found here:

 https://wiki.ubuntu.com/Audio/PositionReporting

  Making this change to /etc/pulse/default.pa:

 load-module module-udev-detect tsched=0

  After rebooting and again loading the loopback module, the playback
  was static-free. As instructed by the above webpage, I'm filing this
  bug to track the issue and suggested solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa62 irq 95'
 Mixer name : 'Realtek ALC898'
 Components : 'HDA:10ec0899,104384d8,0013'
 Controls  : 47
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'Pro'/'Creative Technology Ltd SB X-Fi Surround 5.1 Pro at 
usb-:00:1d.0-1.3, high '
 Mixer name : 'USB Mixer'
 Components : 'USB041e:3237'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 36'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Tue Mar 17 21:02:47 2015
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro successful
  Symptom_Card: GF114 HDMI Audio Controller - HDA NVidia
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 PRO
  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.:bvr1104:bd04/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx: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/alsa-driver/+bug/1433382/+subscriptions

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

[Touch-packages] [Bug 1415321] Re: [regression] Client functions residing in libmircommon

2015-03-19 Thread PS Jenkins bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.13.0

** Changed in: mir
   Status: In Progress => Fix Committed

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

Title:
  [regression] Client functions residing in libmircommon

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

Bug description:
  We seem to now have a bunch of client functions living in
  libmircommon:

  $ nm -D lib/libmircommon.so | grep ' mir_'
  00010287 T mir_event_get_close_surface_event
  0001012a T mir_event_get_input_event
  00010264 T mir_event_get_orientation_event
  00010241 T mir_event_get_prompt_session_event
  0001021e T mir_event_get_resize_event
  000101fb T mir_event_get_surface_event
  00010105 T mir_event_get_type
  0001038e T mir_event_ref
  000103c6 T mir_event_unref
  0002dae2 T mir_input_event_get_device_id
  0002dbea T mir_input_event_get_event_time
  0002dcf0 T mir_input_event_get_key_input_event
  0002e5b5 T mir_input_event_get_pointer_input_event
  0002e003 T mir_input_event_get_touch_input_event
  0002d9d8 T mir_input_event_get_type
  0002ddc9 T mir_key_input_event_get_action
  0002de1e T mir_key_input_event_get_key_code
  0002dfab T mir_key_input_event_get_modifiers
  0002de43 T mir_key_input_event_get_scan_code
  00010368 T mir_orientation_event_get_direction
  0002e6bb T mir_pointer_input_event_get_action
  0002e7d9 T mir_pointer_input_event_get_axis_value
  0002e733 T mir_pointer_input_event_get_button_state
  0002e68f T mir_pointer_input_event_get_modifiers
  00010342 T mir_prompt_session_event_get_state
  0001031c T mir_resize_event_get_height
  000102f6 T mir_resize_event_get_width
  000102aa T mir_surface_event_get_attribute
  000102d0 T mir_surface_event_get_attribute_value
  0002dfd7 T mir_touch_input_event_get_modifiers
  0002e1df T mir_touch_input_event_get_touch_action
  0002e453 T mir_touch_input_event_get_touch_axis_value
  0002e0dd T mir_touch_input_event_get_touch_count
  0002e0f7 T mir_touch_input_event_get_touch_id
  0002e349 T mir_touch_input_event_get_touch_tooltype

  I think this could cause serious risk to clients/toolkits that call
  them. As their symbol versions are no longer tied to the stable client
  ABI, but instead tied to the more volatile mircommon ABI.

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

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

[Touch-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

** Tags removed: verification-done

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1207935] Re: lightdm crashed with SIGSEGV in quit_timeout_cb()

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  lightdm crashed with SIGSEGV in quit_timeout_cb()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  ..

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.8-0ubuntu1
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 31 00:29:44 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2011-07-23 (738 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
   autologin-user=
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x40e47d:  movl   $0x0,0x20(%rax)
   PC (0x0040e47d) ok
   source "$0x0" ok
   destination "0x20(%rax)" (0xaaca) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-07-10 (19 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1069218] Re: users.conf doesn't match users.c

Still working with 1.2.3-0ubuntu2.7

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  users.conf doesn't match users.c

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The default users.conf provided by LightDM mentions a section [UserAccounts]. 
It should be [UserList].

  [Test Case]
  1. Check default installed users.conf
  Expected result:
  Should have a [UserList] section with all items available but disabled.
  Observed result:
  Have a [UserAccounts] section with all items available but disabled.

  [Regression Potential]
  Very low - just changing the default configuration file which has no active 
configuration items.

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

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

[Touch-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 995645] Re: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''

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

** This bug has been marked a duplicate of bug 1396213
   LVM VG is not activated during system boot

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

Title:
  udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
  vgchange -a y''

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Boot takes a long time during which the console reports:

  
  [  100.224928] device-mapper: table: 252:40: snapshot: Snapshot cow pairing 
for exception table handover failed
  udevd[617]: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm 
vgchange -a y'' [1148]

  udevd[617]: 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a
  y'' [1148] terminated by signal 9 (Killed)

  Then the boot stalls waiting to mount /usr and I have to use M to
  manually recover.

  When I get into the recovery shell, a read from
  /dev/rootvol_tmp/ubuntu_usr returns 0 bytes and I have to run
  "vgchange -a y" before I can get a read from that LV to return data.
  At that point I can drop out of the recovery shell and boot will
  continue.

  I have the following LVs on this system:

  # lvs
LV   VG  Attr   LSize   Origin  Snap%  Move Log 
Copy%  Convert
videodatavol -wn-ao 698.19g 
  
video_tmpdatavol -wi-a- 233.32g 
  
apt_archives rootvol_tmp -wi-a-   1.00g 
  
home rootvol_tmp -wi-ao   1.78g 
  
lucidrootvol_tmp -wi-a-   3.00g 
  
lucid_root   rootvol_tmp swi-a-   1.00g ubuntu_root  34.70  
  
lucid_usrrootvol_tmp swi-a-   5.00g ubuntu_usr   42.22  
  
lucid_varrootvol_tmp swi-a-   4.00g ubuntu_var   39.57  
  
myth-0.24_root   rootvol_tmp swi-a-   1.00g ubuntu_root  34.66  
  
myth-0.24_usrrootvol_tmp swi-a-   5.00g ubuntu_usr   35.68  
  
natty_root   rootvol_tmp swi-a- 500.00m ubuntu_root  49.99  
  
natty_usrrootvol_tmp swi-a-   2.49g ubuntu_usr   58.34  
  
swap rootvol_tmp -wi-ao 512.00m 
  
ubuntu_root  rootvol_tmp owi-ao 500.00m 
  
ubuntu_root-20111213 rootvol_tmp swi-a- 500.00m ubuntu_root  70.96  
  
ubuntu_root-20120209 rootvol_tmp swi-a- 500.00m ubuntu_root  70.95  
  
ubuntu_root-20120214 rootvol_tmp swi-a- 500.00m ubuntu_root  70.94  
  
ubuntu_root-20120220 rootvol_tmp swi-a- 500.00m ubuntu_root  70.93  
  
ubuntu_root-20120313 rootvol_tmp swi-a- 500.00m ubuntu_root  70.93  
  
ubuntu_root-20120319 rootvol_tmp swi-a- 500.00m ubuntu_root  70.90  
  
ubuntu_root-20120412 rootvol_tmp swi-a- 500.00m ubuntu_root  50.03  
  
ubuntu_usr   rootvol_tmp owi-ao   2.49g 
  
ubuntu_usr-20111213  rootvol_tmp swi-a-   2.49g ubuntu_usr   69.04  
  
ubuntu_usr-20120209  rootvol_tmp swi-a-   2.49g ubuntu_usr   68.64  
  
ubuntu_usr-20120214  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.79  
  
ubuntu_usr-20120220  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.52  
  
ubuntu_usr-20120313  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.41  
  
ubuntu_usr-20120319  rootvol_tmp swi-a-   2.49g ubuntu_usr   66.21  
  
ubuntu_usr-20120412  rootvol_tmp swi-a-   2.49g ubuntu_usr   65.69  
  
ubuntu_var   rootvol_tmp owi-ao   1.99g 
  

  That's probably more than most people, but certainly not enough to
  warrant an unbootable system I should not think.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CurrentDmesg:
   [  237.755758] NFSD: starting 90-second grace period
   [  256.877022] SysRq : Changing Loglevel
   [  256.880020] Loglevel set to 8
  CustomUdevRuleFiles: 85-alsa.rules 85-ifupdown.rules 85-mdadm.rules 
41-mythtv-permissions.rules
  Date: Sun May  6 17:02:19 2012
  MachineType: To Be Filled By O.E.M. To Be Filled By O

[Touch-packages] [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot

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

** This bug is no longer a duplicate of bug 995645
   udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm 
vgchange -a y''
** This bug has been marked a duplicate of bug 1396213
   LVM VG is not activated during system boot

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

Title:
  cannot boot root on lvm2 with (largish) snapshot

Status in lvm2 - Logical Volume Manager:
  Invalid
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  When running root-on-lvm2 with the root being part of a vg that
  contains snapshotted volume(s), booting may fail if the snapshot size
  (or fill rate) grows over a certain size.

  The kernel will only wait a certain amount of time until dropping to an 
initramfs-shell reporting 'Gave up waiting for root device' as the reason. The 
harddisk drive activity indicator will still show lots of disk access for some 
more time (minutes in out case). 
  'ps | grep lvm' reveals that 'lvchange -a y' is taking a long time to 
complete.
  Waiting for the disk activity to die down, and exiting the shell will allow 
the boot to resume normally.

  Can anybody explain *why* it could take that long - each and every time?
   DETAILS
  More specificly, my volume group contained an Intrepid root partition of 20Gb 
(15Gb filled). I created a snapshot of this (18Gb) in order to 'sandbox 
upgrade' to Jaunty beta. This I did. I was kind of surprised by the volume of 
changes on the snapshot: the snapshot was 53% full after upgrade (so about 9Gb 
of changed blocks vs. Intrepid). On reboot, I found out that the system would 
not reboot itself.

  I have spent a long time around various seemingly related bugs
  (#290153, #332270) for a cause until I found out the culprit myself. I
  have not been able to find any (lvm) documentation warning to the fact
  that lvm operations might take several minutes (?!) to complete on
  snapshotted volumes.

  At the very least this warrants a CAPITAL RED warning flag in the
  docs, IMHO: using large snapshots might render a system unbootable
  (remotely) with root on lvm. Manual intervention at console/serial is
  required!

  1. [untested] it doesn't matter whether the root volume is actually a 
snapshot or origin, as long as the volume group contains said snapshot (in my 
case, intrepid was on the origin and jaunty on tje snapshot; both systems 
failed boot with the same symptoms).
  2. [untested] if root volume is in a separate vg things might work ok 
(assuming activating several volume groups can be done in parallel)
  3. [partially tested: freshly snapshotted system booted ok] I suspect nothing 
is the matter with a snapshot sized 18Gb, unless it fills up ('exception 
blocks' get used). However there is not much use in a snapshot of 18Gb if you 
are only allowed to use small parts of it.
  4. [tested] as a side note, once booted, both systems were reasonably 
performant (at least in responsiveness)
  5. [tested] other volume groups in the same server did not suffer noticeable 
performance penalties even when the problematic one performed badly
  6. [tested] the performance was back to normal (acceptable), even though my 
40Gb Home lv still featured a (largely unaltered) snapshot of 5Gb/6% (in the 
_same_ volume group). This indicates that nothing special to be wrong/corrupted 
in the vg metadata.
  7. [tested] rebooting/shutting down seemed flawed when initiated from Jaunty 
(but it seems unrelated to me: Jaunty appears to use kexec for reboot, causing 
problems with my terminal display and harddisk spin-down as well)

  -- executed from the initramfs shell:
  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # takes several minutes to complete (disk light on 
continuously)
  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # again, same agony (continuous period of solid 
activity)

  /sbin/lvm lvremove vg/largish_snapshot

  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # only takes seconds

  Of course I made a backup of the data in the snapshot that I actually
  wanted to keep :)

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

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

[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

Still fixed in 1.2.3-0ubuntu2.7

** Tags removed: verification-needed

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

Title:
  Daemon end of session/greeter pipes not closed

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

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

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

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

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

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

[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook

2015-03-19 Thread Steve Beattie

Per discussion with Jamie on irc, aa-profile-hook is to be triggered
when the apparmor package or click-apparmor package (provider of aa-
profile-hook) is updated via the system image updater. It is *not*
necessary to run aa-profile-hook on updates to apparmor-easyprof-ubuntu
and apparmor-easyprof-ubuntu-snappy.

(I'm not sure what an update to apparmor-easyprof-ubuntu-snappy should
trigger, if anything; aa-clickhook perhaps?)

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

Title:
  boot script should run aa-profile-hook in addition to aa-clickhook

Status in Snappy Ubuntu:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Summary says it all. aa-profile-hook does the same sort of thing as
  aa-clickhook and is used on snappy.

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

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

[Touch-packages] [Bug 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook

2015-03-19 Thread Jamie Strandboge

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

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

Title:
  boot script should run aa-profile-hook in addition to aa-clickhook

Status in Snappy Ubuntu:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Summary says it all. aa-profile-hook does the same sort of thing as
  aa-clickhook and is used on snappy.

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

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

[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread apjjr

I just resumed from stand-by mode and counted 17 instances of dbus-
daemon running. It's been in and out of suspend mode a few times today.

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

Title:
Duplicate processes started after Resume of amd64 bit

Status in unity package in Ubuntu:
New

Bug description:
$ uname -a
Linux ajsc855 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

Toshiba Satellite C855, 4GB RAM, 720GB HD

I typically run Thunderbird, Firefox, a terminal or two, Gthumb, Gimp,
Qcad, Gedit, Libreoffice, Inkscape, Document Viewer and occasionally
Virtualbox.

I just noticed this a couple of weeks ago, so I am guessing a recent
update started it.

It seems to me that there are quite a few duplicate copies of some
processes populating memory after suspending/resuming a session for a
few days. Namely, dbus-daemon, gvfsd and gconfd-2. The more I
suspend/resume the session, the more of these processes appear. After
a while they start using up a significant amount of memory and system
response seems to slow down.

Logging out and back in did not alleviate the problem. Rebooting did.
But, I will have to reboot again in a week to free up the memory used
by these duplicate processes.

The example session used to get the following results was probably
well over a week in use.

Before rebooting:
$ ps -ef >prereboot.txt
$ grep -i dbus-daemon postreboot.txt
$ grep -i dbus-daemon https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1427785/+subscriptions

--
Mailing list: https://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 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives

2015-03-19 Thread hansie

screen flicker on 'Toshiba Satelite A215-S4697' 
 
1.  kernel 3.19.0 - versions 7,8,9:  ubuntu 15.10
screen does not flicker at all

2.  kernel 3.13.0
a.  uptil version 35 (36?):  screen does not flicker
b.  upwards from version 36 screen flickers badlyc.  (upwards from version 36 a 
bug - or omission - may have crept in)
   


 On Thursday, March 19, 2015 3:42 PM, jwm hogenboom 
 wrote:
   

 kernel versions on 'Satelite A215-S4697' related 
 


 On Monday, March 9, 2015 12:12 PM, jwm hogenboom  
wrote:
   

 1. i installed  a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' 
- hoping that disk speed would solve the problem
2. first distro installed was 'zorin 9 lite'3. the original installation did 
not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: 
kernel 3.13.46
'zorin' is based on 'ubuntu 14.04 xfce'


 On Friday, February 27, 2015 2:01 PM, jwm hogenboom 
 wrote:
   

 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. 
the flickering does not exist in the very first - and original - kernel of 
ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 
'mint' does not change kernels, the way ubuntu does
 

 On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver 
 wrote:
   

 hansie, 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 1405277

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

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

Thank you for your understanding.

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

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

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

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

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+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/1405277

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

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

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

[Touch-packages] [Bug 1160569]

2015-03-19 Thread HackMan

Distro: Slackware 14.1 32bit
Libc: glibc-2.20-i486-2
Kernel: 3.12.38

hackman@terion:~$ firefox -version

(process:22214): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size 
== 0' failed
Mozilla Firefox 36.0.1

hackman@terion:~$ thunderbird -version

(process:22231): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size 
== 0' failed
Thunderbird 31.5.0

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

Title:
  GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0'
  failed

Status in The Mozilla Firefox Browser:
  Confirmed
Status in The "G" Library - GLib:
  Unknown
Status in apport package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Have a look at the screen-shot for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20130308124351
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Tue Mar 26 21:48:57 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130326)
  IpRoute:
   default via 10.0.1.1 dev eth0  proto static
   10.0.1.0/24 dev eth0  proto kernel  scope link  src 10.0.1.16  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Videos) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Videos 3.6.3) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu4
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1429687] Re: Cannot import two files with the same name to ContentStore.App

** Branch linked: lp:ubuntu/vivid-proposed/content-hub

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

Title:
  Cannot import two files with the same name to ContentStore.App

Status in Content sharing/picking infrastructure and service:
  Confirmed
Status in content-hub package in Ubuntu:
  New

Bug description:
  When you import a file using a ContentScope and ContentStore.App, it
  gets copied to ~/.local/share///.  If
  you try to import another file with the same name and content type,
  the existing file will be left in place and the new file not copied
  over.  However, you get a ContentItem returned with the a URL pointing
  to the old imported file.

  My expectation is that the new file should be copied to file(1) or
  similar.  Perhaps this should only happen if the files are distinct.
  Failing this, ContentHub should throw an error and not let me think
  that the import succeeded.

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

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

[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread apjjr

Ok.  I have no idea what I'm looking for.  I see messages in a lot of
the upstart log files that look like errors. See below.

How am I supposed to know what package this 'bug' belongs to?  I'm not a linux 
systems guy.  How would I figure that out?  I'd be glad to classify this better 
if I knew how.
All I know is what I said in my first remark about this.
I've been using Ubuntu since 5.04 and have never seen duplicate processes get 
started like this before.  They just keep building up until I start to see 
performance degradation.  Then I reboot and all is well until they build up 
again.
Thanks for your help.

Here's part of the output of ps fax:
7011 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky >/dev/null -
 7012 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6715 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky >/dev/null
 7016 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky >/dev/null -
 7017 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6872 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky >/dev/null
 7019 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky >/dev/null -
 7021 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6910 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky >/dev/null
 7022 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky >/dev/null -
 7026 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe

I wonder why so many instances of Docky?

I'd appreciate any help I can get.  If I need to reinstall because
somethngs gotten screwed up, I'll do that.

Following are the upstart log files I think are indicating some error:

cups.log
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer 
configuration
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer 
configuration

gpu-manager.log
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

kmod.log
modprobe: FATAL: Module rtc not found.
modprobe: FATAL: Module rtc not found.

network-manager.log

(NetworkManager:861): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

(NetworkManager:879): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

ureadahead.log
ureadahead:/var/lib/NetworkManager/dhclient-wlan0.conf: No such file or 
directory
ureadahead:/var/lib/NetworkManager/dhclient-wlan0.conf: No such file or 
directory

ureadahead-other.log
ureadahead:/home/apjjr/.cache/upstart/im-config.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/update-notifier-release.log: No such file 
or directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-ssh.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-gpg.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/ssh-agent.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/unity7.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/indicator-bluetooth.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-datetime.log: No such file or 
directory
ureadahead:/home/apjjr/.local/share/gvfs-metadata/home-00b673f2.log: No such 
file or directory
ureadahead:/var/lib/ureadahead/boot.efi.pack: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/im-config.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/update-notifier-release.log: No such file 
or directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-ssh.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-gpg.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/ssh-agent.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/unity7.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/window-stack-bridge.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-bluetooth.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-datetime.log: No such file or 
directory
ureadahead:/home/apjjr/.local/share/gvfs-metadata/home-00b673f2.log: No such 
file or directory

wait-for-state-plymouth-shutdownlightdm.log
stop: Job has already been stopped: lightdm
stop: Job has al

Re: [Touch-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives

2015-03-19 Thread hansie

kernel versions on 'Satelite A215-S4697' related 
 


 On Monday, March 9, 2015 12:12 PM, jwm hogenboom  
wrote:
   

 1. i installed  a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' 
- hoping that disk speed would solve the problem
2. first distro installed was 'zorin 9 lite'3. the original installation did 
not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: 
kernel 3.13.46
'zorin' is based on 'ubuntu 14.04 xfce'


 On Friday, February 27, 2015 2:01 PM, jwm hogenboom 
 wrote:
   

 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. 
the flickering does not exist in the very first - and original - kernel of 
ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 
'mint' does not change kernels, the way ubuntu does
 

 On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver 
 wrote:
   

 hansie, 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 1405277

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

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

Thank you for your understanding.

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

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

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

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

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+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/1405277

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

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

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

[Touch-packages] [Bug 1432829] Re: resolv.conf not updated correctly for interfaces configured in initramfs

2015-03-19 Thread Thomas Hood

** Summary changed:

- resolvconf not updated correctly for interfaces configured in initramfs
+ resolv.conf not updated correctly for interfaces configured in initramfs

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

Title:
  resolv.conf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434006] Re: Information leak

2015-03-19 Thread Seth Arnold

You can configure this with /etc/pam.d/sshd -- simply remove the
pam_motd lines from your PAM sshd configuration and this information
will no longer be shown when users successfully authenticate. (Neither
sshd nor pam_motd.so care if your users are using bash or false or
nologin for their shell; they successfully authenticated, which is all
the pam_motd.so cares about.)

Thanks

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

Title:
  Information leak

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I have configured ssh server. I have added user with nologin shell,
  because he's use sftp client to transfer files, not to login to shell.
  But if that user try to login to shell server returns information
  about server:

  $ ssh u...@someserver.org
  user@someserver's password:
  Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com/

System information as of Thu Mar 19 11:16:13 CET 2015

System load:0.0 Processes:   131
Usage of /home: 52.4% of 295.16GB   Users logged in: 1
Memory usage:   11% IP address for eth0: xxx.x.xxx.xxx
Swap usage: 1%  IP address for eth1: xx.xx.xxx.xxx

Graph this data and manage this system at:
  https://landscape.canonical.com/

  10 packages can be updated.
  10 updates are security updates.

  Last login: Thu Mar 19 11:16:13 2015 from xx.xxx.xx.xx
  This account is currently not available.
  Connection to someserver.org closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: openssh-server 1:6.6p1-8
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 11:18:02 2015
  InstallationDate: Installed on 2014-04-19 (334 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to utopic on 2014-11-06 (133 days ago)
  upstart.ssh.override: manual

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

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2015-03-19 Thread Clay Spence

Here's another symptom, though it may well be unrelated. This bug
affects my work computer, on which I have ubuntu 14.04 LTS, 64-bit. On
that computer, when I use the workaround, i.e., quit software updater
and start it, a window appears for it and I can use it to update. But
the window can't be resized. The mouse pointer doesn't even change when
I pass it over the window's border.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  Invalid
Status in intel-linux-graphics-installer source package in Quantal:
  Invalid
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  Invalid

Bug description:
  Found an easy way to reproduce it during brussels sprint:
  1. start deja-dup or update-manager
  2. kill -9 compiz; metacity
  3. compiz --replace

  
  ===

  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 1228575] Re: Slider's tooltip too small sometimes

2015-03-19 Thread Michal Predotka

Wanted to report a bug about this very problem but I see it's already
reported. I'm attaching my screenshot anyway.

** Attachment added: "Screenshot at 22-13-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1228575/+attachment/4350339/+files/Screenshot%20at%2022-13-39.png

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

Title:
  Slider's tooltip too small sometimes

Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I tried to reimplement Slider's formatValue function this way:

  function formatValue(v) {
  if (v < maximumValue / 3)
  return i18n.tr("Small")
  else if (v < maximumValue / 3 * 2)
  return i18n.tr("Midium")
  else return i18n.tr("Large")
  }

  Result: word "Medium" doesn't fit in tooltip.
  Solution: use something like 
  Math.max(STANDARD_WIDTH, innerLabel.contentWidth)

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

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

[Touch-packages] [Bug 1434006] Re: Information leak

2015-03-19 Thread Seth Arnold

** Information type changed from Private Security to Public Security

** Changed in: openssh (Ubuntu)
   Status: New => Invalid

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

Title:
  Information leak

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I have configured ssh server. I have added user with nologin shell,
  because he's use sftp client to transfer files, not to login to shell.
  But if that user try to login to shell server returns information
  about server:

  $ ssh u...@someserver.org
  user@someserver's password:
  Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com/

System information as of Thu Mar 19 11:16:13 CET 2015

System load:0.0 Processes:   131
Usage of /home: 52.4% of 295.16GB   Users logged in: 1
Memory usage:   11% IP address for eth0: xxx.x.xxx.xxx
Swap usage: 1%  IP address for eth1: xx.xx.xxx.xxx

Graph this data and manage this system at:
  https://landscape.canonical.com/

  10 packages can be updated.
  10 updates are security updates.

  Last login: Thu Mar 19 11:16:13 2015 from xx.xxx.xx.xx
  This account is currently not available.
  Connection to someserver.org closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: openssh-server 1:6.6p1-8
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 11:18:02 2015
  InstallationDate: Installed on 2014-04-19 (334 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to utopic on 2014-11-06 (133 days ago)
  upstart.ssh.override: manual

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

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

[Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator

2015-03-19 Thread Jim Hodapp

Plan is to work on underlying background playlist support this next
iteration, so this will be possible to re-enable in the next few weeks
or so.

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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

[Touch-packages] [Bug 1066404] Re: wireless connection drops

2015-03-19 Thread Christos

I have the same symptoms after an upgrade to version 14.04

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

Title:
  wireless connection drops

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 12.10 (fully updated) and the wireless connection
  keeps dropping.  It appears to be connected in Network Manager but I'm
  unable to reach any web pages or the admin page of my router.

  Clicking on the network manager icon and selecting my network re-
  establishes the connection which is fine for about half an hour then
  it drops again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 13 23:22:07 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120302)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to quantal on 2012-10-12 (1 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   Wired connection 10e7ba644-1689-4f76-9e6c-89e9e8d12f9b   
802-3-ethernet1350158233   Sat 13 Oct 2012 20:57:13 BST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   David and Emma's Home Network 9c41658a-d48f-48c0-87d3-bcbcbee8d9b8   
802-11-wireless   1350166935   Sat 13 Oct 2012 23:22:15 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

2015-03-19 Thread paz

The bug fixed for me on  Linux paz 3.2.0-79-generic-pae #115-Ubuntu SMP Thu Mar 
12 14:33:25 UTC 2015 i686 i686 i386 GNU/Linux
Thank you very much!

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434295] [NEW] service systemd-tmpfiles-setup fails to start

2015-03-19 Thread Matteo Croce

Public bug reported:

Service systemd-tmpfiles-setup.service fails to start because there are
two duplicate lines in /usr/lib/tmpfiles.d:

[/usr/lib/tmpfiles.d]# grep -r '^d /var/log ' *
00rsyslog.conf:d /var/log 0775 root syslog -
var.conf:d /var/log 0755 - - -

[/usr/lib/tmpfiles.d]# systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since gio 2015-03-19 22:40:05 CET; 11min 
ago
 Docs: man:tmpfiles.d(5)
   man:systemd-tmpfiles(8)
 Main PID: 430 (code=exited, status=1/FAILURE)

mar 19 22:40:05 raver systemd[1]: Starting Create Volatile Files and 
Directories...
mar 19 22:40:05 raver systemd-tmpfiles[430]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/...ring.
mar 19 22:40:05 raver systemd[1]: systemd-tmpfiles-setup.service: main process 
exited, code=exited, status=1/FAILURE
mar 19 22:40:05 raver systemd[1]: Failed to start Create Volatile Files and 
Directories.
mar 19 22:40:05 raver systemd[1]: Unit systemd-tmpfiles-setup.service entered 
failed state.
mar 19 22:40:05 raver systemd[1]: systemd-tmpfiles-setup.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

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

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

Title:
  service systemd-tmpfiles-setup fails to start

Status in systemd package in Ubuntu:
  New

Bug description:
  Service systemd-tmpfiles-setup.service fails to start because there
  are two duplicate lines in /usr/lib/tmpfiles.d:

  [/usr/lib/tmpfiles.d]# grep -r '^d /var/log ' *
  00rsyslog.conf:d /var/log 0775 root syslog -
  var.conf:d /var/log 0755 - - -

  [/usr/lib/tmpfiles.d]# systemctl status systemd-tmpfiles-setup.service
  ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
 Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since gio 2015-03-19 22:40:05 CET; 
11min ago
   Docs: man:tmpfiles.d(5)
 man:systemd-tmpfiles(8)
   Main PID: 430 (code=exited, status=1/FAILURE)

  mar 19 22:40:05 raver systemd[1]: Starting Create Volatile Files and 
Directories...
  mar 19 22:40:05 raver systemd-tmpfiles[430]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/...ring.
  mar 19 22:40:05 raver systemd[1]: systemd-tmpfiles-setup.service: main 
process exited, code=exited, status=1/FAILURE
  mar 19 22:40:05 raver systemd[1]: Failed to start Create Volatile Files and 
Directories.
  mar 19 22:40:05 raver systemd[1]: Unit systemd-tmpfiles-setup.service entered 
failed state.
  mar 19 22:40:05 raver systemd[1]: systemd-tmpfiles-setup.service failed.
  Hint: Some lines were ellipsized, use -l to show in full.

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

2015-03-19 Thread Pat McGowan

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

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent & the state of the backendand the backend is
  unfortunately variable & lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1434205] Re: accounts-daemon using up several gigabytes of RAM

2015-03-19 Thread Adam K

If you're feeling brave, here's a snippet of the heap that contains
"similar" looking things in it. Without knowing much about accounts-
daemon, it doesn't make sense to me. I just did a gdb dump memory to get
it and dumped this chunk out using Bless.

** Attachment added: "Snippet of heap"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1434205/+attachment/4350328/+files/accounts-daemon-heap-snippet.bin

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

Title:
  accounts-daemon using up several gigabytes of RAM

Status in accountsservice package in Ubuntu:
  New

Bug description:
  HP Z400 Workstation
  Intel Xeon W3520
  12GB RAM
  nVidia QuadroFX 580

  Kubuntu Trusty 14.04.2 LTS, apt-get says everything is up to date
  Kernel 3.13.0-46-generic x64
  KDE SC Version 4.13.2
  Accountsservice 0.6.35-0ubuntu7.1

  My system seems to boot just fine until it tries to bring up LightDM.
  At that point, accounts-daemon eats up 100% of a CPU core, starts
  allocating tons of memory and causes LightDM to hang for ~25 seconds.
  After I put in my username and password accounts-daemon continues
  eating up 100% of a CPU core, allocates more memory and hangs the
  login process some more. After being logged in for a few minutes it
  stops using CPU time but never frees any memory, eventually settling
  in at ~6GB used. At the time of this writing it is currently at
  5,754,280K.

  If I kill the process it frees all of the memory, but after locking
  the screen or similiar action something (dbus?) starts it back up
  again and the process repeats, although only using up ~3GB of RAM. I
  have tried running accounts-daemon --debug and it doesn't spit out
  anything indicating an error. The closest that I've found to a problem
  is in the lightdm.log file excerpted below:

  
  [+0.05s] DEBUG: Using VT 7
  [+0.05s] DEBUG: Seat: Starting local X display on VT 7
  [+0.05s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.05s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.05s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.05s] DEBUG: Launching process 1254: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.05s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.05s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+25.08s] WARNING: Error getting user list from org.freedesktop.Accounts: 
Timeout was reached
  [+25.08s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+25.09s] DEBUG: User x added
  [+25.09s] DEBUG: Got signal 10 from process 1254
  [+25.09s] DEBUG: DisplayServer x-0: Got signal from X server :0
  [+25.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0
  

  dbus does seem to start the service successfully as evidenced in
  syslog:

  
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Activating service 
name='org.freedesktop.Accounts' (using servicehelper)
  Mar 19 10:32:32 the-cybercraft accounts-daemon[1259]: started daemon version 
0.6.35
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Successfully activated 
service 'org.freedesktop.Accounts'
  

  I'll provide any help that I can, and thanks!

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

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

[Touch-packages] [Bug 1434205] Re: accounts-daemon using up several gigabytes of RAM

2015-03-19 Thread Adam K

If it helps, here's a /proc//maps dump of the offending process.

** Attachment added: "proc pid maps dump of accounts-daemon process"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1434205/+attachment/4350318/+files/accounts-daemon-proc-map.txt

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

Title:
  accounts-daemon using up several gigabytes of RAM

Status in accountsservice package in Ubuntu:
  New

Bug description:
  HP Z400 Workstation
  Intel Xeon W3520
  12GB RAM
  nVidia QuadroFX 580

  Kubuntu Trusty 14.04.2 LTS, apt-get says everything is up to date
  Kernel 3.13.0-46-generic x64
  KDE SC Version 4.13.2
  Accountsservice 0.6.35-0ubuntu7.1

  My system seems to boot just fine until it tries to bring up LightDM.
  At that point, accounts-daemon eats up 100% of a CPU core, starts
  allocating tons of memory and causes LightDM to hang for ~25 seconds.
  After I put in my username and password accounts-daemon continues
  eating up 100% of a CPU core, allocates more memory and hangs the
  login process some more. After being logged in for a few minutes it
  stops using CPU time but never frees any memory, eventually settling
  in at ~6GB used. At the time of this writing it is currently at
  5,754,280K.

  If I kill the process it frees all of the memory, but after locking
  the screen or similiar action something (dbus?) starts it back up
  again and the process repeats, although only using up ~3GB of RAM. I
  have tried running accounts-daemon --debug and it doesn't spit out
  anything indicating an error. The closest that I've found to a problem
  is in the lightdm.log file excerpted below:

  
  [+0.05s] DEBUG: Using VT 7
  [+0.05s] DEBUG: Seat: Starting local X display on VT 7
  [+0.05s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.05s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.05s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.05s] DEBUG: Launching process 1254: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.05s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.05s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+25.08s] WARNING: Error getting user list from org.freedesktop.Accounts: 
Timeout was reached
  [+25.08s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+25.09s] DEBUG: User x added
  [+25.09s] DEBUG: Got signal 10 from process 1254
  [+25.09s] DEBUG: DisplayServer x-0: Got signal from X server :0
  [+25.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0
  

  dbus does seem to start the service successfully as evidenced in
  syslog:

  
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Activating service 
name='org.freedesktop.Accounts' (using servicehelper)
  Mar 19 10:32:32 the-cybercraft accounts-daemon[1259]: started daemon version 
0.6.35
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Successfully activated 
service 'org.freedesktop.Accounts'
  

  I'll provide any help that I can, and thanks!

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

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

[Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator

2015-03-19 Thread Pat McGowan

I am informed this just requires the support to be re-enabled in the UI is that 
correct?
If so we could consider for ota

** Changed in: canonical-devices-system-image
 Assignee: Michael Frey (mfrey) => Canonical Phone Foundations 
(canonical-phonedations-team)

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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

[Touch-packages] [Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available

2015-03-19 Thread Pat McGowan

I do not think the other scenario is fixed, assign to Bill t confirm

** Changed in: canonical-devices-system-image
 Assignee: Thomas Voß (thomas-voss) => Bill Filler (bfiller)

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

Title:
  Not yet available but configured providers should be added as soon as
  they become available

Status in the base for Ubuntu mobile products:
  In Progress
Status in location-service package in Ubuntu:
  In Progress
Status in ubuntu-location-provider-here package in Ubuntu:
  In Progress
Status in ubuntu-location-provider-here package in Ubuntu RTM:
  Confirmed

Bug description:
  Right now, the location service tries to instantiate configured
  providers at startup. In specific corner cases, some of the configured
  sensors might not be available and the service should be able to be
  notified when those providers become available.

  In particular, this affects the wizard running on first boot, and
  subsequent login to the user session.

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

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

[Touch-packages] [Bug 1432829] Re: resolvconf not updated correctly for interfaces configured in initramfs

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

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

  * use systemd-ifupdown-helper script to handle ifup and ifdown
of auto or hotplug devices.  This allows iscsi root volumes
to work again. (LP: #1432829)
  * debian/control/tests: disable running of upstart tests until
upstart packaging bug 1422681 is resolved.
 -- Scott MoserThu, 19 Mar 2015 11:43:14 -0400

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

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

Title:
  resolvconf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

2015-03-19 Thread CAILLOT

this new package lightdm/1.2.3-0ubuntu2.7
  is ok for me. thank


Le 19/03/2015 21:01, Brian Murray a écrit :
> Hello timothymowens, or anyone else affected,
>
> Accepted lightdm into precise-proposed. The package will build now and
> be available at
> https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed.  Your feedback will aid us getting this update
> out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, and change the tag
> from verification-needed to verification-done. If it does not fix the
> bug for you, please add a comment stating that, and change the tag to
> verification-failed.  In either case, details of your testing will help
> us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Tags added: verification-needed
>

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1067547] Re: Unity in 12.10 becomes unusably slow after using Alt-Tab to switch between programs (nvidia)

Since no one responded to Andrea's inquiry on 2015-01-17 and Ubuntu
12.10 is out of support, I'm going to surmise this was fixed somewhere
along the way.

If it still does occur, we can either reopen this bug or open a new one.

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

** Changed in: unity (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: unity
Milestone: 7.3.3 => None

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

Title:
  Unity in 12.10 becomes unusably slow after using Alt-Tab to switch
  between programs (nvidia)

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Not sure what else to say. On my laptop with a clean 12.10
  installation everything works great. On my desktop with an Nvidia
  gts250 card (all available drivers in the repo) unity works fine, but
  after I use alt-tab to switch between applications, compiz memory
  usage rises (20, 50, 100mb, depends on... well, something?) and dash,
  all effects and even window dragging becomes unbearably slow.

  After I do a "unity --replace", everything is fine until I use alt-tab
  again. I can reproduce this as many times as I want.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.51  Tue Sep 18 17:36:24 PDT 
2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Oct 17 01:12:10 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current-updates, 304.51, 3.5.0-17-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:34c7]
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=cad55f8d-5c9a-45ee-9ed1-a26e67b985ae ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  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.:bvr0604:bd09/15/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.8.4-0ubuntu2
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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

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

[Touch-packages] [Bug 951929] Re: Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

This is a rather old bug and is sitting stale.  Since no one responded
to Andrea on his 2014-12-01 inquiry about being able to reproduce this,
I'm going to mark it fixed as some prior release probably fixed it.

If this still does occur, then we can reopen this bug or open a new one.

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

** Changed in: unity (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity
Milestone: 7.3.3 => None

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

Title:
  Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  edit: Updated title, its affecting more than gnome-terminal

  1) Description:   Ubuntu precise (development branch)
  Release:  12.04

  2) unity:
    Installed: 5.4.0-0ubuntu2

  3) Gnome-Terminal to show in list of programs to alt+tab to.

  4)  Alt+Tab consistently fails to show gnome-terminal for 'a while' (I
  hate to be vague, I can't figure out what suddenly triggers it to
  appear in the box).  See attached photograph of it occurring.

  I can make it happen at will:

  1) Cold boot into Ubuntu.
  2) Open gnome-terminal.
  3) Open Firefox.
  4) Press alt+tab.  alt+tab window only shows Desktop and Firefox.

  In attached screenshot, note that gnome-terminal has a highlighted
  background and arrow, indicating an instance of it running, as is
  Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sat Mar 10 14:50:09 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1056427] Re: slight flicker in the application title when gnome-control-center is closed.

This is a rather old bug that has been sitting stale for some time.
Since no one responded to Marco in his comment on 2013-09-16, I'm going
to say it's been fixed in some release and going to mark as such.

If this does indeed still occur, then we can either reopen this bug or
open a new one.

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

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity
Milestone: 7.3.3 => None

** Changed in: unity (Ubuntu)
   Status: Incomplete => Fix Released

** No longer affects: unity/7.2

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

Title:
  slight flicker in the application title when gnome-control-center is
  closed.

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  1. open nautilus
  2. open gnome-control-center
  2. close control center

  What happens:
  there is a slight flicker in the panel.

  What should happen:
  no flicker.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0+stagingfuturebzr2741ubuntu0+785 [origin: 
LP-PPA-unity-team-staging-future]
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  Date: Wed Sep 26 01:05:21 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120831)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1434272] [NEW] Icons are too small when title bars and menus are scaled by 1.75

2015-03-19 Thread Tony Houghton

Public bug reported:

I've just installed Ubuntu 14.10 on a Macbook Pro Retina 13. I tried
setting the menu and title bar scaling to 1.75 but the icons did not
scale up appropriately; they stayed at a factor of 1 AFAICT. Certain
apps, eg Nautilus and the settings app, seemed to be using the icon size
to determine layout, so the text appeared cramped and some was
truncated. I increased the setting to 2 and then the icons did scale up
(but not the pointer, see #1359211). However, now title bars, menus and
other text-based widgets are larger than ideal. I can reduce the font
sizes with unity-tweak-tool but it doesn't seem to affect the title bar
size etc.

I presume the lack of icon scaling is because GTK only supports integer
scaling settings and Unity is rounding down the setting for it. Please
could it be changed to round up for fractions over 0.5.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Mar 19 20:51:27 2015
InstallationDate: Installed on 2015-03-19 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Icons are too small when title bars and menus are scaled by 1.75

Status in unity package in Ubuntu:
  New

Bug description:
  I've just installed Ubuntu 14.10 on a Macbook Pro Retina 13. I tried
  setting the menu and title bar scaling to 1.75 but the icons did not
  scale up appropriately; they stayed at a factor of 1 AFAICT. Certain
  apps, eg Nautilus and the settings app, seemed to be using the icon
  size to determine layout, so the text appeared cramped and some was
  truncated. I increased the setting to 2 and then the icons did scale
  up (but not the pointer, see #1359211). However, now title bars, menus
  and other text-based widgets are larger than ideal. I can reduce the
  font sizes with unity-tweak-tool but it doesn't seem to affect the
  title bar size etc.

  I presume the lack of icon scaling is because GTK only supports
  integer scaling settings and Unity is rounding down the setting for
  it. Please could it be changed to round up for fractions over 0.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Mar 19 20:51:27 2015
  InstallationDate: Installed on 2015-03-19 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1057419] Re: Partial tooltips displayed

This is a rather old bug that I can't seem to reproduce and has been set
Incomplete for some time.  It's probably been fixed in some release and
going to mark as such.

If it still occurs, we can either reopen this bug or open a new one.

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

** Changed in: unity
Milestone: 7.3.3 => None

** Changed in: unity (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Partial tooltips displayed

Status in Unity:
  Fix Released
Status in Unity 6.0 series:
  Incomplete
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  See the included screenshot, partial tooltips can be displayed as if there 
were an invisible window hiding them.
  Clicking through this invisible window correctly brings the background 
application in front.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Thu Sep 27 11:20:02 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.8-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

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

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

[Touch-packages] [Bug 1434266] [NEW] coding exception apport-collect -p xorg

2015-03-19 Thread Galen Thurber

Public bug reported:

while trying to update a bug report
apport-collect -p xorg 1424864

A coding exception was thrown and uncaught in a Task.

Full message: TypeError: f.readTo is not a function
...
Full stack: 
exports.IO.readFromFile/<@resource://gre/modules/addons/XPIProvider.jsm -> 
jar:file:///home/xxx/.mozilla/firefox/.default/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js
 -> 
jar:file:///home/xxx/.mozilla/firefox/xxx.default/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/io.js:207:28
TaskImpl_run@resource://gre/modules/Task.jsm:330:41
Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:870:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:749:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:691:37

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

Title:
  coding exception apport-collect -p xorg

Status in apport package in Ubuntu:
  New

Bug description:
  while trying to update a bug report
  apport-collect -p xorg 1424864

  A coding exception was thrown and uncaught in a Task.

  Full message: TypeError: f.readTo is not a function
  ...
  Full stack: 
exports.IO.readFromFile/<@resource://gre/modules/addons/XPIProvider.jsm -> 
jar:file:///home/xxx/.mozilla/firefox/.default/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js
 -> 
jar:file:///home/xxx/.mozilla/firefox/xxx.default/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/io.js:207:28
  TaskImpl_run@resource://gre/modules/Task.jsm:330:41
  Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:870:23
  this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:749:7
  this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:691:37

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

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

[Touch-packages] [Bug 1416215] Re: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1

2015-03-19 Thread Fernando Acero

I have resolved the problem upgrading  sudo in kubuntu 14.04 LTS

I have deleted all files starting with sudo on var/cache/apt/archives/

sudo rm -rf sudo*

After download sudo_1.8.9p5-1ubuntu1.1_i386.deb from repository

sudo dpkg -i sudo_1.8.9p5-1ubuntu1.1_i386.deb

Best regards

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

Title:
  package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso
  instalado el script pre-removal devolvió el código de salida de error
  1

Status in sudo package in Ubuntu:
  New

Bug description:
  Trying to install some libbs, this error apears... i guess that is
  because this is a 32x system and those libb use a 64x sudo, so that.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: sudo 1.8.9p5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Thu Jan 29 13:18:02 2015
  DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:el subproceso instalado el 
script pre-removal devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script pre-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-01-22 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sudo
  Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso 
instalado el script pre-removal devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1432047] Re: Chrome bug on Mesa driver

2015-03-19 Thread Sherif

Distribution: Kubuntu 15.04. I've switchable graphics (Intel and AMD).
It doesn't seem to affect me.

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

Title:
  Chrome bug on Mesa driver

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating mesa drivers from 10.4 to 10.5 Google chrome with GPU
  rendering ON may some strange image distortion.

  Ubuntu Vivid 15.04 Beta1

  AMD Athlon 740 without integrated GPU
  Asus F2A85M
  Nvidia 9600GT

  Watch this
  https://www.youtube.com/watch?v=EEkjz_Ix3Aw

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libegl1-mesa 10.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 13 16:55:23 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-03-12 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed 
root=UUID=66ba97fd-d16b-45d8-87a0-8299ea2ec638 ro quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6508
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M
  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.:bvr6508:bd07/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2
  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.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Mar 13 16:16:49 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(0): [COPY] failed to allocate class.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

** Branch linked: lp:ubuntu/precise-proposed/lightdm

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread Stephen M. Webb

Most of the processes you're seeing are run by the session upstart. Try
'ps fax' to see the process tree. You also get to see what state these
processes are in that way.

Still, this has nothing to do with Unity, which neither handles system
power states nor session process control. You might want ot check logs
in /var/log/upstart or ~/.cache/upstart for more clues.

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

Title:
Duplicate processes started after Resume of amd64 bit

Status in unity package in Ubuntu:
New

Bug description:
$ uname -a
Linux ajsc855 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

Toshiba Satellite C855, 4GB RAM, 720GB HD

I typically run Thunderbird, Firefox, a terminal or two, Gthumb, Gimp,
Qcad, Gedit, Libreoffice, Inkscape, Document Viewer and occasionally
Virtualbox.

I just noticed this a couple of weeks ago, so I am guessing a recent
update started it.

Logging out and back in did not alleviate the problem. Rebooting did.
But, I will have to reboot again in a week to free up the memory used
by these duplicate processes.

The example session used to get the following results was probably
well over a week in use.

Before rebooting:
$ ps -ef >prereboot.txt
$ grep -i dbus-daemon postreboot.txt
$ grep -i dbus-daemon https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1427785/+subscriptions

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

[Touch-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

Hello rumen, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Daemon end of session/greeter pipes not closed

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

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

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

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

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

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

[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Hello timothymowens, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1207935] Re: lightdm crashed with SIGSEGV in quit_timeout_cb()

Hello Fabio, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  lightdm crashed with SIGSEGV in quit_timeout_cb()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  ..

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.8-0ubuntu1
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 31 00:29:44 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2011-07-23 (738 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
   autologin-user=
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x40e47d:  movl   $0x0,0x20(%rax)
   PC (0x0040e47d) ok
   source "$0x0" ok
   destination "0x20(%rax)" (0xaaca) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-07-10 (19 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

Hello Dan, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1069218] Re: users.conf doesn't match users.c

Hello Mike, or anyone else affected,

Accepted lightdm into precise-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lightdm/1.2.3-0ubuntu2.7 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  users.conf doesn't match users.c

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The default users.conf provided by LightDM mentions a section [UserAccounts]. 
It should be [UserList].

  [Test Case]
  1. Check default installed users.conf
  Expected result:
  Should have a [UserList] section with all items available but disabled.
  Observed result:
  Have a [UserAccounts] section with all items available but disabled.

  [Regression Potential]
  Very low - just changing the default configuration file which has no active 
configuration items.

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

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

[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread apjjr

Maybe I should just reinstall and see if the problem goes away. I feel
like I'm talking to myself.

** Package changed: meta-gnome3 (Ubuntu) => unity (Ubuntu)

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

Title:
Duplicate processes started after Resume of amd64 bit

Status in unity package in Ubuntu:
New

Bug description:
$ uname -a
Linux ajsc855 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

Toshiba Satellite C855, 4GB RAM, 720GB HD

I typically run Thunderbird, Firefox, a terminal or two, Gthumb, Gimp,
Qcad, Gedit, Libreoffice, Inkscape, Document Viewer and occasionally
Virtualbox.

I just noticed this a couple of weeks ago, so I am guessing a recent
update started it.

Logging out and back in did not alleviate the problem. Rebooting did.
But, I will have to reboot again in a week to free up the memory used
by these duplicate processes.

The example session used to get the following results was probably
well over a week in use.

Before rebooting:
$ ps -ef >prereboot.txt
$ grep -i dbus-daemon postreboot.txt
$ grep -i dbus-daemon https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1427785/+subscriptions

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

[Touch-packages] [Bug 1434259] [NEW] still screen freeze

2015-03-19 Thread gord rutherford

Public bug reported:

going to full screen on a video feed will freeze computer now first
screen then whole computer

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-77.114-generic-pae 3.2.66
Uname: Linux 3.2.0-77-generic-pae i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  304.125  Mon Dec  1 19:55:52 PST 
2014
 GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
CurrentDmesg:
 [   14.584235] input: Microsoft\xffc2\xffae\xffae LifeCam VX-2000 
as /devices/pci:00/:00:1d.7/usb2/2-6/2-6:1.0/input/input6
 [   15.648283] init: plymouth-splash main process (1320) terminated with 
status 1
 [   16.102134] init: plymouth-stop pre-start process (1547) terminated with 
status 1
 [   25.696008] eth0: no IPv6 routers present
Date: Thu Mar 19 12:50:24 2015
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Device [196e:053c]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: System manufacturer P5Q-PRO
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-77-generic-pae 
root=UUID=b68166a6-2be8-41f8-b327-20235afa223a ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
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.:bvr1104:bd07/31/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.7.12-0ubuntu4
version.libdrm2: libdrm2 2.4.52-1~precise2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.17
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1~precise~xup2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0-0ubuntu1~xup1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3~precise~xup2

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


** Tags: apport-bug i386 needs-reassignment precise regression-update 
running-unity third-party-packages ubuntu

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

Title:
  still screen freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  going to full screen on a video feed will freeze computer now first
  screen then whole computer

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic-pae 3.2.66
  Uname: Linux 3.2.0-77-generic-pae i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.125  Mon Dec  1 19:55:52 
PST 2014
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CurrentDmesg:
   [   14.584235] input: Microsoft\xffc2\xffae\xffae LifeCam 
VX-2000 as /devices/pci:00/:00:1d.7/usb2/2-6/2-6:1.0/input/input6
   [   15.648283] init: plymouth-splash main process (1320) terminated with 
status 1
   [   16.102134] init: plymouth-stop pre-start process (1547) terminated with 
status 1
   [   25.696008] eth0: no IPv6 routers present
  Date: Thu Mar 19 12:50:24 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Device [196e:053c]
  InstallationMedia: Ubuntu

[Touch-packages] [Bug 1060148] Re: unity 6.8 candidate segfaults on "app expose" with low gfx mode

Hmm, seems fixed some time ago, so going to mark the main Unity task as
such as well and remove the milestone.

** Changed in: unity
   Status: Triaged => Fix Released

** Changed in: unity
Milestone: 7.3.3 => None

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

Title:
  unity 6.8 candidate segfaults on "app expose" with low gfx mode

Status in Unity:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  - run the current ppa version
  - open several nautilus dialog
  - click on nautilus in the launcher

  stacktrace:

  #0  0xb7548f90 in ?? () from /lib/i386-linux-gnu/libc.so.6
  No symbol table info available.
  #1  0xb4838cee in memmove (__len=806243456, __src=0x3c73f2f0, 
__dest=) at /usr/include/i386-linux-gnu/bits/string3.h:58
  No locals.
  #2  drisw_update_tex_buffer (drawable=0xc5468d8, ctx=0x8945470, 
res=0xb392b90) at drisw.c:272
  dPriv = 
  st_ctx = 
  pipe = 0x8945500
  transfer = 0xc4f94f0
  map = 0xc65a670 
"\321\332\337\377\262\273\277\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377BIJ\377"...
  x = 52
  y = 7
  w = 201560864
  h = 2
  ximage_stride = 806243456
  line = 1
  cpp = 
  #3  0xb483a373 in dri_set_tex_buffer2 (pDRICtx=0x8945450, target=3553, 
format=8410, dPriv=0xc59ae78) at dri_drawable.c:234
  internal_format = 
  ctx = 0x8945470
  drawable = 0xc5468d8
  pt = 0xb392b90
  #4  0xb4fdfe40 in drisw_bind_tex_image (dpy=0x88f2460, drawable=14680574, 
buffer=8414, attrib_list=0x0) at drisw_glx.c:319
  gc = 0x8945368
  pcp = 0x8945368
  base = 0xb44d178
  pdraw = 0xb44d178
  psc = 
  #5  0xb4fb7c77 in __glXBindTexImageEXT (dpy=0x88f2460, drawable=14680574, 
buffer=8414, attrib_list=0x0) at glxcmds.c:2429
  gc = 
  #6  0xb594b1f7 in operator() > (a=, 
this=, f=) at /usr/include/boost/bind/bind.hpp:457
  No locals.
  #7  operator() (this=, a1=) 
at /usr/include/boost/bind/bind_template.hpp:32
  No locals.
  #8  
boost::detail::function::void_function_obj_invoker1, boost::arg<1>, 
boost::_bi::value, boost::_bi::value > >, void, unsigned 
long>::invoke (function_obj_ptr=..., a0=14680574) at 
/usr/include/boost/function/function_template.hpp:153
  f = 
  #9  0xb595df97 in operator() (a0=14680574, this=0xb596e690 <(anonymous 
namespace)::bindTexImageEXT()::f>) at 
/usr/include/boost/function/function_template.hpp:760
  No locals.
  #10 compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) (serverGrabInterface=0x88ec7d4, 
x11Pixmap=14680573, glxPixmap=14680574, checkPixmapValidity=..., 
bindTexImageEXT=..., waitGLX=..., source=compiz::opengl::InternallyManaged) at 
/build/buildd/compiz-0.9.8.4/plugins/opengl/src/glxtfpbind/src/glx-tfp-bind.cpp:57
  No locals.
  #11 0xb5949897 in TfpTexture::bindTexImage (this=this@entry=0xc453598, 
glxPixmap=@0xc4535b8: 14680574) at 
/build/buildd/compiz-0.9.8.4/plugins/opengl/src/texture.cpp:631
  No locals.
  #12 0xb594a197 in TfpTexture::enable (this=0xc453598, filter=GLTexture::Fast) 
at /build/buildd/compiz-0.9.8.4/plugins/opengl/src/texture.cpp:813
  No locals.
  #13 0xb594f8a6 in GLWindow::glDrawTexture (this=0xbe71748, texture=0xc453598, 
transform=..., attrib=..., mask=786432) at 
/build/buildd/compiz-0.9.8.4/plugins/opengl/src/paint.cpp:1244
  filter = GLTexture::Fast
  #14 0xb246f8a2 in unity::UnityWindow::DrawTexture (this=0xa0c0ad0, 
textures=..., attrib=..., transform=..., mask=786432, x=81, y=77, 
scale=0.90607589483261108) at 
/build/buildd/unity-6.6.0+bzr2749stagingubuntu0+789/plugins/unityshell/src/unityshell.cpp:3552
  wTransform = {m = {0.000884839741, 0, 0, 0, -0, -0.0011797864, -0, 
-0, 0, 0, 1, 0, -0.420898438, 0.399739593, -0.866025388, 1}}
  __for_range = @0xa0c0b74: { >> = { >> = {_M_impl = {> = 
{<__gnu_cxx::new_allocator> = {}, }, _M_start = 0xc4834f8, _M_finish = 0xc4834fc, _M_end_of_storage = 
0xc4834fc}}, }, }
  #15 0xb24730a0 in unity::UnityWindow::scalePaintDecoration (this=0xa0c0ad0, 
attrib=..., transform=..., region=..., mask=786432) at 
/build/buildd/unity-6.6.0+bzr2749stagingubuntu0+789/plugins/unityshell/src/unityshell.cpp:3754
  scale_win = 0xc
  ss = 0x4d
  state = 1014231792
  #16 0xb276c361 in ScaleWindow::scalePaintDecoration (this=0xbe2f288, 
attrib=..., transf

[Touch-packages] [Bug 1429388] Re: Can't select calendar days where DST springs forward

This bug was fixed in the package indicator-datetime -
13.10.0+15.04.20150317-0ubuntu1

---
indicator-datetime (13.10.0+15.04.20150317-0ubuntu1) vivid; urgency=medium

  [ Charles Kerr ]
  * Fix bug that prevented clicking on calendar days where DST sprang
forward. (LP: #1429388)
 -- CI Train BotTue, 17 Mar 2015 15:23:52 +

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Can't select calendar days where DST springs forward

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Can't select sunday 29.03.2015 in calendar. Date is changing to
  28.03.2015 immediately. See the video.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20141009-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
  CurrentDesktop: Unity
  Date: Sat Mar  7 15:12:01 2015
  InstallationDate: Installed on 2014-11-04 (122 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 973932] Re: Disabling 'below' display does not reposition windows properly

Hey Bryce,

Hmm, I followed the exact instructions and cannot reproduce this on
15.04 or 14.04.

You reported this bug on 12.04 and on 2014-12-01, you confirmed it
still occurs, but it's not clear to me if you meant it still occurs on
12.04 or some newer version of Ubuntu.

Could you clarify which version you still see this in?

** Changed in: unity
Status: Triaged => Incomplete

** Changed in: unity (Ubuntu)
Status: Triaged => Incomplete

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

Title:
Disabling 'below' display does not reposition windows properly

Status in Compiz:
Incomplete
Status in compiz package in Ubuntu:
Incomplete

Bug description:
[Problem]
In a multihead config with one monitor above the other, if the lower monitor
is disabled the windows on that screen aren't moved to the still-active display.

[Test Case]
0. Attach laptop (LVDS1) to an external display (VGA1).
1. In the GNOME display properties applet, set the LVDS1 beneath VGA1.
2. Move to the lower left desktop (ctrl+alt+down)
3. Open one gnome terminal window on each monitor.
4. In the upper (VGA1) gnome terminal window type:
xrandr --output LVDS1 --off
(Alternatively, bring up the gnome display properties applet and shut the
laptop display off there)
5. With the LVDS turned off, count the number of gnome terminal windows
visible on VGA1
6. Using either xrandr or gnome, re-enable LVDS1 to the above/below
arrangement
7. With the LVDS re-enabled, count the number of gnome terminals visible on
VGA1 and LVDS1

Expected: 2, then 1/1
Actual:
Gnome Classic (No Effects): 2, then 1/1
Gnome Classic (With Effects): 2, then 1/1
Unity2D: 2, then 1/1
Unity: 1, then 1/1

Other findings...
A. On Unity, with LVDS1 off the missing gnome terminal window is
inaccessible. It can be recovered in various ways, but it's fairly confusing.

B. If step #2 is skipped and the test performed in the upper left
desktop, Unity will place the lower windows into the lower left
desktop.

C. On Unity, repeated testing of this seems to scramble the window
positions to some extent. The same effect does not appear to occur
with metacity; windows generally get placed back where they'd been
before.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
Date: Thu Apr 5 05:27:33 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2011-11-22 (135 days ago)

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

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

[Touch-packages] [Bug 973932] Re: Disabling 'below' display does not reposition windows properly