[Desktop-packages] [Bug 1406825] Re: xscreensaver complains "This version of xscreensaver is VERY OLD!"

2016-04-05 Thread Bug Watch Updater
** Changed in: xscreensaver (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xscreensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1406825

Title:
  xscreensaver complains "This version of xscreensaver is VERY OLD!"

Status in One Hundred Papercuts:
  Invalid
Status in xscreensaver package in Ubuntu:
  Fix Released
Status in xscreensaver package in Debian:
  Fix Released

Bug description:
  Early minutes of year 2015 and the xscreensaver complains that "This
  version of xscreensaver is VERY OLD!" in this dialog:
  http://i.imgur.com/VUCQfun.png?1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xscreensaver 5.26-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-28.38-lowlatency 3.16.7-ckt1
  Uname: Linux 3.16.0-28-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan  1 00:44:38 2015
  InstallationDate: Installed on 2011-11-13 (1144 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xscreensaver
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (67 days ago)

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

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


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

2016-04-05 Thread 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 Desktop
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
  [+0.01s] 

[Desktop-packages] [Bug 1374842] Re: Impossible to use 2x DisplayPort (Dualmonitor) with HP EliteBook 840 G1 on HP 2013 UltraSlim Docking Station

2016-04-05 Thread Luke T
The issue didn't occur anymore. It was fixed by a new Ubuntu version, I
think it was 14.10.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1374842

Title:
  Impossible to use 2x DisplayPort (Dualmonitor) with HP EliteBook 840
  G1 on HP 2013 UltraSlim Docking Station

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have a HP EliteBook 840 G1 laptop that I use in combination with a
  HP 2013 UltraSlim Docking Station (REV V1.00). I cannot use both
  DisplayPort connectors of the docking station to enable a dual-monitor
  setup. If I try to do so, I get a mirrored image instead. The
  "Displays" tool shows the built-in display and only one of my monitors
  (at home, where I'm writing this, I have the same monitor (Asus
  PB278Q) twice). In my office I tested with different monitors and only
  one of them showed up.

  I tried my installed system
  - Ubuntu Desktop 14.04.1 with Gnome Flashback (Metacity), 64 bit
  and several live systems
  - Ubuntu Desktop 14.10 Beta 2, 64 bit
  - Linux Mint Debian Edition 201403 Cinnamon DVD, 32 bit
  - openSUSE 13.2 Beta1 Live KDE, Build 0011, 64 bit
  with the same results.

  I know that the setup should work since the machine is dual-boot and
  works with Windows 7.

  I updated both BIOS (to version 1.20 (2014-07-28) and docking station
  (to version 2.18.000 (2014-03-07)) with no change to the issue.

  The following workarounds work:
  - Imitating a single monitor with a resolution of (3840x1080) This maybe only 
work because the monitors are of the same type.
  - Attaching one of the monitors to VGA instead of the DisplayPort (reducing 
the usable resolution to 1920x1080)

  Attaching one of the monitors to the laptop's DisplayPort connector
  leaves the screen blank.

  I'm willing to give more info or test things but I am not sure on what
  to add.

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

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


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

2016-04-05 Thread Benoit Barthelet
It isn't.

benoit barthelet
http://pgp.mit.edu/pks/lookup?op=get=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:
> 

[Desktop-packages] [Bug 1566437] Re: Scrolling randomly stops working

2016-04-05 Thread Egmont Koblinger
The behavior you describe happens when the terminal switches to the so-
called "alternate screen" upon encountering a certain escape sequence
that is printed by your application. Usually fullscreen applications
(such as the "mc" file manager, "less" pager, text editors etc.) use
this mode.

If it gets stuck in this mode at your shell prompt, it means that your
application did not exit cleanly and left the terminal in this mode.
Execute the "reset" command to get out of this situation.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1566437

Title:
  Scrolling randomly stops working

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Usually, scrolling in the terminal window works as expected, which is like 
this:
  - the terminal window has a scrollbar
  - Assuming there are more lines (of commands you have typed + their output) 
than fit in the window, you can scroll up and down both by dragging the 
scrollbar and by using the mouse wheel

  
  However, at random times, the Terminal starts behaving like this:
  1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the 
existing lines didn't exceed the height of the window, even if that is not the 
case
  2 - you can't scroll by dragging the scrollbar (which is consistent with 1)
  3 - the scrollwheel behaves like the up and down arrow keys, that is, it 
scans through previously typed commands in your history.

  
  I have no idea what triggers the nonsense behavior. It seems to start 
happening randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 19:05:18 2016
  InstallationDate: Installed on 2013-10-11 (906 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago)

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

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


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

2016-04-05 Thread Robert Ancell
Is this still occurring?

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Still occurring?

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => konsole (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assuming fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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 

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

2016-04-05 Thread Robert Ancell
See https://wiki.ubuntu.com/MultiseatTeam/Instructions

-- 
You received this bug notification because you are a member of Desktop
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 1
  

[Desktop-packages] [Bug 1546823] Re: swig: disable PHP bindings until PHP7 support exists

2016-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package libkolabxml - 1.1.2-0ubuntu3

---
libkolabxml (1.1.2-0ubuntu3) xenial; urgency=medium

  * Disable php-kolabformat while swig does not support PHP7.0 (LP: #1546823).
- http://lists.kolab.org/pipermail/users/2015-December/020357.html

 -- Nishanth Aravamudan   Tue, 05 Apr
2016 10:02:53 -0700

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1546823

Title:
  swig: disable PHP bindings until PHP7 support exists

Status in exactimage package in Ubuntu:
  Fix Released
Status in gdcm package in Ubuntu:
  Fix Released
Status in geos package in Ubuntu:
  Fix Released
Status in graphviz package in Ubuntu:
  Fix Released
Status in libkolabxml package in Ubuntu:
  Fix Released
Status in mapserver package in Ubuntu:
  Fix Released
Status in owfs package in Ubuntu:
  Fix Released
Status in redland-bindings package in Ubuntu:
  Fix Released
Status in swig package in Ubuntu:
  Fix Released
Status in swig2.0 package in Ubuntu:
  Fix Released

Bug description:
  As a short-term solution, we need to disable swig's PHP bindings, as
  it does not currently support PHP7.0
  (https://github.com/swig/swig/issues/571).

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

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


[Desktop-packages] [Bug 1546823] Re: swig: disable PHP bindings until PHP7 support exists

2016-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package swig - 3.0.8-0ubuntu3

---
swig (3.0.8-0ubuntu3) xenial; urgency=medium

  * d/rules: remove build-dep on php5* while SWIG does not support
PHP7.0 (LP: #1546823).

 -- Nishanth Aravamudan   Tue, 05 Apr
2016 11:53:32 -0700

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1546823

Title:
  swig: disable PHP bindings until PHP7 support exists

Status in exactimage package in Ubuntu:
  Fix Released
Status in gdcm package in Ubuntu:
  Fix Released
Status in geos package in Ubuntu:
  Fix Released
Status in graphviz package in Ubuntu:
  Fix Released
Status in libkolabxml package in Ubuntu:
  Fix Released
Status in mapserver package in Ubuntu:
  Fix Released
Status in owfs package in Ubuntu:
  Fix Released
Status in redland-bindings package in Ubuntu:
  Fix Released
Status in swig package in Ubuntu:
  Fix Released
Status in swig2.0 package in Ubuntu:
  Fix Released

Bug description:
  As a short-term solution, we need to disable swig's PHP bindings, as
  it does not currently support PHP7.0
  (https://github.com/swig/swig/issues/571).

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

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


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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 id: 4
  

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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Also, a merge proposal is easier to handle than a diff.

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
is this still occurring?

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1133192] Re: Screen goes wonky when HDMI device is plugged in

2016-04-05 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1133192

Title:
  Screen goes wonky when HDMI device is plugged in

Status in xserver-xorg-video-ati package in Ubuntu:
  Expired

Bug description:
  On plugging in HDMI devices, the screen is scrambled.  Pretty simple.

  Boot and log in.
  Plug in HDMI device
  Watch the screen scramble

  This occurs with the Radeon driver.

  I managed to recover the system the first time by unplugging the
  device, however, on the second attempt, the screen scrambled and stuck
  that way and I had to reboot to recover the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-radeon-lts-quantal 
1:6.99.99~git20120913.8637f772-0ubuntu1~precise2
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Tue Feb 26 04:16:32 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-ati-lts-quantal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1133192/+subscriptions

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


[Desktop-packages] [Bug 1311484] Re: Intel Haswell Graphics controller[8086:0a16] Small blocks appear in Firefox randomly

2016-04-05 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1311484

Title:
  Intel Haswell Graphics controller[8086:0a16] Small blocks appear in
  Firefox randomly

Status in xserver-xorg-video-intel package in Ubuntu:
  Expired

Bug description:
  CID: 201307-13941 Dell Latitude E5440

  Some small black block will appear when you scroll up in Firefox.

  Steps:
  1. Install 12.04.4 + updates (3.11.0-19)
  2. Open https://docs.python.org/devguide/ in your Firefox with maximized 
window
  3. Scroll to the bottom of the webpage, and scroll up

  Expected result:
  * Display works fine

  Actuel result:
  * Small black boxes appear in the browser when you scrolling up, this does 
not only happen in this page. 
  But if you shrink the window size, it'll be hard to reproduce.
  Verified with LibreOffice Calc, cannot be reproduced in it.

  This might be an Intel driver related issue, see:
  https://support.mozilla.org/en-US/questions/958127
  https://bugs.freedesktop.org/show_bug.cgi?id=68410

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-19-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1676 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1676 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xf7434000 irq 64'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 21
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf743 irq 65'
 Mixer name : 'Realtek ALC292'
 Components : 'HDA:10ec0292,102805de,0011'
 Controls  : 28
 Simple ctrls  : 13
  Date: Wed Apr 23 02:32:24 2014
  HibernationDevice: RESUME=UUID=1cfd99fb-54b6-4cc8-a24a-8db63ee87d24
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Latitude E5440
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic 
root=UUID=823ebc42-ec31-482a-ac2f-5d02316430ae ro quiet splash initcall_debug
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware 1.79.11
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 01348G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd09/18/2013:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn01348G:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1311484/+subscriptions

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


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

2016-04-05 Thread 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 Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => fluxbox (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 18280] Re: Firefox crashes when setting desktop wallpaper from image

2016-04-05 Thread Biswajit Mandal
Please ignore the #7 commit for this bug, the commit was for bug
https://bugs.launchpad.net/juniperopenstack/+bug/1563929

** Changed in: juniperopenstack/r2.20
Milestone: r2.23 => None

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/18280

Title:
  Firefox crashes when setting desktop wallpaper from image

Status in Juniper Openstack:
  New
Status in Juniper Openstack r2.20 series:
  Fix Committed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Firefox crashes when a user selects "Set as wallpaper" from the rick-click
  context menu over an image.

  A dialogue appears which allows you to set wallpaper properties, and when 
'Okay'
  is pressed, Firefox crashes. No useful messages appear to be output to the
  console (though I'm running only the standard firefox script from
  /usr/lib/mozilla-firefox/firefox)

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

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


[Desktop-packages] [Bug 1546823] Re: swig: disable PHP bindings until PHP7 support exists

2016-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package swig2.0 - 2.0.12-1ubuntu4

---
swig2.0 (2.0.12-1ubuntu4) xenial; urgency=medium

  * debian/rules: Disable PHP SWIG bindings for PHP7.0 transition
(LP: #1546823).

 -- Nishanth Aravamudan   Tue, 05 Apr
2016 12:01:14 -0700

** Changed in: swig2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1546823

Title:
  swig: disable PHP bindings until PHP7 support exists

Status in exactimage package in Ubuntu:
  Fix Released
Status in gdcm package in Ubuntu:
  Fix Released
Status in geos package in Ubuntu:
  Fix Released
Status in graphviz package in Ubuntu:
  Fix Released
Status in libkolabxml package in Ubuntu:
  Fix Committed
Status in mapserver package in Ubuntu:
  Fix Released
Status in owfs package in Ubuntu:
  Fix Released
Status in redland-bindings package in Ubuntu:
  Fix Released
Status in swig package in Ubuntu:
  Fix Committed
Status in swig2.0 package in Ubuntu:
  Fix Released

Bug description:
  As a short-term solution, we need to disable swig's PHP bindings, as
  it does not currently support PHP7.0
  (https://github.com/swig/swig/issues/571).

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

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


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => gtk+3.0 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates 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 
) 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** No longer affects: lightdm (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** No longer affects: lightdm (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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 @ 

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

2016-04-05 Thread Robert Ancell
What is a beamer?

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-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 `hal

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1291278] Re: Lightdm should wait until network is ready or time out

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1287633] Re: login password entry problem

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1233773] Re: lighdm does not change accessibility when login in lubuntu

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1244985] Re: LightDM sets wrong keyboard settings for a session

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1295837] Re: keyboard doesnt work after hibernation lockscreen

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1213596] Re: lightdm should warn when filesystems are read-only since then login is impossible

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1217378] Re: Lightdm does not recognize 3D acceleration with ati radeon driver (Low graphics mode error)

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1170971] Re: Start laptop and login screen doesn't appear

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1185567] Re: Changing an expired password in lightdm does not change gnome-keyring password

2016-04-05 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1165100] Re: Buffer over screen issue on select desktop environment

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1165100

Title:
  Buffer over screen issue on select desktop environment

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  It is preventing you from choosing your favorite  desktop environment.
  I've attached a photo to explain the issue.


  Description:  Ubuntu 12.10
  Release:  12.10

  lightdm:
Installed: 1.4.0-0ubuntu2
Candidate: 1.4.0-0ubuntu2
Version table:
   *** 1.4.0-0ubuntu2 0
  500 http://sa.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


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

2016-04-05 Thread Robert Ancell
** Package changed: lightdm (Ubuntu) => unity-system-compositor (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1181983] Re: Update to 1.2.3-0ubuntu2.1: Broken / Greeter won't start

2016-04-05 Thread Robert Ancell
Closing assumed fixed.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1126960] Re: You need to do something about default Hot keys in ubuntu

2016-04-05 Thread Robert Ancell
Ubuntu is not Windows - we don't want to emulate all those behaviours.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1126960

Title:
  You need to do something about default Hot keys in ubuntu

Status in lightdm package in Ubuntu:
  Opinion

Bug description:
  Hot keys like ctrl-alt-delete and and alt-F4 and alt-shift for languges and 
ctrl-a and all sorts of other default hot keys that windows users now by hart 
should be the default hot keys and then people would be able to change it on 
there own but the default should 
  always be the basis of your hot key system.

  and they also should work when you log off alt-shift for languges
  change for instance doesn't work when you log so there is some problem
  with entering the english password to log on so please fix it as soon
  as possible and i really don't know why you have not thought about it
  before i really don't but now you do so fix it please and thanks in
  advance.

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

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


[Desktop-packages] [Bug 1118798] Re: update keeps failing

2016-04-05 Thread Robert Ancell
** Changed in: lightdm (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1118798

Title:
  update keeps failing

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  installArchives() failed: (Reading database ... 
  dpkg: warning: files list file for package `thunderbird' missing, assuming 
package has no files currently installed.

  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 220467 files and directories currently installed.)
  Preparing to replace unity 5.18.0-0ubuntu1 (using 
.../unity_5.18.0-0ubuntu2_amd64.deb) ...
  Unpacking replacement unity ...
  Preparing to replace libunity-core-5.0-5 5.18.0-0ubuntu1 (using 
.../libunity-core-5.0-5_5.18.0-0ubuntu2_amd64.deb) ...
  Unpacking replacement libunity-core-5.0-5 ...
  Preparing to replace unity-services 5.18.0-0ubuntu1 (using 
.../unity-services_5.18.0-0ubuntu2_amd64.deb) ...
  Unpacking replacement unity-services ...
  Preparing to replace unity-common 5.18.0-0ubuntu1 (using 
.../unity-common_5.18.0-0ubuntu2_all.deb) ...
  Unpacking replacement unity-common ...
  Preparing to replace gnome-settings-daemon 3.4.2-0ubuntu0.6.1 (using 
.../gnome-settings-daemon_3.4.2-0ubuntu0.6.2_amd64.deb) ...
  Unpacking replacement gnome-settings-daemon ...
  Preparing to replace unity-greeter 0.2.8-0ubuntu1.4 (using 
.../unity-greeter_0.2.9-0ubuntu1_amd64.deb) ...
  Unpacking replacement unity-greeter ...
  Processing triggers for gconf2 ...
  Processing triggers for libglib2.0-0 ...
  Processing triggers for hicolor-icon-theme ...
  Setting up lightdm (1.2.3-0ubuntu1) ...
  dpkg: error processing lightdm (--configure):
   subprocess installed post-installation script returned error exit status 10
  Setting up man-db (2.6.1-2ubuntu1) ...
  dpkg: error processing man-db (--configure):
   subprocess installed post-installation script returned error exit status 10
  dpkg: dependency problems prevent configuration of ubuntu-standard:
   ubuntu-standard depends on man-db; however:
Package man-db is not configured yet.
  dpkg: error processing ubuntu-standard (--configure):
   dependency problems - leaving unconfigured
  Setting up checkbox (0.13.9) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  Traceback (most recent call last):
File "/usr/share/checkbox/install/config", line 162, in 
  sys.exit(main(sys.argv[1:]))
File "/usr/share/checkbox/install/config", line 156, in main
  install.write(file)
File "/usr/share/checkbox/install/config", line 122, in write
  new_value = self._debconf.get(question)
File "/usr/lib/python2.7/dist-packages/debconf.py", line 60, in 
  lambda *args, **kw: self.command(command, *args, **kw))
File "/usr/lib/python2.7/dist-packages/debconf.py", line 96, in command
  raise DebconfError(status, data)
  debconf.DebconfError: (10, "checkbox/plugins/apport_prompt/default_enabled 
doesn't exist")
  dpkg: error processing checkbox (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of checkbox-qt:
   checkbox-qt depends on checkbox (>= 0.13.9); however:
Package checkbox is not configured yet.
  dpkg: error processing checkbox-qt (--configure):
   dependency problems - leaving unconfigured
  Setting up grub-pc (1.99-21ubuntu3.9) ...
  No apport report written because MaxReports is reached already
  No apport report written because MaxReports is reached already
  dpkg: error processing grub-pc (--configure):
   subprocess installed post-installation script returned error exit status 10
  Setting up unity-services (5.18.0-0ubuntu2) ...
  No apport report written because MaxReports is reached already
  Setting up libunity-core-5.0-5 (5.18.0-0ubuntu2) ...
  Setting up unity-common (5.18.0-0ubuntu2) ...
  Setting up unity (5.18.0-0ubuntu2) ...
  Setting up gnome-settings-daemon (3.4.2-0ubuntu0.6.2) ...
  Setting up unity-greeter (0.2.9-0ubuntu1) ...
  dpkg: dependency problems prevent configuration of ubuntu-desktop:
   ubuntu-desktop depends on checkbox-qt; however:
Package checkbox-qt is not configured yet.
   ubuntu-desktop depends on lightdm; however:
Package lightdm is not configured yet.
  dpkg: error processing 

[Desktop-packages] [Bug 1534971] Re: banshee freezes on start

2016-04-05 Thread Francois Noel
In response to #11, as far as I know I have the default sqlite3 version.
3.11

$ dpkg -l | grep sqlite
ii  libmono-sqlite4.0-cil   
4.2.1.102+dfsg2-5ubuntu1 all  Mono Sqlite library (for 
CLI 4.0)
ii  libqt5sql5-sqlite:amd64 
5.5.1+dfsg-16ubuntu1 amd64Qt 5 SQLite 3 database 
driver
ii  libsqlite3-0:amd64  3.11.0-1ubuntu1 
 amd64SQLite 3 shared library
ii  libsqlite3-dev:amd643.11.0-1ubuntu1 
 amd64SQLite 3 development files

The CLI is package sqlite3 and also 3.11 but it's not installed on my
system.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/1534971

Title:
  banshee freezes on start

Status in banshee package in Ubuntu:
  Fix Released

Bug description:
  Banshee is not working on Ubuntu 16.04. With old config folder, it
  freezes on startup. If I remove the old config folder, Banshee starts
  correctly, but freezes everytime I launch the action to scan the music
  on my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: banshee 2.9.0+really2.6.2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 16 18:58:23 2016
  InstallationDate: Installed on 2015-01-16 (365 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to xenial on 2016-01-16 (0 days ago)

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

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


[Desktop-packages] [Bug 1535689] Re: Avila tablet is not recognised by libmtp

2016-04-05 Thread Yuan-Chen Cheng
** Changed in: avila
 Assignee: Yuan-Chen Cheng (ycheng-twn) => Alfonso Sanchez-Beato 
(alfonsosanchezbeato)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1535689

Title:
   Avila tablet is not recognised by libmtp

Status in The Avila project:
  Triaged
Status in Canonical System Image:
  Fix Committed
Status in libmtp package in Ubuntu:
  New

Bug description:
  The Avila tablet (product name is Frieza) is not recognised when in
  MTP file mode by Ubuntu.

   idVendor=2a47, idProduct=200D

  Tested on a trusty/precise/wily laptop and found the device is not
  listed in the desktop interface.

  The line below will make it work normally just for testing.
  ATTR{idVendor}=="2a47", ATTR{idProduct}=="200d", SYMLINK+="libmtp-%k", 
MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
  # Avila Frieza (MTP+ADB)

  Reproduction Proceedure:

   - Plug a tarblet into the Ubuntu desktop via a USB cable
   - Expect to see a natuilus window pop up, with the option to browse and copy 
files to the phone's file system

   - Actual result: no response from the Ubuntu host.

  Related OEM bug #1531494

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

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


[Desktop-packages] [Bug 1487819] Re: Wily user UI shows auto-login off after selecting on during install

2016-04-05 Thread Tim
oddly the toggle state works fine on xenial + GNOME 3.20, which would
still be using the same accountsservice. However the related code in
gnome-control-center has not changed in years

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1487819

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in accountsservice package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

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

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


[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-04-05 Thread Magnus Olsen
Running the following command from Terminal solved to problem for me.
Only hassle is that I have to log in every time with my pass and
username (for vpn): sudo openvpn --config file.ovpn

Be sure to find the correct folder where the relevant ovpn file is via
terminal, and then execute the before mentioned command.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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


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

2016-04-05 Thread Gunnar Hjalmarsson
Sponsored to the xenial queue.

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

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1487819] Re: Wily user UI shows auto-login off after selecting on during install

2016-04-05 Thread Tim
** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1487819

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in accountsservice package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

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

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


[Desktop-packages] [Bug 1564416] Re: [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all - Sony Vaio

2016-04-05 Thread Raymond
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=c3c2c9e7ff3e38bd9ff5b721b6ae8634fce42802

it worked in the previous basic model because the driver enable output
on four pins,

-   {0x15, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_OUT},
-   /* select line-out */
-   {0x0e, AC_VERB_SET_CONNECT_SEL, 0x00},
-   /* LINE-OUT pin */
-   {0x0f, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_OUT},
-   /* enable HP */
-   {0x10, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_HP},
-   /* enable Mono */
-   {0x11, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_OUT},

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

Title:
  [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all -
  Sony Vaio

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Release Ubuntu 16.04
  Bug (probably) in Alsa package - unity-control-center 
15.04.0+16.04.20160315-0ubuntu1
  I expected to hear sound from the built-in sound device.
  But there was no sound at all.

  This bug is a sort of regression. The problem was happening before;
  some days ago it disappeared (probably it was fixed); and now happens
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  1790 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 15:27:28 2016
  InstallationDate: Installed on 2016-03-17 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160304)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  1790 F pulseaudio
  Symptom_Jack: Green Line Out, Front
  Symptom_Type: No sound at all
  Title: [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2005
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0080J1
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0080J1:bd07/10/2005:svnSonyCorporation:pnVGN-FS315B:pvrC3LLQA01:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS315B
  dmi.product.version: C3LLQA01
  dmi.sys.vendor: Sony Corporation

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

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


[Desktop-packages] [Bug 1564416] Re: [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all - Sony Vaio

2016-04-05 Thread Raymond
The point is laptop should have speaker pin,  line out at sep mean dock
line out

Pulseaudio rely on the jack state of headphone to select active port and
mute/unmute

You have to provide out put of

 hdajacksensetest -a

to find out which node is headphone

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

Title:
  [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all -
  Sony Vaio

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Release Ubuntu 16.04
  Bug (probably) in Alsa package - unity-control-center 
15.04.0+16.04.20160315-0ubuntu1
  I expected to hear sound from the built-in sound device.
  But there was no sound at all.

  This bug is a sort of regression. The problem was happening before;
  some days ago it disappeared (probably it was fixed); and now happens
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  1790 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 31 15:27:28 2016
  InstallationDate: Installed on 2016-03-17 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160304)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  1790 F pulseaudio
  Symptom_Jack: Green Line Out, Front
  Symptom_Type: No sound at all
  Title: [VGN-FS315B, Realtek ALC260, Green Line Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2005
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0080J1
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0080J1:bd07/10/2005:svnSonyCorporation:pnVGN-FS315B:pvrC3LLQA01:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS315B
  dmi.product.version: C3LLQA01
  dmi.sys.vendor: Sony Corporation

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

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


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

2016-04-05 Thread Tim
** Patch added: "gdm3-path.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1547297/+attachment/4625468/+files/gdm3-path.debdiff

-- 
You received this bug notification because you are a member of Desktop
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:
  New
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1566596] [NEW] MBP 8, 2 internal microphone stopped working

2016-04-05 Thread Fernando
Public bug reported:

The internal microphone doesn't work in a Ubuntu Xenial installation.
The concrete model is Cirrus Logic CS4206. I've tested with the Xenial
live usb (2nd beta) and it doesn't work either, so it doesn't look line
I've broken something. However with the Wily live CD (both standard
Ubuntu and Kubuntu) it works.

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

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

Title:
  MBP 8,2 internal microphone stopped working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The internal microphone doesn't work in a Ubuntu Xenial installation.
  The concrete model is Cirrus Logic CS4206. I've tested with the Xenial
  live usb (2nd beta) and it doesn't work either, so it doesn't look
  line I've broken something. However with the Wily live CD (both
  standard Ubuntu and Kubuntu) it works.

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

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


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

2016-04-05 Thread Tim
Accounts Service is supposed to update custom.conf, but the path is
wrong now

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

-- 
You received this bug notification because you are a member of Desktop
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:
  New
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1291342] Re: Xorg crashed with SIGABRT in XIChangeDeviceProperty()

2016-04-05 Thread Bug Watch Updater
Launchpad has imported 35 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88903.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-02-01T23:59:54+00:00 Thilo-t wrote:

Created attachment 113027
Proposal for bugfix, applies against master branch 
064445364b4775b25ba49c2250b22b169f291147

Hello,

on my machine and touchpad (supports 3 touches) the Linux kernel may send 
multiple touch state updates per SYN_REPORT event, for the same slot.
I'm not much into Kernel code but reading the documentation to the evdev module 
there's nowhere written this must not happen so the synaptics driver should 
deal with it. Anyways, it doesn't and it had my XServer reliably crash after 
~3h of usage for the past two weeks on my new Laptop :(
Behaviour reproduced on a 3.16.0-0.bpo.4-amd64 kernel as well as most recent 
3.18.5, on a vanilla debian xorg-xserver, xf86-input-synaptics, as well as on 
the latest git versions.

Here's the event sequence that triggers it (some standard events like
abs position events partially omitted):

OPEN SLOT 0
ABS X
ABS Y
[...]
SYN_REPORT
OPEN SLOT 1
ABS [...]

SYN_REPORT

CLOSE SLOT 0
OPEN SLOT 0  <- here bad things will happen
ABS [...]
SYN_REPORT

The function EventProcessTouchEvent() in eventcomm.c:600 (just
overwrites the SLOTSTATE_CLOSE value so that HandleTouches in
synaptics.c never gets notified by the close.

Attached patch is a proposal to get rid of this unpleasant matter.
Will inject SYN_REPORT behaviour if a slotstate would be overwritten, and holds 
back the touch event until synaptics.c has been properly notified.

Best regards,
Thilo

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/1291342/comments/6


On 2015-02-02T00:33:07+00:00 Thilo-t wrote:

Oh, btw...

root@Helmuth:/usr/src/libevdev# cat /sys/class/input/event10/device/name 
ELAN0501:00 04F3:300B UNKNOWN
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/abs 
2608003
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/ev
b
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/ff
0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/key
6420 1 0 0 0 0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/led
0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/msc
0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/rel
0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/snd
0
root@Helmuth:/usr/src/libevdev# cat 
/sys/class/input/event10/device/capabilities/sw
0

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/1291342/comments/7


On 2015-02-02T02:01:32+00:00 Peter Hutterer wrote:

actually, can you attach the evemu-record output for this? That sounds
like a kernel bug the way you describe it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/1291342/comments/8


On 2015-02-02T02:38:06+00:00 Thilo-t wrote:

Created attachment 113029
Event log triggering bug

Here you go.

Interesting part starts at
0.318317

I thought it might be a kernel bug, but only saw
Documentation/input/event-codes.txt
I didn't see
Documentation/input/multi-touch-protocol.txt
yet for some reason.

I can reproduce this bug by touching the touchpad with finger 1, 2, and while 
keeping finger 2 on the pad, rapidly switching between finger 1 and 3.
The missing SYN_REPORT does not happen on every occasion, but still fairly 
often.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/1291342/comments/9


On 2015-02-02T03:29:47+00:00 Peter Hutterer wrote:

Indeed, that's a new one, didn't think that was legal and this sequence
will likely cause issues in evdev and libinput as well. Benjamin, Hans:
should we force the kernel to send a SYN_REPORT before re-opening a slot
in the same sync frame or just deal with it in userspace?

E: 0.318317 0003 002f   # EV_ABS / ABS_MT_SLOT  0
E: 0.318317 0003 0039 -001  # EV_ABS / ABS_MT_TRACKING_ID   -1
E: 0.318317 0003 002f 0001  # EV_ABS / ABS_MT_SLOT  1
E: 0.318317 0003 0035 0757  # EV_ABS / ABS_MT_POSITION_X757
E: 0.318317 0003 0036 0911  # EV_ABS / ABS_MT_POSITION_Y911
E: 0.318317 0003 002f   

[Desktop-packages] [Bug 1563184] Re: InitializeSandbox() called with multiple threads in process gpu-process

2016-04-05 Thread William Woods
Confirming that I am having the same issue on both an Orange Pi and a
ODroid running Ubuntu Mate 15.10.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
  InitializeSandbox() called with multiple threads in process gpu-
  process

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  crashes on startup with

  [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() 
called with multiple threads in process gpu-process
  Segmentation fault

  System ODROID XU3 armhf

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

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


[Desktop-packages] [Bug 1546823] Re: swig: disable PHP bindings until PHP7 support exists

2016-04-05 Thread Steve Langasek
** Changed in: swig (Ubuntu)
   Status: New => Fix Committed

** Changed in: swig2.0 (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1546823

Title:
  swig: disable PHP bindings until PHP7 support exists

Status in exactimage package in Ubuntu:
  Fix Released
Status in gdcm package in Ubuntu:
  Fix Released
Status in geos package in Ubuntu:
  Fix Released
Status in graphviz package in Ubuntu:
  Fix Released
Status in libkolabxml package in Ubuntu:
  Fix Committed
Status in mapserver package in Ubuntu:
  Fix Released
Status in owfs package in Ubuntu:
  Fix Released
Status in redland-bindings package in Ubuntu:
  Fix Released
Status in swig package in Ubuntu:
  Fix Committed
Status in swig2.0 package in Ubuntu:
  Fix Committed

Bug description:
  As a short-term solution, we need to disable swig's PHP bindings, as
  it does not currently support PHP7.0
  (https://github.com/swig/swig/issues/571).

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

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


[Desktop-packages] [Bug 1546823] Re: swig: disable PHP bindings until PHP7 support exists

2016-04-05 Thread Steve Langasek
** Changed in: libkolabxml (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland-bindings in Ubuntu.
https://bugs.launchpad.net/bugs/1546823

Title:
  swig: disable PHP bindings until PHP7 support exists

Status in exactimage package in Ubuntu:
  Fix Released
Status in gdcm package in Ubuntu:
  Fix Released
Status in geos package in Ubuntu:
  Fix Released
Status in graphviz package in Ubuntu:
  Fix Released
Status in libkolabxml package in Ubuntu:
  Fix Committed
Status in mapserver package in Ubuntu:
  Fix Released
Status in owfs package in Ubuntu:
  Fix Released
Status in redland-bindings package in Ubuntu:
  Fix Released
Status in swig package in Ubuntu:
  New
Status in swig2.0 package in Ubuntu:
  New

Bug description:
  As a short-term solution, we need to disable swig's PHP bindings, as
  it does not currently support PHP7.0
  (https://github.com/swig/swig/issues/571).

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

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


[Desktop-packages] [Bug 1501300] Re: [SRU] Wily (15.10) this package got not compiled with __cxx11 support

2016-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-3.4 -
1:3.4.2-13ubuntu2.1

---
llvm-toolchain-3.4 (1:3.4.2-13ubuntu2.1) wily; urgency=medium

  * d/rules: fix gcc-5 detection, since gcc-5.2 doesn't provide a g++-5.2
binary (but it is called g++-5). Patch cherry-picked from Debian
(Gianfranco Costamagna). LP: #1501300

 -- Iain Lane   Mon, 07 Dec 2015 13:10:08
+

** Changed in: llvm-toolchain-3.4 (Ubuntu Wily)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1501300

Title:
  [SRU] Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.4 source package in Wily:
  Fix Released

Bug description:
  [Impact]

  * with gcc-5 default, and llvm-3.4 built with the gcc-4.9, people
  can't link programs using cxx11 support

  [Test Case]

  * compile a program using cxx11 e.g. using boost libraries

  [Regression Potential]

  * llvm-3.4 is a compiler, and the change should affect only cxx11
  support (since the library is ABI compatible).

  So, fixing cxx11 support shouln't have any regression, only the
  feature will start working, while it wasn't before

  [Other Info]
   
  * Doko ack'd the SRU, and it should be the best voice here, for sure better 
than mine :)


  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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


[Desktop-packages] [Bug 1501300] Update Released

2016-04-05 Thread Chris Halse Rogers
The verification of the Stable Release Update for llvm-toolchain-3.4 has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1501300

Title:
  [SRU] Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.4 source package in Wily:
  Fix Released

Bug description:
  [Impact]

  * with gcc-5 default, and llvm-3.4 built with the gcc-4.9, people
  can't link programs using cxx11 support

  [Test Case]

  * compile a program using cxx11 e.g. using boost libraries

  [Regression Potential]

  * llvm-3.4 is a compiler, and the change should affect only cxx11
  support (since the library is ABI compatible).

  So, fixing cxx11 support shouln't have any regression, only the
  feature will start working, while it wasn't before

  [Other Info]
   
  * Doko ack'd the SRU, and it should be the best voice here, for sure better 
than mine :)


  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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


[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

2016-04-05 Thread Tony Espy
NM 1.1.93 ( 1.2-rc1 ) was just released.

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

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-iodine package in Ubuntu:
  Confirmed
Status in network-manager-openconnect package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" command and via
  D-Bus API.
  * The API for VPN plugins now supports multiple simultaneous connections.
  Most popular VPN plugins have been updated to support this functionality.
  * The libnm library now provides API to access VPN service 

[Desktop-packages] [Bug 572045] Re: should be marked undumpable to avoid PTRACE attach

2016-04-05 Thread Bug Watch Updater
** Changed in: gnupg2
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/572045

Title:
  should be marked undumpable to avoid PTRACE attach

Status in GNOME Keyring:
  Confirmed
Status in GnuPG2:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-keyring

  Programs that keep sensitive information in memory should avoid
  dumping core or being PTRACEable.  Things like ssh-agent already
  accomplish this by calling:

  prctl(PR_SET_DUMPABLE, 0);

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-keyring 2.92.92.is.2.30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  Architecture: amd64
  Date: Thu Apr 29 22:19:39 2010
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring

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

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


  1   2   3   >