[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Daniel van Vugt]

Note that the failing assertion is in qtubuntu ...

ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in
file ../../../src/ubuntumirclient/glcontext.cpp, line 71

** Package changed: unity8 (Ubuntu) => qtubuntu (Ubuntu)

** Summary changed:

- Unity 8/Mir doesn't load on Intel Pineview graphics
+ Unity 8 doesn't load on Intel Pineview graphics (qtubuntu: ASSERT: 
"eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE")

** Summary changed:

- Unity 8 doesn't load on Intel Pineview graphics (qtubuntu: ASSERT: 
"eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE")
+ Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: 
"eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

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

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

[Touch-packages] [Bug 1565818] Re: Disable hardware home button on arale when greeter is active

[Michał Sawicz]

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) => Michał Sawicz (saviq)

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

Title:
  Disable hardware home button on arale when greeter is active

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  current build number: 298
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  On devices with a hardware button, tapping on it when on the greeter
  dismisses the greater and reveals the keypad to unlock the screen. If,
  for some reason, the display turns on (power button pressed
  inadvertently or battery notification for example) while the device is
  in a pocket, the button is pressed, the greeter dismissed and the
  pocket starts tapping random keys until the device is completely
  locked.

  This button must be disabled when the device is locked.

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

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

[Touch-packages] [Bug 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

[Launchpad Bug Tracker]

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

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

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

Title:
  Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I use terminus font in gnome-terminal. After upgrade to the latest
  fonconfig in xenial my terminal font is blurry.

  Versions which work as expected:

  <= 2.11.1-0ubuntu8

  Broken versions:

  >= 2.11.1-0ubuntu9

  Screenshots attached.

  Probably related to this change
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457

  Rollback to the following packages fixes this issue:

  fontconfig_2.11.1-0ubuntu8_amd64.deb
  fontconfig-config_2.11.1-0ubuntu8_all.deb
  libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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

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

[Touch-packages] [Bug 1556701] Re: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE

[Daniel van Vugt]

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

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

Note about bug 1549455: The original reporter is using Pineview as shown
in the logs there, and further down in comment #32 a Mir developer has
confirmed the same assert happens on his own hardware.


** This bug has been marked a duplicate of bug 1549455
   Unity 8/Mir doesn't load on Intel Pineview graphics

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

Title:
  ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This occurs on a WeTab tablet computer.

  The system configuration and browser apps won't run.  They display
  their small windows, then the windows disappear.

  The batter/sound/network/time & date/system pull-down menu won't stay
  open.  It closes within a second of pulling it down.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160301-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar 13 19:40:18 2016
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

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

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Daniel van Vugt]

Keeping this bug open in the Mir project so we don't lose it. Looks like
a third Pineview user is reporting the same crash.

** Changed in: mir
   Status: Invalid => Confirmed

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

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

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

[Touch-packages] [Bug 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

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

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

[Touch-packages] [Bug 1174391] Re: LightDM doesn't start

[Sworddragon]

What does make you think that this is fixed?

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

Title:
  LightDM doesn't start

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 13.04 dev with lightdm 1.6.0-0ubuntu2.1 0. On booting
  my system it will change to console 7 and the screen does go black.
  But after a few seconds this process stops and I'm seeing just text on
  console 7. Trying to manually start lightdm will result in the same
  behavior. If I'm installing GDM all is working fine. In the
  attachments is my Xorg.0.log.

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

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

[Touch-packages] [Bug 1390700] Re: perl 5.20 missing fakethe.h perlsfio.h

[Launchpad Bug Tracker]

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

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

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

Title:
  perl 5.20 missing fakethe.h perlsfio.h

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Not sure that this is Ubuntu/Debian issue but after upgrading 14.04 to
  14.10 (with new perl package 5.20) due to lack of these two files I
  wasn't able to build for ex. Session::Token module from source.

  Solution was simple:
  sudo touch /usr/lib/x86_64-linux-gnu/perl/5.20/CORE/fakethr.h
  sudo touch /usr/lib/x86_64-linux-gnu/perl/5.20/CORE/perlsfio.h

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

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

[Touch-packages] [Bug 1396611] Re: Cannot install click packages on ISO installs of Ubuntu

[Sebastien Bacher]

Xenial got this change

https://launchpad.net/ubuntu/+source/unity-scope-
click/0.1.1+16.04.20160318-0ubuntu1

"unity-scope-click (0.1.1+16.04.20160318-0ubuntu1) xenial;
urgency=medium

  * Add dependency on packagekit so install of clicks will work on PCs."


it means that installing unity8/unity-scope-click is installing packagekit now 
(and removing the aptdaemon compat layer) which should make things work. Unity8 
still doesn't have the prompting capability needed though it seems, maybe one 
workaround would be to add a plka file allowing local users to install clicks 
without have to auth, since clicks don't have access to system directories it's 
less likely to damage the system so it might be an ok thing to do there?


On, and we still plan to update packagekit at some point (next cycle hopefully) 
so we still need to make click stop using the deprecated interface...

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

Title:
  Cannot install click packages on ISO installs of Ubuntu

Status in Canonical System Image:
  Confirmed
Status in click package in Ubuntu:
  In Progress

Bug description:
  Installing packages from the Ubuntu Store fails under unity8-desktop-
  session mir.

  The error can be reproduced using pkcon:

  mzanetti@noneyet ~/.local/share/ubuntu-download-manager  $  pkcon 
install-local Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click
  Installing files  [=]
  Loading cache [=]
  Resolving dependencies[=]
  Finished  [=]
  Installing files  [=]
  Loading cache [=]
  Resolving dependencies[=]
  Waiting for authentication[=]
  Loading cache [=]
  Resolving dependencies[=]
  Committing changes[=]
  Finished  [=]
  (Reading database ... 588050 files and directories currently installed.)
  Preparing to unpack .../com.ubuntu.developer.robert-ancell.dotty_2_all.click 
...
  Click packages may not be installed directly using dpkg.
  Use 'click install' instead.
  dpkg: error processing archive 
/home/mzanetti/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click
 (--install):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   
/home/mzanetti/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click

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

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

[Touch-packages] [Bug 246381] Re: APT daily cronjobs hangs, prevents other cronjobs to be executed

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.10

---
apt (1.2.10) unstable; urgency=medium

  [ Zhou Mo ]
  * zh_CN.po: update simplified Chinese translation. (100%)

  [ Julian Andres Klode ]
  * test-apt-download-progress: Use a larger file for testing
  * Allow lowering trust level of a hash via config

  [ Michael Vogt ]
  * Use systemd.timer instead of a cron job (Closes: #600262, #709675, #663290)
(LP: #246381, #727685)

  [ David Kalnischkies ]
  * use buffered writing for InRelease splitting

  [ Takuma Yamada ]
  * Japanese program translation update (Closes: 819938)

 -- Michael Vogt   Tue, 05 Apr 2016 20:23:47 +0200

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

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

Title:
  APT daily cronjobs hangs, prevents other cronjobs to be executed

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I've created a cronjob in /etc/cron.daily (a very simple mysqldump)
  and have been looking for weeks why it wouldnt execute... Following
  the advice of a friend I run:

  sudo su -
  run-parts --report /etc/cron.daily 

  Which seemed to hang completely. I straced the process, and it seemed it was 
hanging on the APT cron job; 
  access("/etc/cron.daily/apt", X_OK) = 0
  pipe([3, 4])= 0
  pipe([5, 6])= 0
  clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0xb7db86f8) = 13861
  close(4)= 0
  close(6)= 0
  select(6, [3 5], NULL, NULL, NULL

  I removed the APT cronjob and now the run-parts works fine...  would
  be worth testing but I wonder if all the cronjobs following
  /etc/cron.daily/apt are executed properly...

  Maybe this bug is linked to 
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/86896 ?
  I am using Jeos 8.04 built with uvb - tell me if I can provide any additional 
information, thanks!

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

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

[Touch-packages] [Bug 727685] Re: /etc/cron.daily/apt randomly delays other jobs

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.10

---
apt (1.2.10) unstable; urgency=medium

  [ Zhou Mo ]
  * zh_CN.po: update simplified Chinese translation. (100%)

  [ Julian Andres Klode ]
  * test-apt-download-progress: Use a larger file for testing
  * Allow lowering trust level of a hash via config

  [ Michael Vogt ]
  * Use systemd.timer instead of a cron job (Closes: #600262, #709675, #663290)
(LP: #246381, #727685)

  [ David Kalnischkies ]
  * use buffered writing for InRelease splitting

  [ Takuma Yamada ]
  * Japanese program translation update (Closes: 819938)

 -- Michael Vogt   Tue, 05 Apr 2016 20:23:47 +0200

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

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

Title:
  /etc/cron.daily/apt randomly delays other jobs

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: apt

  Hi,

  (affects 10.04 LTS as well)

  anacron executes
run-parts --report /etc/cron.daily
  daily. run-parts runs the job in /etc/cron.daily one after the other in 
alphabetical order.

  /etc/cron.daily/apt is one of the first to be executed, and contains a
  random_sleep to avoid all ubuntu machines on the world hitting the
  server at the same time. This makes sense, but randomly delays all the
  other tasks in /etc/cron.daily, and causes inconsistencies, e.g.
  logrotates do not cover exactly 24 hours, but sometimes more,
  sometimes less.

  Would be nice to send this apt job either to the background or run it
  as the last job (ie. rename to zzapt or something like this).

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: apt 0.8.3ubuntu7
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  Architecture: amd64
  Date: Wed Mar  2 10:59:29 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/tcsh
  SourcePackage: apt

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

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

[Touch-packages] [Bug 1566660] [NEW] Mount count does not get resettet to 0 after file system check.

[fw114]

Public bug reported:

Mount count does not get resettet to 0 after file system check.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: e2fsprogs 1.42.12-1ubuntu2
Uname: Linux 4.4.6-040406-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Apr  6 08:26:40 2016
InstallationDate: Installed on 2016-01-07 (89 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  Mount count does not get resettet to 0 after file system check.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Mount count does not get resettet to 0 after file system check.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: e2fsprogs 1.42.12-1ubuntu2
  Uname: Linux 4.4.6-040406-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Apr  6 08:26:40 2016
  InstallationDate: Installed on 2016-01-07 (89 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1512100] Re: Blinking screen during the call if you remove the phone from your ear

[Ethan Chang]

Tried rc-proposed #299 image on Arale, I can not reproduce this issue on
device.

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

Title:
  Blinking screen during the call if you remove the phone from your ear

Status in Canonical System Image:
  In Progress
Status in android package in Ubuntu:
  In Progress
Status in powerd package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  I have a problem with my Meizu MX4 (Arale r6). 
  During a call if you remove the phone from your ear, sometimes (not always) 
the screen remains turned off. When you try to push the power button to wake up 
the screen, that starts blinking and it's not possible to hang up. The screen 
remains in that condition even after the end of the call.
  When it keeps blinking I try to hold the button down and in few seconds the 
screen turns black and the phone starts working again. Sometimes, instead, it 
starts working again by itself.

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

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

[Touch-packages] [Bug 1553309] Re: [FFe]: Include FIPS 140-2 into openssl package

[Joy Latten]

New debdiff. 
Added a few more sentences to describe the patch to the patch header.
Also corrected a compiler warning.

** Attachment added: "Patch to include fips selftest and fips support to 
openssl"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309/+attachment/4625642/+files/debdiff.openssl_1.0.2g-1ubuntu3~ppa4

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

Title:
  [FFe]: Include FIPS 140-2 into openssl  package

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This is a request for a Feature Freeze Exception to include FIPS 140-2 
selftest into the openssl package in preparation for the FIPS 140-2 compliance 
for 16.0.4. 
  This patchset will :
   - add ability to config, compile, run with fips option enabled
   - add the selftest files to crypto/fips directory. 
   - minor changes to several algorithms in crypto directory to ensure the 
selftest compile successfully when fips is enabled. 
   
  The selftest will be initiated externally at this point and not internally.
  Hope to have a test package ready early next week.

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

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

[Touch-packages] [Bug 1566657] [NEW] [apt] implement --yes

[buhtz]

Public bug reported:

Please implement the option '--yes' (known from apt-get) in apt itself.

It is not available in Ubuntu 16.04 Beta.

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


** Tags: apt xenial

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

Title:
  [apt] implement --yes

Status in apt package in Ubuntu:
  New

Bug description:
  Please implement the option '--yes' (known from apt-get) in apt
  itself.

  It is not available in Ubuntu 16.04 Beta.

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

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

[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

** No longer affects: gdm

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1556457] Re: [FFe] Demilight (OS/2 weight=350) confuses fontconfig

[Ivan Larionov]

Gunnar, could you please check
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651

I believe it's related to this fontconfig update.

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

Title:
  [FFe] Demilight (OS/2 weight=350) confuses fontconfig

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Fix Released
Status in fontconfig package in Debian:
  Unknown

Bug description:
  [FFe request comment]

  Upgrading to fontconfig 2.11.94 is proposed as a fix of this bug,
  including a fix of certain font weight issues due to the switch from
  fonts-droid to fonts-noto-cjk for Chinese (discussed at bug #1468027)
  where we haven't found any way to work around the problem.

  The proposed upload is available in this PPA:
  https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig-test2

  Changes are listed in the attachment upstream_git-log.txt

  [Original description including updates]

  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug
  1468027.

  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).

  Although it's possible to write (dirty?) hacks for deb-packed fonts,
  this still causes problems for otherwise sourced fonts.

  Archlinux: https://bugs.archlinux.org/task/48550 (fix released,
  upgraded to 2.11.94)

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

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

[Touch-packages] [Bug 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

[Ivan Larionov]

** Description changed:

  I use terminus font in gnome-terminal. After upgrade to the latest
  fonconfig in xenial my terminal font is blurry.
  
  Versions which work as expected:
  
  <= 2.11.1-0ubuntu8
  
  Broken versions:
  
  >= 2.11.1-0ubuntu9
  
  Screenshots attached.
  
  Probably related to this change
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457
+ 
+ Rollback to the following packages fixes this issue:
+ 
+ fontconfig_2.11.1-0ubuntu8_amd64.deb
+ fontconfig-config_2.11.1-0ubuntu8_all.deb
+ libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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

Title:
  Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I use terminus font in gnome-terminal. After upgrade to the latest
  fonconfig in xenial my terminal font is blurry.

  Versions which work as expected:

  <= 2.11.1-0ubuntu8

  Broken versions:

  >= 2.11.1-0ubuntu9

  Screenshots attached.

  Probably related to this change
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457

  Rollback to the following packages fixes this issue:

  fontconfig_2.11.1-0ubuntu8_amd64.deb
  fontconfig-config_2.11.1-0ubuntu8_all.deb
  libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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

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

[Touch-packages] [Bug 1566651] Re: Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

[Ivan Larionov]

** Attachment added: "fontconfig 2.11.1-0ubuntu9"
   
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566651/+attachment/4625619/+files/fontconfig_new.png

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

Title:
  Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I use terminus font in gnome-terminal. After upgrade to the latest
  fonconfig in xenial my terminal font is blurry.

  Versions which work as expected:

  <= 2.11.1-0ubuntu8

  Broken versions:

  >= 2.11.1-0ubuntu9

  Screenshots attached.

  Probably related to this change
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457

  Rollback to the following packages fixes this issue:

  fontconfig_2.11.1-0ubuntu8_amd64.deb
  fontconfig-config_2.11.1-0ubuntu8_all.deb
  libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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

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

[Touch-packages] [Bug 1566651] [NEW] Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

[Ivan Larionov]

Public bug reported:

I use terminus font in gnome-terminal. After upgrade to the latest
fonconfig in xenial my terminal font is blurry.

Versions which work as expected:

<= 2.11.1-0ubuntu8

Broken versions:

>= 2.11.1-0ubuntu9

Screenshots attached.

Probably related to this change
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457

Rollback to the following packages fixes this issue:

fontconfig_2.11.1-0ubuntu8_amd64.deb
fontconfig-config_2.11.1-0ubuntu8_all.deb
libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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


** Tags: xenial

** Attachment added: "fontconfig_old.png"
   
https://bugs.launchpad.net/bugs/1566651/+attachment/4625618/+files/fontconfig_old.png

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

Title:
  Blurry fonts after update to fontconfig 2.11.1-0ubuntu9

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I use terminus font in gnome-terminal. After upgrade to the latest
  fonconfig in xenial my terminal font is blurry.

  Versions which work as expected:

  <= 2.11.1-0ubuntu8

  Broken versions:

  >= 2.11.1-0ubuntu9

  Screenshots attached.

  Probably related to this change
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1556457

  Rollback to the following packages fixes this issue:

  fontconfig_2.11.1-0ubuntu8_amd64.deb
  fontconfig-config_2.11.1-0ubuntu8_all.deb
  libfontconfig1_2.11.1-0ubuntu8_amd64.deb

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

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

[Touch-packages] [Bug 1451256] Re: user "daisy" can log in but user "karel" gets a blank X-screen

[Karel]

The behaviour has slightly changed but it seems clear to me that the same issue 
is still at work.
At the prahical login, there is now a list of accounts to choose from, it does 
include "daisy" but not "karel". There is however a "not listed" to click, and 
that allows me to enter "karel" as login, after password validation everything 
works as expected.

My understanding was and is that the non-working user "karel", though
mentioned in the basic /etc/passwd and /etc/shadow, is missing from some
other list of users, proper to lightdm. I have however failed to find
such a file, perhaps the account names are encrypted into it?

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

Title:
  user "daisy" can log in but user "karel" gets a blank X-screen

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  When logging in as "karel" I get a blank X screen, which is perfectly
  functional as such - from a terminal I can launch "firefox --display
  :0" and so forth - but user Karel does not get a window manager
  active. For newly created user "daisy" everything works as expected.
  Not sure this is a bug, though, the trouble started after some
  twiddling with adding and removing packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Sun May  3 20:31:50 2015
  InstallationDate: Installed on 2014-04-29 (369 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (367 days ago)

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

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

[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.40-2ubuntu9

---
accountsservice (0.6.40-2ubuntu9) xenial; urgency=medium

  * debian/patches/0005-gdm_config_file_path_ubuntu.patch:
Copy patch from Debian packaging to correct the path to the
GDM config file. (LP: #1547297)
  * debian/patches/0007-add-lightdm-support.patch:
Update paths to gdm config directory

 -- Tim Lunn   Wed, 06 Apr 2016 10:59:09 +1000

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

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1458869] Re: multiseat doesn't work after upgrading to 1.14

[Robert Ancell]

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

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

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

Title:
  multiseat doesn't work after upgrading to 1.14

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I read that from 1.10 to 1.14 things changed and that i need to use logind. 
So I removed files that were working with lightdm 1.10 and tried to set it up 
the "logind" way.
  I removed my xorg.conf and got a bare lightdm.conf (see below)
  Am I overlooking something obvious that prevent the second X server to launch 
properly like it used to with version 1.10 ?

  thanks

  I got 2 GPU, 2 screens.
  I configured logind that way :
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/drm/card1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/graphics/fb1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.1/sound/card2
  loginctl attach seat-1 /sys/devices/pci:00/:00:1d.2/usb8

  resulting in those udev rules :
  cat /etc/udev/rules.d/72-seat-drm-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-graphics-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-sound-pci-_03_00_1.rules 
/etc/udev/rules.d/72-seat-usb-pci-_00_1d_2.rules

  TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_03_00_0", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="graphics-pci-_03_00_0", 
ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_03_00_1", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_00_1d_2", ENV{ID_SEAT}="seat-1"

  well now only one seat is working :
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.14.0, UID=0 PID=12879
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.00s] DEBUG: Registered seat module xlocal
  [+0.00s] DEBUG: Registered seat module xremote
  [+0.00s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Monitoring logind for seats
  [+0.01s] DEBUG: New seat added from logind: seat0
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat0: Starting
  [+0.01s] DEBUG: Seat seat0: Creating greeter session
  [+0.01s] DEBUG: Seat seat0: Creating display server of type x
  [+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+0.01s] DEBUG: Using VT 7
  [+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
  [+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.01s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.01s] DEBUG: Launching process 12883: /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.01s] DEBUG: New seat added from logind: seat-1
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat-1 has property CanMultiSession=no
  [+0.01s] DEBUG: Seat seat-1: Starting
  [+0.01s] DEBUG: Seat seat-1: Creating greeter session
  [+0.01s] DEBUG: Seat seat-1: Creating display server of type x
  [+0.01s] DEBUG: Seat seat-1: Starting local X display
  [+0.01s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+0.01s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+0.01s] DEBUG: DisplayServer x-1: Launching X Server
  [+0.01s] DEBUG: Launching process 12885: /usr/bin/X :1 -seat seat-1 -sharevts 
-auth /var/run/lightdm/root/:1 -nolisten tcp
  [+0.01s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat1
  [+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
  [+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+0.01s] DEBUG: User clarisse added
  [+0.01s] DEBUG: User lotso added
  

[Touch-packages] [Bug 1554040] Re: Allow hiding authentication data in scope binary

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

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

** Changed in: unity-scopes-shell (Ubuntu)
   Importance: Undecided => High

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

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

Title:
  Allow hiding authentication data in scope binary

Status in unity-scopes-api package in Ubuntu:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  The current scope API doesn't allow the developer to specify the OAuth client 
keys at runtime, they must reside in the .service files which end up installed 
on the filesystem.
  Some people are concerned about exposing their API keys, and would rather 
embed them in their scope binary and specify them at runtime. While 
acknowledging that this will actually not improve the security, this 
possibility is offered by all other Online Accounts APIs, and it would be nice 
if scopes offered this too.

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

-- 
Mailing list: https://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 1458869] Re: multiseat doesn't work after upgrading to 1.14

[Benoit Barthelet]

It isn't.

benoit barthelet
http://pgp.mit.edu/pks/lookup?op=get&search=0xF150E01A72F6D2EE
On 6 Apr 2016 06:51, "Robert Ancell"  wrote:

> Is this still a problem?
>
> ** Changed in: lightdm (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1458869
>
> Title:
>   multiseat doesn't work after upgrading to 1.14
>
> Status in lightdm package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I read that from 1.10 to 1.14 things changed and that i need to use
> logind. So I removed files that were working with lightdm 1.10 and tried to
> set it up the "logind" way.
>   I removed my xorg.conf and got a bare lightdm.conf (see below)
>   Am I overlooking something obvious that prevent the second X server to
> launch properly like it used to with version 1.10 ?
>
>   thanks
>
>   I got 2 GPU, 2 screens.
>   I configured logind that way :
>   loginctl attach seat-1
> /sys/devices/pci:00/:00:07.0/:03:00.0/drm/card1
>   loginctl attach seat-1
> /sys/devices/pci:00/:00:07.0/:03:00.0/graphics/fb1
>   loginctl attach seat-1
> /sys/devices/pci:00/:00:07.0/:03:00.1/sound/card2
>   loginctl attach seat-1 /sys/devices/pci:00/:00:1d.2/usb8
>
>   resulting in those udev rules :
>   cat /etc/udev/rules.d/72-seat-drm-pci-_03_00_0.rules
> /etc/udev/rules.d/72-seat-graphics-pci-_03_00_0.rules
> /etc/udev/rules.d/72-seat-sound-pci-_03_00_1.rules
> /etc/udev/rules.d/72-seat-usb-pci-_00_1d_2.rules
>
>   TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_03_00_0",
> ENV{ID_SEAT}="seat-1"
>   TAG=="seat", ENV{ID_FOR_SEAT}=="graphics-pci-_03_00_0",
> ENV{ID_SEAT}="seat-1"
>   TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_03_00_1",
> ENV{ID_SEAT}="seat-1"
>   TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_00_1d_2",
> ENV{ID_SEAT}="seat-1"
>
>   well now only one seat is working :
>   [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
>   [+0.00s] DEBUG: Starting Light Display Manager 1.14.0, UID=0 PID=12879
>   [+0.00s] DEBUG: Loading configuration dirs from
> /usr/share/lightdm/lightdm.conf.d
>   [+0.00s] DEBUG: Loading configuration from
> /usr/share/lightdm/lightdm.conf.d/01_debian.conf
>   [+0.00s] DEBUG: Loading configuration dirs from
> /usr/local/share/lightdm/lightdm.conf.d
>   [+0.00s] DEBUG: Loading configuration dirs from
> /etc/xdg/lightdm/lightdm.conf.d
>   [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
>   [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
>   [+0.00s] DEBUG: Registered seat module xlocal
>   [+0.00s] DEBUG: Registered seat module xremote
>   [+0.00s] DEBUG: Registered seat module unity
>   [+0.01s] DEBUG: Monitoring logind for seats
>   [+0.01s] DEBUG: New seat added from logind: seat0
>   [+0.01s] DEBUG: Loading properties from config section SeatDefaults
>   [+0.01s] DEBUG: Seat seat0: Starting
>   [+0.01s] DEBUG: Seat seat0: Creating greeter session
>   [+0.01s] DEBUG: Seat seat0: Creating display server of type x
>   [+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child
> process "plymouth" (No such file or directory)
>   [+0.01s] DEBUG: Using VT 7
>   [+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
>   [+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
>   [+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to
> /var/run/lightdm/root/:0
>   [+0.01s] DEBUG: DisplayServer x-0: Launching X Server
>   [+0.01s] DEBUG: Launching process 12883: /usr/bin/X :0 -seat seat0 -auth
> /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
>   [+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X
> server :0
>   [+0.01s] DEBUG: New seat added from logind: seat-1
>   [+0.01s] DEBUG: Loading properties from config section SeatDefaults
>   [+0.01s] DEBUG: Seat seat-1 has property CanMultiSession=no
>   [+0.01s] DEBUG: Seat seat-1: Starting
>   [+0.01s] DEBUG: Seat seat-1: Creating greeter session
>   [+0.01s] DEBUG: Seat seat-1: Creating display server of type x
>   [+0.01s] DEBUG: Seat seat-1: Starting local X display
>   [+0.01s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
>   [+0.01s] DEBUG: DisplayServer x-1: Writing X server authority to
> /var/run/lightdm/root/:1
>   [+0.01s] DEBUG: DisplayServer x-1: Launching X Server
>   [+0.01s] DEBUG: Launching process 12885: /usr/bin/X :1 -seat seat-1
> -sharevts -auth /var/run/lightdm/root/:1 -nolisten tcp
>   [+0.01s] DEBUG: DisplayServer x-1: Waiting for ready signal from X
> server :1
>   [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
>   [+0.01s] DEBUG: Registering seat with bus path
> /org/freedesktop/DisplayManager/Seat0
>   [+0.01s] DEBUG: Registering seat with bus path
> /org/freedesktop/DisplayManager/Seat1
>   [+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 

[Touch-packages] [Bug 1542906] Re: unity::scopes::testing::TypedScopeFixture<> usage always fails

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

Title:
  unity::scopes::testing::TypedScopeFixture<> usage always fails

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

Bug description:
  Following the official documentation at the Ubuntu developer gateway
  https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1 I tried to
  create a scope fixture to use in my test cases using the
  unity::scopes::testing::TypedScopeFixture<> template to wrap my Scope
  class.

  The unit tests always fail at runtime with an error similar to the following.
[ RUN  ] ScopeFixture.surfacing_query
/usr/include/unity-scopes-1.0/unity/scopes/testing/TypedScopeFixture.h:90: 
Failure
Expected: scope->start(ScopeTraits::name()) doesn't throw an 
exception.

  Turns out the problem is that the TypedScopeFixture template class
  does not call the required initialization functions in its
  constructor.  It's not possible to work around this by driving from
  TypedScopeFixture because the required initialization functions (for
  example, TypedScopeFixtureHelper::set_scope_directory()) are private
  static member functions in another class.  The only workaround is to
  include a modified copy of TypedScopeFixture.h in my own project.

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

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

[Touch-packages] [Bug 1378396] Re: Guest session needs to remind user that data will be deleted

[Robert Ancell]

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

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

** This bug has been marked a duplicate of bug 435930
   Guest session does not warn about temporary nature of files

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

Title:
  Guest session needs to remind user that data will be deleted

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu gives users a "guest session" that looks and feels pretty much
  like a regular session, but on logging out it deletes the user's data
  without adequate warning. This is a serious problem because users,
  even long-time users such as myself, may not expect this, and somebody
  they care about *will* lose important data. For examples, see bug
  #435930: the initial report, and comment #3, and comment #7. (Those
  examples are from before there was a warning dialogue at the start of
  the session, but that by itself surely won't prevent more
  occurrences.)

  A set of design changes to fix this bug properly would need to involve
  reminding the user at appropriate times while using the session that
  all data they store in the "home" directory is temporary. This could
  include changing the desktop theme and background to something
  visually different from a regular session; changes to the file-save
  and directory-browsing dialogs to remind users that Desktop and
  Documents and so on are not permanent storage locations, and more. I
  remember using SuSE Linux a few years ago, and you could log in as
  root, and the root session was visually distinguished in several ways
  as a reminder.

  The behaviour of a guest session should be specified in
   (see bug #882296, "No
  complete specification for how Ubuntu sessions are supposed to work").

  Bug #435930 and bug #1270788 ask for reminder messages at log-in and
  log-out time respectively, but I see those as only crude attempts to
  ameliorate the real problem.

  (I'm not sure what projects/packages this bug report should target:
  lightdm, gnome-session, Ayatana Design, ...)

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

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

[Touch-packages] [Bug 1367015] Re: when booting, screen turns white after "init-bottom"

[Robert Ancell]

Is this still occurring?

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

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

Title:
  when booting, screen turns white after "init-bottom"

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  This happen each time I boot after hours of shut down.
  When booting, screen turns all white right after text "init-bottom" or 
something like that. Can't access cli, so I have to use power button to reboot. 
Usually, after 4-5 forced reboots, then system will run normal.
  Notice that booting into recovery mode always work fine, but it won't show 
normal resolution (only 1024x768). So this "white-screen" only happen to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  9 05:11:01 2014
  InstallationDate: Installed on 2014-08-25 (14 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=eka
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  LightdmGreeterLog:
   init: indicator-power main process (2043) killed by TERM signal
   init: indicator-application main process (2047) killed by TERM signal
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:791): WARNING **: Failed to load user background: 
Failed to open file '/media/eka/BUMI/pic/1000_origami_cranes.jpg': Permission 
denied
   init: indicator-power main process (833) killed by TERM signal
   init: indicator-application main process (843) killed by TERM signal
  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/1367015/+subscriptions

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

[Touch-packages] [Bug 1394863] Re: Lightdm will not autologin and open a second seat after update from Ubuntu 14.04 to 14.10

[Robert Ancell]

See https://wiki.ubuntu.com/MultiseatTeam/Instructions

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

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

Title:
  Lightdm will not autologin and open a second seat after update from
  Ubuntu 14.04 to 14.10

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  OS version:
  Description:  Ubuntu 14.10
  Release:  14.10

  Lightdm version info:

  lightdm:
Installiert:   1.12.1-0ubuntu1
Installationskandidat: 1.12.1-0ubuntu1
Versionstabelle:
   *** 1.12.1-0ubuntu1 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ utopic/main 
amd64 Packages
  100 /var/lib/dpkg/status

  With Ubuntu 14.04 lightdm opened VT7 with autologin 'mythtv' and a
  sencod VT8 with no autologin (for parallel login). Now, with Ubuntu
  14.10 there is no autologin and only VT7 with the login screen. The
  /etc/lightdm/lightdm.conf is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.1-0ubuntu1
  Uname: Linux 3.13.11-0313-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Nov 21 05:56:06 2014
  InstallationDate: Installed on 2014-11-20 (0 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:4455): WARNING **: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
   
   ** (lightdm-gtk-greeter:4455): WARNING **: Failed to load user image: Datei 
»/home/stefan/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:4294): WARNING **: Error retrieving accessibility 
bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus 
was not provided by any .service files
   
   ** (lightdm-gtk-greeter:4294): WARNING **: Failed to load user image: Datei 
»/home/stefan/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   
   (lightdm-gtk-greeter:4294): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO 
error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1394863/+subscriptions

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

[Touch-packages] [Bug 1071187] Re: Konsole profiles widget sorts entries wrong

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => konsole (Ubuntu)

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

Title:
  Konsole profiles widget sorts entries wrong

Status in konsole package in Ubuntu:
  New

Bug description:
  After upgrading to Quantal, konsole profiles appear in random-looking order
  (In Precise they're in alphabetical order).
  This makes it very difficult (time-consuming) to find desired profile.

  (I'm not sure if the package designation is correct, as it's not Konsole 
itself 
  where the bug appears, but I can't think of any other obvious choice either.)
  --- 
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   32.248211] init: plymouth-stop pre-start process (1539) 
terminated with status 1
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=c7357f23-1175-4f90-bd31-1c3d8d5e7b3f
  MachineType: Tranquil PC Atom PC
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=46f26696-67e7-4b74-8821-c3c0b548370d ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  quantal
  Uname: Linux 3.5.0-17-generic i686
  UpgradeStatus: Upgraded to quantal on 2012-10-25 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 08/14/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LF94510J.86A.0103.2008.0814.1910
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D945GCLF2
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE46416-101
  dmi.chassis.type: 3
  dmi.chassis.vendor: Tranquil PC LTD
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLF94510J.86A.0103.2008.0814.1910:bd08/14/2008:svnTranquilPC:pnAtomPC:pvrATOM330_A:rvnIntelCorporation:rnD945GCLF2:rvrAAE46416-101:cvnTranquilPCLTD:ct3:cvr:
  dmi.product.name: Atom PC
  dmi.product.version: ATOM330_A
  dmi.sys.vendor: Tranquil PC

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

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

[Touch-packages] [Bug 1074843] Re: plymouth programs are running altough system startup finished

[Robert Ancell]

Closing assumed fixed.

** Package changed: lightdm (Ubuntu) => plymouth (Ubuntu)

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

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

Title:
  plymouth programs are running altough system startup finished

Status in plymouth package in Ubuntu:
  Fix Released

Bug description:
  Below are the running processes :
  -
  j@j-VB:~$ ps axl | head -1 && ps axl | grep -i ply | grep -v "grep"
  F   UID   PID  PPID PRI  NIVSZ   RSS WCHAN  STAT TTYTIME COMMAND
  5 0   199 1  20   0  46524   688 epoll_ S?  0:00 
/sbin/plymouthd --mode=boot --attach-to-session
  4 0   380 1  20   0  19636  1004 epoll_ Ss   ?  0:00 
plymouth-upstart-bridge
  j@j-VB:~$ 
  -

  Is there a way to use init in order to launch plymouthd at shutdown ?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: plymouth 0.8.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CurrentDmesg: [   15.224003] init: lightdm main process (818) killed by TERM 
signal
  Date: Sun Nov  4 10:57:16 2012
  DefaultPlymouth: Error: command ['readlink', 
'/etc/alternatives/default.plymouth'] failed with exit code 1:
  InstallationDate: Installed on 2012-10-20 (14 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=cd43b074-5f0e-46e5-8362-13424056d921 ro quiet splash vt.handoff=7
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=cd43b074-5f0e-46e5-8362-13424056d921 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: Error: command ['readlink', '/etc/alternatives/text.plymouth'] 
failed with exit code 1:
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  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/ubuntu/+source/plymouth/+bug/1074843/+subscriptions

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

[Touch-packages] [Bug 952765] Re: Switch user doesn't work when screen is locked

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  Switch user doesn't work when screen is locked

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  When Switch user is clicked in login screen the screen goes blank for
  a while and returns to login screen. When typed correct password for
  current user the following error message is shown on desktop:

  "The name org.gnome.DisplayManager was not provided by any .service
  files"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar 12 09:37:42 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)

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

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

[Touch-packages] [Bug 1086331] Re: Last session type doesn't get recorded

[Robert Ancell]

Still occurring?

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

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

Title:
  Last session type doesn't get recorded

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  In an NFS4 with ldap-auth environment the last session type doesn't
  get recorded per user. The default session (Xubuntu in our case) is
  pre-selected, whatever session one last used. Not sure if that is a
  bug in lightdm or accountsservice.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Tue Dec  4 12:09:55 2012
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1086331/+subscriptions

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

[Touch-packages] [Bug 1382956] Re: cannot change hdmi monitor resolution anymore

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  cannot change hdmi monitor resolution anymore

Status in xorg-server package in Ubuntu:
  New

Bug description:
  since a few weeks cannot set resolution to 1360 x 768 anymore...didnt
  change anything...just updates..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Oct 19 12:38:27 2014
  InstallationDate: Installed on 2014-06-09 (131 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=rolf
   autologin-user-timeout=0
   user-session=Lubuntu
   greeter-session=lightdm-gtk-greeter
  LightdmGreeterLog: ** (lightdm-gtk-greeter:30754): WARNING **: Failed to load 
user image: Failed to open file '/home/rolf/.face': No such file or directory
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1225): WARNING **: Failed to 
load user image: Failed to open file '/home/rolf/.face': No such file or 
directory
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

[Robert Ancell]

Can you check your config is valid by running:
$ lightdm --show-config
from a terminal.

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

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

Title:
  lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Ubuntu 14.04.1LTS
  IIyama 19" Pro-Lite Touchscreen
  Dell 17" regular monitor

  Due to another bug in the detection of input devices I had to write a
  script to tell Ubuntu which screen to use the touch from the
  touchscreen.

  so I put the following two entries into a basic bash script based on xinput 
list and xrandr -q 
  
  #!/bin/bash
  xinput map-to-output 12 DVI-I-1
  xrandr --output DVI-I-1 --primary
  =

  I added this script to 
/usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf
  and the contents look like this.
  
  [SeatDefaults]
  greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  session-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  
  When I start a user session the touchscreen is calibrated and works normally 
with the touch happening on the touchscreen.
  As soon as I logoff into LightDM the touch calibration is off moving the 
pointer a logarithmic distance from the left of the touchscreen. 

  As soon as I log in again, no problems, touch works great, log back
  out into the lightDM greeter and boom touch is all crazy.

  Can lightdm please detect that a touchscreen can only accept touch input and 
output to the touchscreen device??
  Or at least have lightdm actually run the script when given?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 22:11:38 2014
  InstallationDate: Installed on 2014-11-03 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=boerske
  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/1392064/+subscriptions

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

[Touch-packages] [Bug 1458869] Re: multiseat doesn't work after upgrading to 1.14

[Robert Ancell]

Is this still a problem?

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

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

Title:
  multiseat doesn't work after upgrading to 1.14

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I read that from 1.10 to 1.14 things changed and that i need to use logind. 
So I removed files that were working with lightdm 1.10 and tried to set it up 
the "logind" way.
  I removed my xorg.conf and got a bare lightdm.conf (see below)
  Am I overlooking something obvious that prevent the second X server to launch 
properly like it used to with version 1.10 ?

  thanks

  I got 2 GPU, 2 screens.
  I configured logind that way :
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/drm/card1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/graphics/fb1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.1/sound/card2
  loginctl attach seat-1 /sys/devices/pci:00/:00:1d.2/usb8

  resulting in those udev rules :
  cat /etc/udev/rules.d/72-seat-drm-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-graphics-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-sound-pci-_03_00_1.rules 
/etc/udev/rules.d/72-seat-usb-pci-_00_1d_2.rules

  TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_03_00_0", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="graphics-pci-_03_00_0", 
ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_03_00_1", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_00_1d_2", ENV{ID_SEAT}="seat-1"

  well now only one seat is working :
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.14.0, UID=0 PID=12879
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.00s] DEBUG: Registered seat module xlocal
  [+0.00s] DEBUG: Registered seat module xremote
  [+0.00s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Monitoring logind for seats
  [+0.01s] DEBUG: New seat added from logind: seat0
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat0: Starting
  [+0.01s] DEBUG: Seat seat0: Creating greeter session
  [+0.01s] DEBUG: Seat seat0: Creating display server of type x
  [+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+0.01s] DEBUG: Using VT 7
  [+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
  [+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.01s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.01s] DEBUG: Launching process 12883: /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.01s] DEBUG: New seat added from logind: seat-1
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat-1 has property CanMultiSession=no
  [+0.01s] DEBUG: Seat seat-1: Starting
  [+0.01s] DEBUG: Seat seat-1: Creating greeter session
  [+0.01s] DEBUG: Seat seat-1: Creating display server of type x
  [+0.01s] DEBUG: Seat seat-1: Starting local X display
  [+0.01s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+0.01s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+0.01s] DEBUG: DisplayServer x-1: Launching X Server
  [+0.01s] DEBUG: Launching process 12885: /usr/bin/X :1 -seat seat-1 -sharevts 
-auth /var/run/lightdm/root/:1 -nolisten tcp
  [+0.01s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat1
  [+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
  [+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+0.01s] DEBUG: User clarisse added
  [+0.01s] DEBUG: User lotso added
  [+0.01s] DEBUG: User max added
  [+0.03s] DEBUG: Pro

[Touch-packages] [Bug 1037973] Re: authorization procedure locks up after administrator password changed to null

[Robert Ancell]

Closing assuming fixed.

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

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

Title:
  authorization procedure locks up after administrator password changed
  to null

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  i changed the administrator password to null string. after that I tried to 
change it to some real string i could not pass the unlocking procedure of the 
password change screen, the null string dont work and the previous password 
dont work as well.
  however the installation is now unprotected, as i am able to log in into 
administrator user account without password.
  I tried to revert to earlier version of ubuntu, but the bug spilled to there 
too.

  If i knew how, i would delete and reinstall the ubuntu, saving my data
  firs, but as the ubuntu is installed parallel to windows, it is beyond
  my skills

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

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

[Touch-packages] [Bug 877140] Re: Lightdm hangs when logging in using empty username with smartcard and pam-pkcs11

[Robert Ancell]

Closing assumed fixed.

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

Title:
  Lightdm hangs when logging in using empty username with smartcard and
  pam-pkcs11

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  GDM was able to auto-detect user name when logging in using pam-pkcs11. The 
name was taken from certificates mapping.
  In lightdm however if one tries to login with empty username the module 
correctly asks for smart card PIN and then hangs, writing in log on failed 
assertion.

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

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

[Touch-packages] [Bug 1458869] Re: multiseat doesn't work after upgrading to 1.14

[Robert Ancell]

See https://wiki.ubuntu.com/MultiseatTeam/Instructions

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

Title:
  multiseat doesn't work after upgrading to 1.14

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I read that from 1.10 to 1.14 things changed and that i need to use logind. 
So I removed files that were working with lightdm 1.10 and tried to set it up 
the "logind" way.
  I removed my xorg.conf and got a bare lightdm.conf (see below)
  Am I overlooking something obvious that prevent the second X server to launch 
properly like it used to with version 1.10 ?

  thanks

  I got 2 GPU, 2 screens.
  I configured logind that way :
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/drm/card1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.0/graphics/fb1
  loginctl attach seat-1 
/sys/devices/pci:00/:00:07.0/:03:00.1/sound/card2
  loginctl attach seat-1 /sys/devices/pci:00/:00:1d.2/usb8

  resulting in those udev rules :
  cat /etc/udev/rules.d/72-seat-drm-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-graphics-pci-_03_00_0.rules 
/etc/udev/rules.d/72-seat-sound-pci-_03_00_1.rules 
/etc/udev/rules.d/72-seat-usb-pci-_00_1d_2.rules

  TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_03_00_0", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="graphics-pci-_03_00_0", 
ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_03_00_1", ENV{ID_SEAT}="seat-1"
  TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_00_1d_2", ENV{ID_SEAT}="seat-1"

  well now only one seat is working :
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.14.0, UID=0 PID=12879
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.00s] DEBUG: Registered seat module xlocal
  [+0.00s] DEBUG: Registered seat module xremote
  [+0.00s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Monitoring logind for seats
  [+0.01s] DEBUG: New seat added from logind: seat0
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat0: Starting
  [+0.01s] DEBUG: Seat seat0: Creating greeter session
  [+0.01s] DEBUG: Seat seat0: Creating display server of type x
  [+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+0.01s] DEBUG: Using VT 7
  [+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
  [+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.01s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.01s] DEBUG: Launching process 12883: /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.01s] DEBUG: New seat added from logind: seat-1
  [+0.01s] DEBUG: Loading properties from config section SeatDefaults
  [+0.01s] DEBUG: Seat seat-1 has property CanMultiSession=no
  [+0.01s] DEBUG: Seat seat-1: Starting
  [+0.01s] DEBUG: Seat seat-1: Creating greeter session
  [+0.01s] DEBUG: Seat seat-1: Creating display server of type x
  [+0.01s] DEBUG: Seat seat-1: Starting local X display
  [+0.01s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+0.01s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+0.01s] DEBUG: DisplayServer x-1: Launching X Server
  [+0.01s] DEBUG: Launching process 12885: /usr/bin/X :1 -seat seat-1 -sharevts 
-auth /var/run/lightdm/root/:1 -nolisten tcp
  [+0.01s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat1
  [+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
  [+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+0.01s] DEBUG: User clarisse added
  [+0.01s] DEBUG: User lotso added
  [+0.01s] DEBUG: User max added
  [+0.03s] DEBUG: Process 12885 exited with return value 

[Touch-packages] [Bug 877140] Re: Lightdm hangs when logging in using empty username with smartcard and pam-pkcs11

[Robert Ancell]

Closing assumed fixed.

** No longer affects: lightdm

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

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

Title:
  Lightdm hangs when logging in using empty username with smartcard and
  pam-pkcs11

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  GDM was able to auto-detect user name when logging in using pam-pkcs11. The 
name was taken from certificates mapping.
  In lightdm however if one tries to login with empty username the module 
correctly asks for smart card PIN and then hangs, writing in log on failed 
assertion.

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

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

[Touch-packages] [Bug 918636] Re: No way to select session when loggind in using 'Other'

[Robert Ancell]

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

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

Title:
  No way to select session when loggind in using 'Other'

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  If my account is listed in lightdm screen and I use that option,
  selecting the session type (e.g. xmonad) wworks as expected. If
  logging in as 'Other' -> type username -> type password and I select
  session type when entering the username, it's back to default once I
  get to the password screen. Selecting here a non-system-default
  session will not take any effect.

  So for correct functioning
  a) the user selection made when entering the username needs to be preserved 
(or the session type selection disabled there)
  b) the session selected in the password entering stage needs to actually take 
effect
  c) If I use the 'entering username' way of login, my last selection should be 
preserved

  Ubuntu 11.10 i386. Accounts in NIS, Authentication using kerberos

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

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

[Touch-packages] [Bug 1132009] Re: lightdm crashed with SIGSEGV in check_stopped()

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  lightdm crashed with SIGSEGV in check_stopped()

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  A crash message poped up.. yet lightdm hasn't started on boot. So I
  had to do 'sudo lightdm restart' thing to get it running.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: lightdm 1.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Tue Feb 19 12:07:59 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2012-12-07 (77 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=false
   greeter-show-remote-login=false
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x410518:  mov0x28(%rax),%ecx
   PC (0x00410518) ok
   source "0x28(%rax)" (0xaad2) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   g_closure_add_marshal_guards () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_closure_add_marshal_guards()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1101204] Re: lightdm crashed with SIGSEGV in magazine_chain_pop_head()

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  lightdm crashed with SIGSEGV in magazine_chain_pop_head()

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  After applying updates of Thurs Jan 17 2013 , login manager failed to
  complete login process as usual and would not complete transfer to
  desktop session. Applied updates of Fri Jan 18, using terminal mode
  rebooted same problem, rebooted into recovery mode ran dpkg to fix
  broken packages and applied seven more updates. Was able then to login
  normally, have not tried to reboot again, as immediately upon starting
  desktop session apport  notification activated to report this bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Jan 18 06:17:42 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2012-12-11 (38 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121210)
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f6317c8b5a2 :mov
0x8(%rdx),%rbx
   PC (0x7f6317c8b5a2) ok
   source "0x8(%rdx)" (0x7f630008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1161433] Re: User with passwords containing deadkeys may experience problems logging in.

[Robert Ancell]

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

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

Title:
  User with passwords containing deadkeys may experience problems
  logging in.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I found a bug that leaves a users unable to log his account in a TTY.

  the bug occurs when the user has its keyboard layout set to support deadkeys. 
and chooses a password with a "^" character.
  The graphics interface will not support deadkeys whereas the textmode login 
(without lightdm) does.

  What i expect to happen:
  that it does not matter wich login i use, they will be consistent.

  What actually happens:
  So when a user graphicaly creates a password: "ab[shift-6]c" ([shift-6] is 
the ^ char  on my keyboard)  
  it will be intepretated  as "ab^c"  and when he uses the spacebar 
"ab[shift-6][space]c" it is "ab^ c".

  the problem is whatever you try to login in TTY it wont work.

  the other way around is the same a password with the "^" created in
  TTY wont be able to login in graphical.

  exalt@edlap:~$ lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  exalt@edlap:~$ apt-cache policy lightdm
  lightdm:
Installed: 1.4.0-0ubuntu2
Candidate: 1.4.0-0ubuntu2
Version table:
   *** 1.4.0-0ubuntu2 0
  500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  exalt@edlap:~$ echo $LANG # both in grapical and TTY
  en_US.UTF-8

  exalt@edlap:~$ sudo cat /etc/default/keyboard
  [sudo] password for exalt: 
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="us"
  XKBVARIANT="intl"
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 28 15:25:34 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2013-03-20 (7 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  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/1161433/+subscriptions

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

[Touch-packages] [Bug 1467079] Re: Seats do not start

[Robert Ancell]

See https://wiki.ubuntu.com/MultiseatTeam/Instructions

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

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

Title:
  Seats do not start

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  In trusty, I was able to get a second login screen by defining two
  seats in the lightdm config. This does not work any more in vivid.

  I have the following file:
/usr/share/lightdm/lightdm.conf.d/60-seats.conf

  with contents:
[Seat:0]
user-session=ubuntu

[Seat:1]
user-session=ubuntu

  In trusty, this starts two login screens on vt7 and vt8.
  In vivid, I just get the default seat on vt7. The config entries seem to be 
ignored.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 20 13:11:47 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-12 (798 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (57 days ago)

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

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

[Touch-packages] [Bug 1452373] Re: Keyboard language switching shortcut doesn't work

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  Keyboard language switching shortcut doesn't work

Status in unity package in Ubuntu:
  New

Bug description:
  In lightdm's login page the shortcut keys for switching the keyboard language 
don't work.
  As a result, every time you resume from suspend or want to unlock the 
computer you have to use your mouse to switch the language back to English in 
order to enter your password. Having to do this every time is slow and 
frustrating.

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

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

[Touch-packages] [Bug 1464530] Re: Black screen after Kernel update Dell XPS15, NVidia GeForce GT 750M

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Black screen after Kernel  update Dell XPS15, NVidia GeForce GT 750M

Status in xorg-server package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  After upgrading to the kernel version 3.19.0-20-generic I only see a black 
screen when the login screen should appea.
  I can hear the "drum roll" of the login screen, so I guess it's  a problem 
with the graphics driver / display manager.

  I'm currently using the NVIDIA binary driver - version 346.59 from 
nvidia-346-updates (proprietary).
  I've already tried every other NVIDIA driver offered in the "Additional 
Drivers Tab" for "Software and Updates".

  Booting with the previous kernel 3.19.0-18-generic works fine.

  The machine is a DELL XPS 15 model from 2015.

  $lshw
  euler 
  description: Computer
  width: 64 bits
  capabilities: smbios-2.7 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 15GiB
   *-cpu
product: Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
size: 3102MHz
capacity: 3300MHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat 
epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust 
bmi1 avx2 smep bmi2 erms invpcid xsaveopt cpufreq
   *-pci
description: Host bridge
product: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 06
width: 32 bits
clock: 33MHz
  *-pci:0
   description: PCI bridge
   product: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 
Controller
   vendor: Intel Corporation
   physical id: 1
   bus info: pci@:00:01.0
   version: 06
   width: 32 bits
   clock: 33MHz
   capabilities: pci pm msi pciexpress normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:26 ioport:e000(size=4096) 
memory:f600-f70f ioport:e000(size=301989888)
 *-display UNCLAIMED
  description: 3D controller
  product: GK107M [GeForce GT 750M]
  vendor: NVIDIA Corporation
  physical id: 0
  bus info: pci@:02:00.0
  version: a1
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress bus_master cap_list
  configuration: latency=0
  resources: memory:f600-f6ff memory:e000-efff 
memory:f000-f1ff ioport:e000(size=128) memory:f700-f707
  *-display
   description: VGA compatible controller
   product: 4th Gen Core Processor Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:f740-f77f 
memory:d000-dfff ioport:f000(size=64)
  *-multimedia:0
   description: Audio device
   product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:16 memory:f7c1c000-f7c1
  *-generic:0 UNCLAIMED
   description: Signal processing controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical 

[Touch-packages] [Bug 1566423] Re: Update to PHP7.0 build dependencies

[Launchpad Bug Tracker]

This bug was fixed in the package libvpx - 1.5.0-2ubuntu1

---
libvpx (1.5.0-2ubuntu1) xenial; urgency=medium

  * Update to PHP7.0 build-dependencies (LP: #1566423).

 -- Nishanth Aravamudan   Tue, 05 Apr
2016 09:38:23 -0700

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

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

Title:
  Update to PHP7.0 build dependencies

Status in libvpx package in Ubuntu:
  Fix Released

Bug description:
  Update to PHP7.0 build-dependencies.

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

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

[Touch-packages] [Bug 1451256] Re: user "daisy" can log in but user "karel" gets a blank X-screen

[Robert Ancell]

Sounds like a broken session for some reason - is this still occurring?

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

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

Title:
  user "daisy" can log in but user "karel" gets a blank X-screen

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  When logging in as "karel" I get a blank X screen, which is perfectly
  functional as such - from a terminal I can launch "firefox --display
  :0" and so forth - but user Karel does not get a window manager
  active. For newly created user "daisy" everything works as expected.
  Not sure this is a bug, though, the trouble started after some
  twiddling with adding and removing packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Sun May  3 20:31:50 2015
  InstallationDate: Installed on 2014-04-29 (369 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (367 days ago)

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

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

[Touch-packages] [Bug 1564616] Re: detaching lightdm into background

[Robert Ancell]

Debian does it differently - is there any advantage over each method?

I'm wondering if we should just copy the Debian init script entirely,
given the Ubuntu version seems very out of date.

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

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

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

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

Title:
  detaching lightdm into background

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi

  When starting /etc/init.d/lightdm (either directly from root console
  or through SysV init), it will get stuck because lightdm doesn't fork
  into background when starting.

  Please could you add --background option to start-stop-daemon to fix
  this? (note: the debian lightdm package already does this)

  This change is needed for ubuntuBSD (which uses SysV init to manage
  system daemons).

  Thank you!

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

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

[Touch-packages] [Bug 1548534] Re: 1.16.7 installation fails with 'failed to preconfigure with exit status 30'

[Robert Ancell]

is this still occurring?

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

Title:
  1.16.7 installation fails with 'failed to preconfigure with exit
  status 30'

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu Wily and lightdm has been failing to install for the
  past couple weeks. I've tried everything from removing the package and
  doing a clean install to reverting to an older version, but it always
  fails with the same error.  Here's the error that I  get when running
  the install:

  --
  Preconfiguring packages ...
  lightdm failed to preconfigure, with exit status 30
  Selecting previously unselected package lightdm.
  .
  .
  .
  .
  Setting up lightdm (1.16.7-0ubuntu1) ...
  dpkg: error processing package lightdm (--configure): 
subprocess installed post-installation script returned error exit status 30
  --

  With the last reboot, I can no longer load the desktop.

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

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

[Touch-packages] [Bug 1564616] Re: detaching lightdm into background

[Robert Ancell]

Also, a merge proposal is easier to handle than a diff.

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

Title:
  detaching lightdm into background

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi

  When starting /etc/init.d/lightdm (either directly from root console
  or through SysV init), it will get stuck because lightdm doesn't fork
  into background when starting.

  Please could you add --background option to start-stop-daemon to fix
  this? (note: the debian lightdm package already does this)

  This change is needed for ubuntuBSD (which uses SysV init to manage
  system daemons).

  Thank you!

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

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

[Touch-packages] [Bug 1486140] Re: No login with lightdm possible when on the dock

[Robert Ancell]

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

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

Title:
  No login with lightdm possible when on the dock

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Two days ago I did the upgrade to Xubuntu 15.04 on my neighbors Dell
  D620. Since the upgrade I am not able to boot the laptop when on the
  docking station (with 90W power supply). All I get is a white screen
  with the mouse cursor in the centre which I am able to move. When I
  boot the system without the docking station everything works fine. I
  have now changed the default login manager to gdm and everything works
  fine also, on and off the docking station. This is reproducable
  always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-release-upgrader-core 1:15.04.14
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic i686
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: i386
  CrashDB: ubuntu
  Date: Tue Aug 18 18:41:34 2015
  InstallationDate: Installed on 2014-11-18 (273 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to vivid on 2015-08-16 (2 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1517569] Re: after change my password using a character * i was unable to login in graphic mode, but in terminal it works ok, i change to a password without * and it works fine i

[Robert Ancell]

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

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

Title:
  after change my password using a character * i was unable to login in
  graphic mode, but in terminal it works ok, i change to a password
  without * and it works fine in all, graphic and terminal.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 15.10 and recently change my password it works ok,
  but after reboot my machine i can't login anymore using the graphic
  interface, but when i enter the command line mode i can login
  normally. I make sure that the problem was the password changed
  instaling ubuntu in a virtual machine and trying the same thing, i
  realize that when i use the * character in my password this error
  occurs. Once occurred the first time i try to change the password and
  login again in graphic mode but it doesn't work, only reinstalling the
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 18 15:21:05 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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/1517569/+subscriptions

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

[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1493804] Re: incorrect apparmor settings for lightdm-guest-session

[Robert Ancell]

Are these causing any issues?

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

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

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

Title:
  incorrect apparmor settings for lightdm-guest-session

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when using a guest session with xubuntu 15.10 beta1, I get several
  apparmor alerts (see attached file).

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep  9 13:00:38 2015
  InstallationDate: Installed on 2015-08-28 (12 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  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/1493804/+subscriptions

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

[Touch-packages] [Bug 1475771] Re: lightdm gives corrupted background image on login

[Robert Ancell]

It's either something in XFCE going wrong or a video driver issue.

** Package changed: lightdm (Ubuntu) => xfce4-session (Ubuntu)

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

Title:
  lightdm gives corrupted background image on login

Status in xfce4-session package in Ubuntu:
  New

Bug description:
  My desktop background is set up so that I have a .png file on top of a
  gradient background. The colors of the gradient background are the
  same, so that I have a solid color background.

  On login, instead of showing the image on the background, it showed
  the image fit to the screen with a black-and-white pattern behind it.

  I'm running Xubuntu 14.04, with lightdm version 1.10.5-0ubuntu1.1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Fri Jul 17 12:53:17 2015
  InstallationDate: Installed on 2015-06-19 (28 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1482684] Re: No keyboard / Mouse 50% of lightdm starts

[Robert Ancell]

Sounds like a video driver issue.

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  No keyboard / Mouse 50% of lightdm starts

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is most prevalent when resuming from suspend, however it does
  occur on a few cold boot scenarios.

  When lightdm comes up, I see the mouse cursor, it disappears and then
  I cannot move the mouse. The system, however, is still responsive, I
  can press the power button to see the Unity shutdown menu and the
  mouse cursor on the default user session still animates.

  I however cannot tty down and cannot do anything other than force
  shutdown. Attached are the contents of lightdm.log.old on the next
  boot.

  This hasn't occured for me on 14.04.1 nor Freya. It started happening
  when I installed 15.04 and then 14.04.3 so I believe it's related to
  the 3.19 hardware stack or lightdm 1.10.5.

  I have a mostly intel system, a Lenovo u410. I'd prefer to fix the
  issue rather than avoid it since I cannot download 14.04.1 anymore.

  
  During the expected behavior, lightdm boots, the mouse dissappears and then 
reappears (why it's mounting and unmounting when plymouth closes is beyond me). 
And I should be able to use my mouse/kb when resuming or cold booting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  7 10:21:52 2015
  InstallationDate: Installed on 2015-08-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1520933] Re: Lightdm should show login on active monitor

[Robert Ancell]

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

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

Title:
  Lightdm should show login on active monitor

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  I have a laptop with a small screen, and a large monitor that I use
  while at home. If I plug in the monitor from boot and close the laptop
  lid, I'll see the entire boot process on the large monitor; however,
  when lightdm fires up, it displays the login widgetry on the (closed)
  laptop monitor.

  It should be enhanced to detect that the primary monitor is not
  active, and display on the secondary monitor if this is the case.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 29 08:57:59 2015
  InstallationDate: Installed on 2014-07-11 (505 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to wily on 2015-11-28 (0 days ago)

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

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

[Touch-packages] [Bug 1528860] Re: Screen freezes after 10 seconds. Mouse and keyboard not responding.

[Robert Ancell]

Sounds like a video driver issue.

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Screen freezes after 10 seconds. Mouse and keyboard not responding.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi, I've experienced this bug randomly after rebooting my computer in
  Xubuntu 15.10.  This error is consistent even after multiple "disk
  format and reinstalls" of the operative system.

  PROBLEM: When i see the login screen, my mouse and keyboard turn off,
  and the cursos blinks in the password box for some seconds, and then
  it freezes.

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

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

[Touch-packages] [Bug 1550504] Re: lightdm unresponsive after suspend

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  lightdm unresponsive after suspend

Status in unity package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1565102] Re: The AlwaysShared option for lightdm does not work.

[Robert Ancell]

Can you explain the steps you did and how you confirmed it wasn't
working?

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

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

Title:
  The AlwaysShared option for lightdm does not work.

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Setup lightdm on Ubuntu 16.04 s390x beta2.  Successfully updated
  software.  Changed lightdm.conf to use the AlwaysShared option so that
  I could share a VNC session.  This did not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.0-0ubuntu2 [modified: 
lib/systemd/system/lightdm.service]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic s390x
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: s390x
  Date: Fri Apr  1 17:19:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2016-03-31T11:20:02.696961
  mtime.conffile..etc.pam.d.lightdm.greeter: 2016-03-31T11:47:26.478007

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

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

[Touch-packages] [Bug 1523922] Re: cursor disappears frequently

[Robert Ancell]

LightDM doesn't control the cursor. It's either the X server or Unity.

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  cursor disappears frequently

Status in Unity:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  A few times a week, my cursor just disappears.

  It is still there, reacting to mouse events, I can see hover events,
  clicking works too. But the cursor image just disappears which makes
  it unusable.

  Rebooting is the only solution. Restarting unity doesn't recover it.

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

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

[Touch-packages] [Bug 1529910] Re: can't log whit my password on account

[Robert Ancell]

Attach the contents of /var/log/lightdm/lightdm.log after this occurs.

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

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

Title:
  can't log whit my password on account

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  when i try to log in on my acc whit my password i can't do it, i just
  get back to log in page and i need to type password again.. nothing
  seems to help..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 29 18:02:16 2015
  InstallationDate: Installed on 2015-02-12 (320 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1529910/+subscriptions

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

[Touch-packages] [Bug 1525633] Re: passage du clavier Azerty en qwerty à chaque démarrage

[Robert Ancell]

What version of Ubuntu?

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

** Changed in: unity-greeter (Ubuntu)
   Status: New => Incomplete

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

Title:
  passage du clavier Azerty en qwerty à chaque démarrage

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  depuis une mise à jour récente, le clavier AZERTY passe en QWERTY à
  chaque démarrage.

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

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

[Touch-packages] [Bug 1551260] Re: after some work in fluxbox default fail to start

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => fluxbox (Ubuntu)

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

Title:
  after some work in fluxbox default fail to start

Status in fluxbox package in Ubuntu:
  New

Bug description:
  ubuntu start in fluxbox (has problems with images path) after
  erinstalling it. Now the default ubuntu show two errors to report then
  some command lines and return to login screen. System: Ubuntu 14.04
  updated

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-62.82~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb 29 16:30:45 2016
  InstallationDate: Installed on 2015-05-03 (301 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1548534] Re: 1.16.7 installation fails with 'failed to preconfigure with exit status 30'

[Robert Ancell]

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

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

Title:
  1.16.7 installation fails with 'failed to preconfigure with exit
  status 30'

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu Wily and lightdm has been failing to install for the
  past couple weeks. I've tried everything from removing the package and
  doing a clean install to reverting to an older version, but it always
  fails with the same error.  Here's the error that I  get when running
  the install:

  --
  Preconfiguring packages ...
  lightdm failed to preconfigure, with exit status 30
  Selecting previously unselected package lightdm.
  .
  .
  .
  .
  Setting up lightdm (1.16.7-0ubuntu1) ...
  dpkg: error processing package lightdm (--configure): 
subprocess installed post-installation script returned error exit status 30
  --

  With the last reboot, I can no longer load the desktop.

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

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

[Touch-packages] [Bug 1553074] Re: unity-greeter disappears after 10 seconds following boot

[Robert Ancell]

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

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

Title:
  unity-greeter disappears after 10 seconds following boot

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  When booting, the unit-greeter will appear as I expect it to, but
  after approximately 10 seconds the greeter wallpaper and the login
  prompt disappear.  I can still see the mouse pointer (and can move it)
  but nothing else is visible.

  I've learned that I can still login to the system by typing my
  password in blind, however; this is less than optimal as if an errant
  click of the mouse is made the focus will be taken off of the password
  field.  This means that I cannot login without a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Mar  4 02:16:02 2016
  InstallationDate: Installed on 2015-11-05 (120 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to wily on 2015-11-09 (115 days ago)

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

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

[Touch-packages] [Bug 1550683] Re: pwd accesso

[Robert Ancell]

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

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

Title:
  pwd accesso

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  accesso al pc avviene senza richiedere password

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-80.124-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-80-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Feb 27 09:57:06 2016
  DistUpgraded: 2014-04-21 00:43:01,510 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-75-generic, i686: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, i686: installed
   virtualbox, 4.3.36, 3.13.0-78-generic, i686: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, i686: installed
   virtualbox, 4.3.36, 3.13.0-80-generic, i686: installed
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff10]
 Subsystem: Toshiba America Info Systems Device [1179:ff10]
  InstallationDate: Installed on 2012-09-29 (1245 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: TOSHIBA Satellite A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-80-generic 
root=UUID=320d6461-fc7c-4f78-87fa-ab7dc3e18f9d ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (677 days ago)
  dmi.bios.date: 05/11/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.70
  dmi.board.name: MPAD-MSAE Customer Reference Boards
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.70:bd05/11/2006:svnTOSHIBA:pnSatelliteA100:pvrPSAA8E-07702PIT:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Satellite A100
  dmi.product.version: PSAA8E-07702PIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 27 09:08:35 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   0 
   vendor LPL
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1538772] Re: Stop build-depending on libfarstream-0.1-dev and gstreamer 0.10

[Bryan Quigley]

This is the last fix keeping src:gst-plugins-good0.10 in archive.

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

Title:
  Stop build-depending on libfarstream-0.1-dev and gstreamer 0.10

Status in telepathy-qt package in Ubuntu:
  New
Status in telepathy-qt5 package in Ubuntu:
  Confirmed

Bug description:
  This is the old gst0.10 farstream, you don't want this anymore.

  This is keeping the following source packages unnessarily in main (and maybe 
existing):
  gstreamer0.10-nice

  This holds the obsolete farstream source in Ubuntu, which got removed
  in Debian (#802204).

  Bug in xenial.

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

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

[Touch-packages] [Bug 1558287] Re: Stop depending on gstreamer0.10-pulseaudio and gstreamer0.10-plugins-good

[Bryan Quigley]

This fix has landed.

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

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

Title:
  Stop depending on gstreamer0.10-pulseaudio and gstreamer0.10-plugins-
  good

Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released

Bug description:
  Gstreamer0.10 is being removed from the archive.

  Ubuntu-touch still depends on gstreamer0.10-pulseaudio and
  gstreamer0.10-plugins-good even though that's no longer necessary
  (with the switch to Qt5.5.).

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

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

[Touch-packages] [Bug 1470980] Re: lightdm does not start in kvm with qxl graphics

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  lightdm does not start in kvm with qxl graphics

Status in xorg-server package in Ubuntu:
  New

Bug description:
  To do install a lubuntu installation in a kvm vm with qxl graphics.
  Then lightdm will not start after restarting the installation. Lightdm
  will not start.

  lightdm:
Installed: 1.15.0-0ubuntu1
Candidate: 1.15.0-0ubuntu1
Version table:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  I expected lightdm to start to a graphcial login screen. Instead
  lightdm did not start with qxl graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.15.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  Date: Thu Jul  2 11:50:17 2015
  InstallationDate: Installed on 2015-07-02 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150702)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1446720] Re: Cannot login on live CD

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  Cannot login on live CD

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  I downloaded 15.04 Vivid daily build 16/04/2015, and on login screen I
  can't login using "ubuntu" as username and blank password, as on
  previous Ubuntu releases. This implies I can't use Vivid live, I can
  install only.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 21 17:13:13 2015
  InstallationDate: Installed on 2015-04-17 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150416)
  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/1446720/+subscriptions

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

[Touch-packages] [Bug 1471948] Re: package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[Robert Ancell]

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

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

Title:
  package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  just booted and logged me in, then tryed to install the updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: liblightdm-gobject-1-0 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.11
  AptOrdering:
   p7zip-full: Install
   liblightdm-gobject-1-0: Configure
   p7zip-full: Configure
  Architecture: amd64
  Date: Mon Jul  6 20:59:10 2015
  DuplicateSignature: package:liblightdm-gobject-1-0:1.10.5-0ubuntu1.1:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2011-08-13 (1423 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  SourcePackage: lightdm
  Title: package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (437 days ago)

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

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

[Touch-packages] [Bug 1221815] Re: saucy mir ppa black screen on notebook Radeon HD 6310

[Daniel van Vugt]

That would be Xmir 1.0 which we no longer develop or support.

Also, Canonical no longer supports Ubuntu 13.10 in general:
   https://wiki.ubuntu.com/Releases

So please upgrade. Although admittedly this bug has been silent for 2.5
years. Just tidying up...

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  saucy mir ppa black screen on notebook Radeon HD 6310

Status in unity-system-compositor package in Ubuntu:
  Won't Fix

Bug description:
  Boots to black screen.  Ctrl-Alt-F1 no response.  Have to power off.
  Boot in recovery mode xrandr says;

  jerry@Aspire-5253:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x7680.0* 
 800x60061.0 

  Runs fine in saucy without mir PPA

  Looks like saucy - mir - compositor cannot recognize the normal laptop
  built-in display at 1366x768.

  Attached is tar.gz of 
  lightdm.log  unity-system-compositor.log  x-0.log
  lightdm.log.old  unity-system-compositor.log.old  x-0.log.old

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.12-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Fri Sep  6 11:46:05 2013
  InstallationDate: Installed on 2013-08-31 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=jerry
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[JianFeng Liu]

why not just dlopen libGL.so.1
I've mailed to the packager of nvidia driver in debian and got the answer: 
"pyqt should dlopen libGL.so.1".

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
&PositionOnlyVertexShader) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

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

[Touch-packages] [Bug 1447306] Re: Window sections shown as black boxes

[Robert Ancell]

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

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

Title:
  Window sections shown as black boxes

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Sections of certain windows will be incorrectly rendered as black when
  they should be rendered as the default color according to the selected
  theme.

  Although I'm not 100% certain, I've tagged this as a lightdm bug
  because I tested various configurations of nouvea/nvidia and unity
  /gnome-shell and found this happened in all configurations.

  To clarify, I tested this in the following configurations:

  nouveau + unity
  nouveau + gnome-shell
  nvidia-340 + unity
  nvidia-340 + gnome-shell

  and found this happened in several windows, notable gedit and gnome-
  tweak-tool (only gnome-shell). In general, it seemed to occur in the
  sections of the window that are otherwise empty and not populated by
  widgets.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 22 14:38:19 2015
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2015-04-19 (2 days ago)

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

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

[Touch-packages] [Bug 1451704] Re: upgradeing to ubuntu 15.05

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  upgradeing to ubuntu 15.05

Status in lightdm package in Ubuntu:
  Fix Released
Status in lim package in Ubuntu:
  New

Bug description:
  It installs fine but when you restart the computer  ubuntu does not
  come back  it just stays  a black screen  and I left it over night
  and it was still in the black screen  so i had to reinstall 12.04 ver
  again  and upgrade  up to 14.10 for the threed time  im not upgradeing
  to 15.04 until i know it works  like 14.10 ver  softwere  .

  
   i want to be at the current ver  but it keeps crashing my computer 

  im staying at 14.10 version  thanks  any q's  
  Please e-mail me at  nitro9...@gmail.com

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

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

[Touch-packages] [Bug 1462723] Re: lightdm quits at startup when beamer is connected

[Robert Ancell]

What is a beamer?

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

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

Title:
  lightdm quits at startup when beamer is connected

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I have a beamer. Since installation of kubuntu-15.04 I can't log into
  my account if the beamer is connected. The kubuntu splash screen show
  up alright, but takes a bit longer to complete, then I am dropped into
  a black screen with a (movable) mouse pointer.

  If I disconnect the beamer during startup, I can login.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jun  7 10:15:33 2015
  InstallationDate: Installed on 2015-03-16 (82 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (42 days ago)

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

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

[Touch-packages] [Bug 1458865] Re: No Graphics on IGEL m300

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  No Graphics on IGEL m300

Status in xorg-server package in Ubuntu:
  New

Bug description:
  i cant start X on the IGEL m300. Installed LUBUNTU since the igel is
  not very vast.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  Date: Tue May 26 14:41:48 2015
  LightdmGreeterLog:
   Activating service name='org.a11y.atspi.Registry'
   Successfully activated service 'org.a11y.atspi.Registry'
   
   ** (lightdm-gtk-greeter:1515): WARNING **: Failed to load user image: Failed 
to open file '/home/jaap/.face': Bestand of map bestaat niet
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-05-26 (0 days ago)

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

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

[Touch-packages] [Bug 1463224] Re: /usr/bin/X segfaults on startup

[Robert Ancell]

** No longer affects: lightdm (Ubuntu)

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

Title:
  /usr/bin/X segfaults on startup

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm seeing this both with Ubuntu 15.04 and Ubuntu 15.10.

  When I boot into Ubuntu, I get a screen saying that 'The system is
  running in low-graphics mode'. When I look at the `xserver` log files,
  I see that it's actually segfaulted (and so I get no GUI -- e.g.
  'lightdm' fails to start)

  Backtrace:

  [77.069] (EE) Backtrace:
  [77.069] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7fa8f86e9346]
  [77.069] (EE) 1: /usr/bin/X (0x7fa8f8536000+0x1b74a9) [0x7fa8f86ed4a9]
  [77.069] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fa8f61fb000+0x352f0) 
[0x7fa8f62302f0]
  [77.069] (EE) 3: /usr/bin/X (RRSetChanged+0x50) [0x7fa8f864d4a0]
  [77.069] (EE) 4: /usr/bin/X (RRScreenSetSizeRange+0x54) [0x7fa8f86519d4]
  [77.069] (EE) 5: /usr/bin/X (xf86RandR12CreateScreenResources+0x2a5) 
[0x7fa8f860e965]
  [77.069] (EE) 6: /usr/bin/X (0x7fa8f8536000+0xcbc00) [0x7fa8f8601c00]
  [77.069] (EE) 7: /usr/bin/X (0x7fa8f8536000+0x5c094) [0x7fa8f8592094]
  [77.069] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7fa8f621ba40]
  [77.069] (EE) 9: /usr/bin/X (_start+0x29) [0x7fa8f857c5b9]
  [77.069] (EE) 
  [77.069] (EE) Segmentation fault at address 0xa0

  And the log in its entirety:

  [76.727] 
  X.Org X Server 1.17.1
  Release Date: 2015-02-10
  [76.727] X Protocol Version 11, Revision 0
  [76.727] Build Operating System: Linux 3.2.0-79-generic x86_64 Ubuntu
  [76.727] Current Operating System: Linux kevin-Z68X-UD3H-B3 
3.16.0-38-generic #52-Ubuntu SMP Thu May 7 10:51:21 UTC 2015 x86_64
  [76.727] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=7cb7429e-756d-4b07-b226-ef75f21de60c ro quiet splash vt.handoff=7
  [76.727] Build Date: 03 June 2015  04:44:17AM
  [76.727] xorg-server 2:1.17.1-0ubuntu4 (For technical support please see 
http://www.ubuntu.com/support) 
  [76.727] Current version of pixman: 0.32.6
  [76.727]  Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  [76.727] Markers: (--) probed, (**) from config file, (==) default 
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [76.727] (==) Log file: "/var/log/Xorg.1.log", Time: Mon Jun  8 17:53:37 
2015
  [76.727] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [76.727] (==) No Layout section.  Using the first Screen section.
  [76.727] (==) No screen section available. Using defaults.
  [76.727] (**) |-->Screen "Default Screen Section" (0)
  [76.727] (**) |   |-->Monitor ""
  [76.727] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
  [76.727] (==) Automatically adding devices
  [76.727] (==) Automatically enabling devices
  [76.728] (==) Automatically adding GPU devices
  [76.728] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [76.728]  Entry deleted from font path.
  [76.728] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [76.728]  Entry deleted from font path.
  [76.728] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [76.728]  Entry deleted from font path.
  [76.728] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [76.728]  Entry deleted from font path.
  [76.728] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [76.728]  Entry deleted from font path.
  [76.728] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
  [76.728] (==) ModulePath set to 
"/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
  [76.728] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
  [76.728] (II) Loader magic: 0x7fa8f8970d80
  [76.728] (II) Module ABI versions:
  [76.728]  X.Org ANSI C Emulation: 0.4
  [76.728]  X.Org Video Driver: 19.0
  [76.728]  X.Org XInput driver : 21.0
  [76.728]  X.Org Server Extension : 9.0
  [76.728] (II) xfree86: Adding drm device (/dev/dri/card0)
  [76.730] (--) PCI: (0:0:2:0) 8086:0162:1458:d000 rev 9, Mem @ 
0xfb40/4194304, 0xc000/268435456, I/O @ 0xff00/64
  [76.730] (--) PCI:*(0:1:0:0) 10de:1401:3842:3966 rev 161, Mem @ 
0xf900/16777216, 0xd000/268435456, 0xee00/33554432, I/O @ 
0xcf00/128, BIOS @ 0x??

[Touch-packages] [Bug 1467100] Re: package liblightdm-qt-3-0 1.10.5-0ubuntu1 failed to install/upgrade: package liblightdm-qt-3-0 is not ready for configuration cannot configure (current status `half-

[Robert Ancell]

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

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

Title:
  package liblightdm-qt-3-0 1.10.5-0ubuntu1 failed to install/upgrade:
  package liblightdm-qt-3-0 is not ready for configuration  cannot
  configure (current status `half-installed')

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Not getting connected with yureka through USB

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: liblightdm-qt-3-0 1.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  AptOrdering:
   libid3tag0: Install
   mtpfs: Install
   liblightdm-qt-3-0: Configure
   libid3tag0: Configure
   mtpfs: Configure
  Architecture: i386
  Date: Sat Jun 20 18:00:58 2015
  DuplicateSignature: package:liblightdm-qt-3-0:1.10.5-0ubuntu1:package 
liblightdm-qt-3-0 is not ready for configuration  cannot configure (current 
status `half-installed')
  ErrorMessage: package liblightdm-qt-3-0 is not ready for configuration  
cannot configure (current status `half-installed')
  InstallationDate: Installed on 2015-04-13 (68 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: lightdm
  Title: package liblightdm-qt-3-0 1.10.5-0ubuntu1 failed to install/upgrade: 
package liblightdm-qt-3-0 is not ready for configuration  cannot configure 
(current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1556701] Re: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE

[Daniel van Vugt]

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

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

Title:
  ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This occurs on a WeTab tablet computer.

  The system configuration and browser apps won't run.  They display
  their small windows, then the windows disappear.

  The batter/sound/network/time & date/system pull-down menu won't stay
  open.  It closes within a second of pulling it down.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160301-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar 13 19:40:18 2016
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1557634] Re: Crashes when given an invalid keymap

[Daniel van Vugt]

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

** Summary changed:

- Crashes when given an invalid keymap
+ Mir crashes when given an invalid keymap

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

Title:
  Mir crashes when given an invalid keymap

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

Bug description:
  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
 from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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

[Touch-packages] [Bug 1565236] Re: Spanish keyboard layout wrong

[Daniel van Vugt]

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

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

Title:
  Spanish keyboard layout wrong

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Keyboard: http://www.logitech.com/en-hk/product/wireless-touch-
  keyboard-k400r2

  In Ubuntu 14.04 desktop
  (http://cdimage.ubuntu.com/releases/12.04/release/) the keyboard works
  perfect.

  In Phone: bq Aquaris E.4.5 Ubuntu Edition, Ubuntu release: 15.04
  (r305):

  With the default keyboard layout I can write many characters pressing
  the keys they are printed. The specific symbols like ? or - are in
  different keys than those they are printed. This is expected.

  If I choose 'Spanish' from 'Settings > Language and text > External
  keyboard' I can write almost all characters and specific symbols
  except those which you have to press ALT-GR key. The accented
  characters are impossible to obtain, i.e., I only can write Sabado
  instead of Sábado.

  I have compared /usr/share/i18n/charmaps/ES.gz in desktop and phone
  and they don't have differences.

  I hope this to help. Thanks.

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

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

[Touch-packages] [Bug 1476433] Re: invisible pointer on boot

[Robert Ancell]

** No longer affects: lightdm (Ubuntu)

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

Title:
  invisible pointer on boot

Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  Upon login to xfce, there is a pointer (as evidenced by right clicking
  with the touch pad) but it is invisible.  Plugging a mouse in makes
  the pointer visible again.

  xfce:  4.12.1
  ubuntu: wily werewolf

  [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev 
touchpad catchall"
  [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad 
catchall"
  [60.751] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default 
clickpad buttons"
  [60.751] (II) LoadModule: "synaptics"
  [60.751] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xfce4 4.12.1
  Uname: Linux 4.1.0-040100rc1-generic x86_64
  ApportVersion: 2.18-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul 20 20:02:19 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (376 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  PackageArchitecture: all
  SourcePackage: xfce4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1251348] Re: lightdm crashes on bootup or logout

[Robert Ancell]

Closing assumed fixed. Sounds like a video driver issue.

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

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

Title:
  lightdm crashes on bootup or logout

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Upon booting lightdm usually* crashes and to a blinking text courser on the 
top-left (no login gui).
Usually* - lightdm almost always crashes (at least 50-80%)
  If lightdm doesn’t crash on boot and you login, if you try logging out and 
user switching lightdm will crash to the text courser (seen at the top left). 
(However light does not crash on a lock screen)

  
  I suspect its lightdm becaouse when using gdm there are no issues, but when 
reverting to lightdm the issues reappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 14 12:04:49 2013
  InstallationDate: Installed on 2013-11-10 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  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/1251348/+subscriptions

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

[Touch-packages] [Bug 1285697] Re: can't type password

[Robert Ancell]

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

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

Title:
  can't type password

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  I just installed Trusty http://cdimage.ubuntu.com/daily-live/20140224
  Everything looks normal, the cursor blinks, but I can not type anything.

  Workaround: click on menu then click on the password input.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 16:29:31 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=emanuel
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1233773] Re: lighdm does not change accessibility when login in lubuntu

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu)

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

Title:
  lighdm does not change accessibility when login in lubuntu

Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  When choosing accessibility option in LightDM greeter, the greeter
  changes them. But after login, the effect is not present in the
  Lubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  1 19:11:15 2013
  InstallationDate: Installed on 2013-09-29 (1 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130929)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  MarkForUpload: True
  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-gtk-greeter/+bug/1233773/+subscriptions

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

[Touch-packages] [Bug 1244985] Re: LightDM sets wrong keyboard settings for a session

[Robert Ancell]

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

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

Title:
  LightDM sets wrong keyboard settings for a session

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Suddenly my session is starting with the wrong keyboard. I have a
  Spanish keyboard, and in some session I get the English keyboard.

  Opening the keyboard system settings, and unchoosing and choosing back
  the Spanish keyboard gets me back to the correct configuration of the
  keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct 26 17:02:56 2013
  InstallationDate: Installed on 2012-05-31 (513 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to saucy on 2013-09-06 (50 days ago)

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

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

[Touch-packages] [Bug 1287633] Re: login password entry problem

[Robert Ancell]

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

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

Title:
  login password entry problem

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  When I boot my laptop I reach the login screen of ubuntu 14.04.

  I have 3 login id's
  one of which is guest account.
  when I try to type the password in my regular login account the password 
field does not accept the entry. Then I chenge my language / keyboard settings 
in top right corner of the screen from english with rupee sign to english uk 
and back again to english with rupee sign it allows me to type the password in 
my password field. my password is all caps so i keep the caps lock on.
  i tried with caps lock on and off both but it allows only after tweaking the 
keybord settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: login 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar  4 15:30:36 2014
  InstallationDate: Installed on 2012-03-24 (709 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to trusty on 2014-01-30 (33 days ago)

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

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

[Touch-packages] [Bug 1291278] Re: Lightdm should wait until network is ready or time out

[Robert Ancell]

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

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

** Summary changed:

- Lightdm should wait until network is ready or time out
+ Wait until network is ready for remote authentication

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

Title:
  Wait until network is ready for remote authentication

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Hi,

  refer to this Bug #1039151 to see the background.

  Lightdm should wait until we have Networking ready. If no network is 
available it should start immediately. This is necessary for all non local 
authentication methods like sssd etc. 
  If lightdm starts to early it may lead to failed login attempts until network 
is ready and for example M$-AD Server is available.

  These are the scripts i used to prevent lightdm from starting to
  early:

  Here are the skripts:

  /etc/init/networkdelay.conf :

  description "wait for IP to be there"

  #emits networkdelay

  start on (net-device-up IFACE!=lo
  and local-filesystems)

  #start on (((starting lightdm or starting kdm) or starting xdm) or starting 
lxdm)
  start on (starting lightdm
  or starting kdm
  or starting xdm
  or starting lxdm)

  task

  script
  exec /usr/sbin/network-ok
  end script


  
  /usr/sbin/network-ok:

  #!/bin/sh
  LOG=/tmp/network-diag
  rm $LOG
  #LOG=/dev/null
  #touch $LOG
  MAXWAIT=60
  T0=`cut -f1 -d. /proc/uptime`

  while (( test $(($T0+$MAXWAIT)) -gt $(cut -f1 -d. /proc/uptime) ))
  do
   date >> $LOG
   pidof lightdm >> $LOG
   #GW=`ip ro list default |head -1 |cut -d " " -f 3`
   GW=`ip -4 ro list 0.0.0.0/0 | cut -d " " -f 3`
  # ethtool eth0 >> $LOG
   test -n "$GW" && ping -c1 -w1 $GW >> $LOG 2>&1 && break
   sleep 1
  done

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

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

[Touch-packages] [Bug 1295837] Re: keyboard doesnt work after hibernation lockscreen

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  keyboard doesnt work after hibernation lockscreen

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  when i open the lid to my laptop the keybaord doesnt work in the
  lockscreen unless i go up to the power cog and go to switch account
  then i can log back in just fine it only happens when my laptop lid
  has been shut for more then 5 mins... This is for ubuntu 14.04

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

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

[Touch-packages] [Bug 1221815] Re: saucy mir ppa black screen on notebook Radeon HD 6310

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity-system-compositor (Ubuntu)

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

Title:
  saucy mir ppa black screen on notebook Radeon HD 6310

Status in unity-system-compositor package in Ubuntu:
  Won't Fix

Bug description:
  Boots to black screen.  Ctrl-Alt-F1 no response.  Have to power off.
  Boot in recovery mode xrandr says;

  jerry@Aspire-5253:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x7680.0* 
 800x60061.0 

  Runs fine in saucy without mir PPA

  Looks like saucy - mir - compositor cannot recognize the normal laptop
  built-in display at 1366x768.

  Attached is tar.gz of 
  lightdm.log  unity-system-compositor.log  x-0.log
  lightdm.log.old  unity-system-compositor.log.old  x-0.log.old

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.12-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Fri Sep  6 11:46:05 2013
  InstallationDate: Installed on 2013-08-31 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=jerry
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1185567] Re: Changing an expired password in lightdm does not change gnome-keyring password

[Robert Ancell]

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

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

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

Title:
  Changing an expired password in lightdm does not change gnome-keyring
  password

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  pam_sss is configured to authenticate against Active Directory via Kerberos. 
pam.d/common-password has been configured such that manual "passwd" invocations 
change pam_sss, then go on to pam_gnomekeyring and a pam_script to change any 
lingering passwords manually.
  When lightdm detects an expired password and goes through the password change 
process, pam_gnomekeyring is not able to start gnome-keyring-daemon to change 
the keyring password.
  pam_sss does not have a defer_pwchange option, which appears to be the 
workaround for bug #972537.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: lightdm 1.6.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed May 29 19:31:08 2013
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1185567/+subscriptions

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

[Touch-packages] [Bug 1213596] Re: lightdm should warn when filesystems are read-only since then login is impossible

[Robert Ancell]

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

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

** Summary changed:

- lightdm should warn when filesystems are read-only since then login is 
impossible
+ Warn when filesystems are read-only since then login is impossible

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

Title:
  Warn when filesystems are read-only since then login is impossible

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Today I was greeted by a text console after logging in to lightdm
  (Ubuntu standard Unity desktop). No error messages, no nothing (at
  least on screen).

  Since I know my way around Linux I dropped to a console and found that
  my root fs had been mounted read-only due to an IO error on the
  harddisk. A novice user would have no idea what to do.

  Displaying a warning message saying something like "Your harddisk has
  been mounted in read-only mode. It might be faulty or there is another
  system defect which prevented a normal startup procedure. Please
  reboot, press SHIFT while the computer restarts and choose "Rescue
  mode" at the boot manager prompt. In the rescue mode menu, try
  checking for harddisk errors and checking your installed software
  package database." would help a novice user a lot.

  This should be fairly easy to implement. If it is not possible to
  display notifications before login in lightdm, just change the
  background image to something which contains this error message in,
  say, English, German, French, Spanish, and Chinese. This is e.g. what
  Mac OS X does.

  This might apply also to later distributions (I haven't checked).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.3
  ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
  Uname: Linux 3.5.0-37-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Sun Aug 18 10:57:19 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130214)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1213596/+subscriptions

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

[Touch-packages] [Bug 1217378] Re: Lightdm does not recognize 3D acceleration with ati radeon driver (Low graphics mode error)

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Lightdm does not recognize 3D acceleration with ati radeon driver (Low
  graphics mode error)

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all.

  I'm experiencing a problem in Ubuntu 12.04.3 LTS.

  I have an ATI Radeon 9100 (r200), which supports 3D acceleration as
  you can verify by

  $ glxinfo | grep direct
  direct rendering: Yes

  and is using the xserver-xorg-video-ati / xserver-xorg-video-radeon
  driver.

  Anyway, after some upgrades time ago, lightdm started to not recognize 
graphics capability: when I power up the pc, I got a "The system is running in 
low graphics mode" error.
  I tried to reconfigure the package and many other solutions I've seen around 
the internet, but I couldn't solve it.

  The only workaround, which also justifies why I selected "lightdm"
  package and not "xserver-xorg-video-ati" package, was to switch logon
  screen from lightdm to gdm: GDM correctly recognizes the 3D ability
  and gives no error.

  
  Steps to reproduce the bug:
  1- Install an ATI Radeon 9100 card
  2- Install Ubuntu 32bit 12.04.3 LTS (lightdm v.1.2.3-ubuntu2.3, 
xserver-xorg-video-radeon v1:6-14.99~git20111219.aacbd629-0ubuntu2)
  3- Start the computer.

  I may suggest, though I'm not so sure, it could be a regression?
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  ati/+bug/495973

  Thanks in advance,
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.3
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Tue Aug 27 14:07:12 2013
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1181983] Re: Update to 1.2.3-0ubuntu2.1: Broken / Greeter won't start

[Robert Ancell]

Closing assumed fixed.

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

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

Title:
  Update to 1.2.3-0ubuntu2.1: Broken / Greeter won't start

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I'm running Ubuntu 12.04.2 with Gnome Classic / Gnome Panel and
  LightDM + Unity Greeter on AMD64.

  The recent update of LightDM from 1.2.3-0ubuntu2 to 1.2.3-0ubuntu2.1
  left me with a command line login prompt after boot. It turned out
  that LightDM will start neither Unity-Greeter nor LightDM-Gtk-Greeter.
  I still can manually start X and then Gnome-Panel but the desktop
  behaviour is not without errors.

  I had to remove both lightdm_1.2.3-0ubuntu2.1 and liblightdm-
  gobject-1-0_1.2.3-0ubuntu2.1 and replace the packages by the previous
  versions (2 instead of 2.1), which restored full login and desktop
  funtionality.


  Any suggestions?!

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

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

[Touch-packages] [Bug 1170971] Re: Start laptop and login screen doesn't appear

[Robert Ancell]

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

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

Title:
  Start laptop and login screen doesn't appear

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  This seems to occur randomly. Upon Restarting or starting my laptop
  when it reaches the point of logging in (or when the sound of the boot
  finishing with the drums occurs) I will sometimes be greeted with a
  blank black screen with my cursor also present. I can then pres ctrl +
  alt + F1 stop lightdm and then start it once again and then procede to
  log in and use the laptop as I normally would.

  Release final beta of 13.04 (NOT a daily release)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: lightdm 1.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat Apr 20 12:16:47 2013
  InstallationDate: Installed on 2013-04-20 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1170971/+subscriptions

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