[Desktop-packages] [Bug 1042069] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad

2016-07-28 Thread Robert Orzanna
Any updates on this?

Here is another screencast that demonstrates the problem:

https://www.youtube.com/watch?v=oTgaf8tTNEc

~Robert

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

Title:
  Jumpy Mouse Cursor using Thinkpad X230 Touchpad

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Expired

Bug description:
  Really annoying bug!

  Trackpoint moves the mouse cursor smootly,
  when using the touchpad i have a jumpy cursor. (vertically it moves fine, 
horizontally it moves always 4 pixels at once).

  Please see the following demonstration video:
  http://www.youtube.com/watch?v=XUVRKFUsAmc

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Date: Mon Aug 27 08:08:27 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120824)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1042069/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-28 Thread Daniel van Vugt
** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

Status in qtmir package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1607240/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-28 Thread Daniel van Vugt
** Description changed:

  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4
  
  wheel mouse scrolling is too fast, tried with firefox and geany.
  
  run firefox on mir scroll up/down some random long page using the mouse
  wheel
+ 
+ TEST CASE:
+ 
+   1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
+   2. Roll your mouse wheel over it and watch the log
+ 
+ Expected: vscroll values of +1/-1
+ Observed: vscroll values of +7/-7
+ 
+ WORKAROUND:
+ 
+ System Settings > Mouse & Touchpad >
+ Slide the second (unlabelled) slider all the way left, and then one notch 
right.
+ 
+ Turns out that unlabelled slider is the wheel scroll speed. Setting it
+ one notch from the left correctly reduces the wheel speed from 7.0 to
+ 1.0 as Mir clients expect.

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

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1607240/+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 1607583] Re: package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: package metacity-common is already installed and configured

2016-07-28 Thread dino99
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

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

Title:
  package metacity-common 1:2.34.13-0ubuntu4.1 failed to
  install/upgrade: package metacity-common is already installed and
  configured

Status in metacity package in Ubuntu:
  New

Bug description:
  Occurred during UBUNTU upgrade from 14.04 to 16.04 via GUI.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: metacity-common 1:3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptTermLog:
   
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul 29 02:12:58 2016
  DuplicateSignature:
   package:metacity-common:1:2.34.13-0ubuntu4.1
   Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
   dpkg: error processing package compiz-core (--configure):
package compiz-core is already installed and configured
  ErrorMessage: package metacity-common is already installed and configured
  InstallationDate: Installed on 2014-06-13 (776 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: metacity
  Title: package metacity-common 1:2.34.13-0ubuntu4.1 failed to 
install/upgrade: package metacity-common is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1607583/+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 1604704] Re: [regression] GTK apps hang for a long time on start-up under Xmir (and less under native Mir) failing to find dbus

2016-07-28 Thread Daniel van Vugt
Confirmed in all cases it's just that the X11/Xmir apps can't detect the
session bus address of the login (which is on a different TTY BTW).
Forcing DBUS_SESSION_BUS_ADDRESS solves the problem.

Here are some stack traces of the hangs:

gedit:
(gdb) bt
#0  0x7705e853 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7477acd1 in g_spawn_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7477b313 in g_spawn_command_line_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x77862b70 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x778645f2 in g_dbus_address_get_for_bus_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7786f7ee in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7787522b in g_bus_get_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x7784b969 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x778488f3 in g_application_register ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x7784918f in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#10 0x778494f2 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x00400cfa in main ()

nautilus:
(gdb) bt
#0  0x734c9833 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
#1  0x7418ecd1 in g_spawn_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7418f313 in g_spawn_command_line_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x74729b70 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7472b5f2 in g_dbus_address_get_for_bus_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x747367ee in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7473c22b in g_bus_get_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x74712969 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x7470f8f3 in g_application_register ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x0042c78e in ?? ()
#10 0x7fffedd29e40 in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#11 0x7fffedd298ab in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#12 0x7441fcf5 in g_cclosure_marshal_generic_va ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7441f1d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x744394b8 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7443a08f in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x74710168 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x747104f2 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#18 0x0042ba31 in ?? ()
#19 0x733ed7e0 in __libc_start_main (main=0x42b970, argc=1, 
argv=0x7fffe5b8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe5a8)
at ../csu/libc-start.c:291
#20 0x0042ba99 in ?? ()

/usr/games/sol:
(gdb) bt
#0  0x7537556d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x70fdacf8 in _dbus_read ()
   from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2  0x70fde349 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3  0x70fd2c95 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4  0x70fd2b3a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x70fbd32f in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x70fb8e08 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7fffedc925f6 in atspi_get_a11y_bus ()
   from /usr/lib/x86_64-linux-gnu/libatspi.so.0
#8  0x739e9052 in atk_bridge_adaptor_init ()
   from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
#9  0x77117134 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x75f3dfa5 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x75f4ffc1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x75f58d5c in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x75f5908f in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x75f424d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x75f44961 in g_object_notify ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x76de5778 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#17 0x75f3e1d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x75f589a6 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x75f59555 in g_signal_emit_by_name ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x76e0b6c5 in ?? () from 

[Desktop-packages] [Bug 1606901] Re: Clicking "Show details" in AO for Nautilus produces "Could not find 'nautilus.desktop'" error from gnome-software

2016-07-28 Thread Jeremy Bicha
I suspect this is related to the final lines of

https://bazaar.launchpad.net/~ubuntu-
desktop/nautilus/ubuntu/view/head:/debian/rules

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

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

** Tags added: yakkety

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

Title:
  Clicking "Show details" in AO for Nautilus produces "Could not find
  'nautilus.desktop'" error from gnome-software

Status in Ubuntu GNOME:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In the Activities Overview applications list, if I right-click on
  "Files" (AKA Nautilus) and select the "Show details" option gnome-
  software is launched but with the error of "Could not find
  'nautilus.desktop'":

  gnome-software_Could_Not_Find_Nautilus-desktop.png

  I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am also not sure as
  to which package to report this issue under (gnome-shell, nautilus,
  gnome-software, or perhaps something else), but as soon as I find out
  (if you know please comment) I will report it upstream under the
  relevant package (if that is required) and also mark this bug as
  affecting the package here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1606901/+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 1606901] Re: Clicking "Show details" in AO for Nautilus produces "Could not find 'nautilus.desktop'" error from gnome-software

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Clicking "Show details" in AO for Nautilus produces "Could not find
  'nautilus.desktop'" error from gnome-software

Status in Ubuntu GNOME:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In the Activities Overview applications list, if I right-click on
  "Files" (AKA Nautilus) and select the "Show details" option gnome-
  software is launched but with the error of "Could not find
  'nautilus.desktop'":

  gnome-software_Could_Not_Find_Nautilus-desktop.png

  I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am also not sure as
  to which package to report this issue under (gnome-shell, nautilus,
  gnome-software, or perhaps something else), but as soon as I find out
  (if you know please comment) I will report it upstream under the
  relevant package (if that is required) and also mark this bug as
  affecting the package here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1606901/+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 1606901] Re: Clicking "Show details" in AO for Nautilus produces "Could not find 'nautilus.desktop'" error from gnome-software

2016-07-28 Thread Jeremy Bicha
** Changed in: ubuntu-gnome
   Importance: Undecided => Low

** Changed in: ubuntu-gnome
   Status: New => Confirmed

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

Title:
  Clicking "Show details" in AO for Nautilus produces "Could not find
  'nautilus.desktop'" error from gnome-software

Status in Ubuntu GNOME:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In the Activities Overview applications list, if I right-click on
  "Files" (AKA Nautilus) and select the "Show details" option gnome-
  software is launched but with the error of "Could not find
  'nautilus.desktop'":

  gnome-software_Could_Not_Find_Nautilus-desktop.png

  I am running Ubuntu GNOME 16.04 with GNOME 3.20. I am also not sure as
  to which package to report this issue under (gnome-shell, nautilus,
  gnome-software, or perhaps something else), but as soon as I find out
  (if you know please comment) I will report it upstream under the
  relevant package (if that is required) and also mark this bug as
  affecting the package here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1606901/+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 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start

2016-07-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1604704 ***
https://bugs.launchpad.net/bugs/1604704

I'm making this a duplicate of bug 1604704 now which is clearer.

The fix for bug 1604872 has not solved it.

** This bug is no longer a duplicate of bug 1604872
   Apps can't connect to the user's session bus, even though it exists

** This bug has been marked a duplicate of bug 1604704
   [regression] GTK apps hang for a long time on start-up under Xmir (and less 
under native Mir) failing to find dbus

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

Title:
  X apps that use dbus (GTK, Firefox) either don't start or take a very
  long time to start

Status in Libertine:
  New
Status in dbus package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  ubuntu 16.10 + proposed / unity8 - desktop x86

  libertine apps don't work anymore
  attached are firefox and nautilus logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1603904/+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 1604704] Re: [regression] GTK apps hang for a long time on start-up under Xmir (and less under native Mir) failing to find dbus

2016-07-28 Thread Daniel van Vugt
The yakkety fix for bug 1604872 has not solved this. So no longer a
duplicate.

** This bug is no longer a duplicate of bug 1604872
   Apps can't connect to the user's session bus, even though it exists
** This bug has been marked a duplicate of bug 1603904
   X apps that use dbus (GTK, Firefox) either don't start or take a very long 
time to start

** This bug is no longer a duplicate of bug 1603904
   X apps that use dbus (GTK, Firefox) either don't start or take a very long 
time to start

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [regression] GTK apps hang for a long time on start-up under Xmir (and
  less under native Mir) failing to find dbus

Status in dbus package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  $ /usr/games/sol

  (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
  Failed to connect to socket /tmp/dbus-7diijTV1R5: Connection refused
  GConf Error: No D-BUS daemon running

  
  (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
  Failed to connect to socket /tmp/dbus-Zlu4hiB92O: Connection refused
  GConf Error: No D-BUS daemon running

  
  $ nautilus

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1604704/+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 1555568] Re: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to he

2016-07-28 Thread mtvoid
I have tried that earlier. In my case, I can set Internal Mic, Headset
Mic, or Headphone Mic as the Capture source. The hiss does not go away
when it is set to Internal or Headset Mic. When I set it to Headphone
Mic, it stops, but so does all sound output, so it does not work for me.

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

Title:
  [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant
  cracking sound, even when idel (no media playback). Muting and
  unmuting the sound seems to help for around half a minute...

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound constantly cracking, even when not playing any media. Muting and 
unmuting solves the problem for less than a minute. 
  Running kernel 4.4.4, but the problem was still present on the factory Ubuntu 
15.10 installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.4-040404-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseny 1639 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 10 13:22:09 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P96YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/13/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0P96YG:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/168/+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 1607470] Re: LightDM (in locked state) shows desktop if I try to change keyboard layout

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

** Summary changed:

- LightDM (in locked state) shows desktop if I try to change keyboard layout
+ Screenlock shows desktop if I try to change keyboard layout

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

Title:
  Screenlock shows desktop if I try to change keyboard layout

Status in unity package in Ubuntu:
  New

Bug description:
  This bug is related to bug#1606555. But this is also a security and
  privacy threat.

  release of Ubuntu: Ubuntu 16.04

  What's happening:

  I lock my machine(Super + L key)
  LightDM greeter is showing.
  If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
  It's a privacy risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1607470/+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 1605117] Re: LightDM tray items disappear after logout

2016-07-28 Thread Robert Ancell
I've made a release with just this change (1.18.2-0ubuntu2).

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

** Changed in: lightdm
Milestone: None => 1.18.3

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

** Changed in: lightdm
   Importance: Undecided => High

** Description changed:

- LightDM tray items disappear after logout
+ [Impact]
+ Unity Greeter indications don't show second time greeter started.
  
- Steps to reproduce:
- 1) install latest LightDM updates (reboot)
- 2) login
- 3) logout
+ [Test Case]
+ 1. Log in with greeter
+ 2. Log out
  
- Downgrading to LightDM 1.18.1-0ubuntu1 fix problem
+ Expected result:
+ Unity greeter is shown with all UI elements as in step 1.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: lightdm 1.18.2-0ubuntu1
- ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
- Uname: Linux 4.4.0-31-generic i686
- ApportVersion: 2.20.1-0ubuntu2.1
- Architecture: i386
- CurrentDesktop: Unity
- Date: Thu Jul 21 10:57:44 2016
- InstallationDate: Installed on 2016-05-23 (58 days ago)
- InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
- SourcePackage: lightdm
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Observed result:
+ Unity greeter is shown but only one indicator shows (accessibility)
+ 
+ [Regression potential]
+ Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Description changed:

  [Impact]
- Unity Greeter indications don't show second time greeter started.
+ Unity Greeter indicatiors don't show second time greeter started.
  
  [Test Case]
  1. Log in with greeter
  2. Log out
  
  Expected result:
  Unity greeter is shown with all UI elements as in step 1.
  
  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)
  
  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Description changed:

  [Impact]
- Unity Greeter indicatiors don't show second time greeter started.
+ Unity Greeter indicators don't show second time greeter started.
  
  [Test Case]
  1. Log in with greeter
  2. Log out
  
  Expected result:
  Unity greeter is shown with all UI elements as in step 1.
  
  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)
  
  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Summary changed:

- LightDM tray items disappear after logout
+ Unity greeter indicators don't show on second launch

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

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1605117/+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 1606275] Re: gnome-software doesn't run

2016-07-28 Thread Alexander Grünewald
** This bug is no longer a duplicate of bug 1606238
   gnome-software won't open

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

Title:
  gnome-software doesn't run

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Entering gnome-software in a terminal results in a new process called
  'gnome-software' but no window and no messages in the terminal.
  Doesn't run using unity launcher either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 07:49:18 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-30 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606275/+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 1606238] Re: gnome-software won't open

2016-07-28 Thread Alexander Grünewald
** This bug is no longer a duplicate of bug 1577602
   ubuntu-software will not launch

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

Title:
  gnome-software won't open

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I upgrade the system from Ubuntu 14.04 to 16.04 some time ago.
  At beginning, gnome-software refused to open and I had to remove old ubuntu 
software and "--reinstall" the gnome-software.
  Everything was fine, except for many sorts of packages it can't install so I 
installed synaptic.

  Some days ago, gnome software went on a strike but claimed nothing !
  I can open a terminal and call gnome-software : nothing 
  The launcher turns around in the dock.

  Any Idea ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 15:28:05 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606238/+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 1606275] Re: gnome-software doesn't run

2016-07-28 Thread Alexander Grünewald
*** This bug is a duplicate of bug 1606238 ***
https://bugs.launchpad.net/bugs/1606238

** This bug is no longer a duplicate of bug 1577602
   ubuntu-software will not launch

** This bug has been marked a duplicate of bug 1606238
   gnome-software won't open

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

Title:
  gnome-software doesn't run

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Entering gnome-software in a terminal results in a new process called
  'gnome-software' but no window and no messages in the terminal.
  Doesn't run using unity launcher either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 07:49:18 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-30 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606275/+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 1606238] Re: gnome-software won't open

2016-07-28 Thread Alexander Grünewald
** This bug has been marked a duplicate of bug 1577602
   ubuntu-software will not launch

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

Title:
  gnome-software won't open

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I upgrade the system from Ubuntu 14.04 to 16.04 some time ago.
  At beginning, gnome-software refused to open and I had to remove old ubuntu 
software and "--reinstall" the gnome-software.
  Everything was fine, except for many sorts of packages it can't install so I 
installed synaptic.

  Some days ago, gnome software went on a strike but claimed nothing !
  I can open a terminal and call gnome-software : nothing 
  The launcher turns around in the dock.

  Any Idea ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 15:28:05 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606238/+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 1606275] Re: gnome-software doesn't run

2016-07-28 Thread Alexander Grünewald
*** This bug is a duplicate of bug 1577602 ***
https://bugs.launchpad.net/bugs/1577602

** This bug has been marked a duplicate of bug 1577602
   ubuntu-software will not launch

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

Title:
  gnome-software doesn't run

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Entering gnome-software in a terminal results in a new process called
  'gnome-software' but no window and no messages in the terminal.
  Doesn't run using unity launcher either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 07:49:18 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-30 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606275/+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 1606238] Re: gnome-software won't open

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-software won't open

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I upgrade the system from Ubuntu 14.04 to 16.04 some time ago.
  At beginning, gnome-software refused to open and I had to remove old ubuntu 
software and "--reinstall" the gnome-software.
  Everything was fine, except for many sorts of packages it can't install so I 
installed synaptic.

  Some days ago, gnome software went on a strike but claimed nothing !
  I can open a terminal and call gnome-software : nothing 
  The launcher turns around in the dock.

  Any Idea ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 15:28:05 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606238/+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 1606275] Re: gnome-software doesn't run

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-software doesn't run

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Entering gnome-software in a terminal results in a new process called
  'gnome-software' but no window and no messages in the terminal.
  Doesn't run using unity launcher either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 07:49:18 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-30 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1606275/+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 1607478] Re: Please don't feature the GNOME Maps app

2016-07-28 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

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

Title:
  Please don't feature the GNOME Maps app

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The GNOME Maps app is the most prominent app in Ubuntu's Software app.
  It's the only app with a large wide-screen banner on the home page of
  the Software app.

  The Maps app currently doesn't work because the server it was using
  stopped providing free map tiles. See bug 1602035 for more info.

  This bug was originally reported at
  
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 28 14:15:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1607478/+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 1607583] Re: package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: package metacity-common is already installed and configured

2016-07-28 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package metacity-common 1:2.34.13-0ubuntu4.1 failed to
  install/upgrade: package metacity-common is already installed and
  configured

Status in metacity package in Ubuntu:
  New

Bug description:
  Occurred during UBUNTU upgrade from 14.04 to 16.04 via GUI.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: metacity-common 1:3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptTermLog:
   
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul 29 02:12:58 2016
  DuplicateSignature:
   package:metacity-common:1:2.34.13-0ubuntu4.1
   Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
   dpkg: error processing package compiz-core (--configure):
package compiz-core is already installed and configured
  ErrorMessage: package metacity-common is already installed and configured
  InstallationDate: Installed on 2014-06-13 (776 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: metacity
  Title: package metacity-common 1:2.34.13-0ubuntu4.1 failed to 
install/upgrade: package metacity-common is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1607583/+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 1607583] [NEW] package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: package metacity-common is already installed and configured

2016-07-28 Thread Ben Saini
Public bug reported:

Occurred during UBUNTU upgrade from 14.04 to 16.04 via GUI.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: metacity-common 1:3.18.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.1-0ubuntu2.1
AptTermLog:
 
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Jul 29 02:12:58 2016
DuplicateSignature:
 package:metacity-common:1:2.34.13-0ubuntu4.1
 Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
 dpkg: error processing package compiz-core (--configure):
  package compiz-core is already installed and configured
ErrorMessage: package metacity-common is already installed and configured
InstallationDate: Installed on 2014-06-13 (776 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: metacity
Title: package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: 
package metacity-common is already installed and configured
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package metacity-common 1:2.34.13-0ubuntu4.1 failed to
  install/upgrade: package metacity-common is already installed and
  configured

Status in metacity package in Ubuntu:
  New

Bug description:
  Occurred during UBUNTU upgrade from 14.04 to 16.04 via GUI.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: metacity-common 1:3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptTermLog:
   
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul 29 02:12:58 2016
  DuplicateSignature:
   package:metacity-common:1:2.34.13-0ubuntu4.1
   Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
   dpkg: error processing package compiz-core (--configure):
package compiz-core is already installed and configured
  ErrorMessage: package metacity-common is already installed and configured
  InstallationDate: Installed on 2014-06-13 (776 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: metacity
  Title: package metacity-common 1:2.34.13-0ubuntu4.1 failed to 
install/upgrade: package metacity-common is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1607583/+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 1607573] Re: package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2016-07-28 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 1

Status in ppp package in Ubuntu:
  New

Bug description:
  I upgrated from 14 to 16.04.
  During installation I had a bug.
  After installation I restated the computer and the desktop launch was broken 
in this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ppp 2.4.5-5.1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jul 28 20:23:17 2016
  DuplicateSignature:
   package:ppp:2.4.5-5.1ubuntu2.2
   De-configuring network-manager (0.9.8.8-0ubuntu7.3) ...
   update-rc.d: /etc/init.d/pppd-dns exists during rc.d purge (use -f to force)
   dpkg: error processing archive 
/var/cache/apt/archives/ppp_2.4.7-1+2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2015-08-28 (335 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ppp
  Title: package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1607573/+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 1607573] [NEW] package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2016-07-28 Thread Horea Aflat
Public bug reported:

I upgrated from 14 to 16.04.
During installation I had a bug.
After installation I restated the computer and the desktop launch was broken in 
this bug.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ppp 2.4.5-5.1ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jul 28 20:23:17 2016
DuplicateSignature:
 package:ppp:2.4.5-5.1ubuntu2.2
 De-configuring network-manager (0.9.8.8-0ubuntu7.3) ...
 update-rc.d: /etc/init.d/pppd-dns exists during rc.d purge (use -f to force)
 dpkg: error processing archive 
/var/cache/apt/archives/ppp_2.4.7-1+2ubuntu1_amd64.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2015-08-28 (335 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ppp
Title: package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 1

Status in ppp package in Ubuntu:
  New

Bug description:
  I upgrated from 14 to 16.04.
  During installation I had a bug.
  After installation I restated the computer and the desktop launch was broken 
in this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ppp 2.4.5-5.1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jul 28 20:23:17 2016
  DuplicateSignature:
   package:ppp:2.4.5-5.1ubuntu2.2
   De-configuring network-manager (0.9.8.8-0ubuntu7.3) ...
   update-rc.d: /etc/init.d/pppd-dns exists during rc.d purge (use -f to force)
   dpkg: error processing archive 
/var/cache/apt/archives/ppp_2.4.7-1+2ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2015-08-28 (335 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ppp
  Title: package ppp 2.4.5-5.1ubuntu2.2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1607573/+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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-28 Thread Fritz Hudnut
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel 
wrote:

> In the meantime you could try to get one of the other drivers
>> "modesetting", "fbdev", "fbdevhw" to work with 24 bit depth. You can use
>> my xorg.conf as starting point and edit it manually. Just put it in
>> /etc/X11.
>>
>
> So, I tried the -configure and that failed.  Then I wrote the xorg.conf
> out as per your suggestion using "modesetting" . . . didn't seem to work;
> changed it to "fbdevhw" didn't seem to work.  Trying to "rm r128" and said
> "File not found."
>

My xorg.conf file, see anything wrong with it??  Still booting to black
screen--here I'm in "live" DVD and I copied the xorg.conf file:

Section   "Device"
  Identifier  "Card0"
  Driver  "fbdevhw"
EndSection

Section   "Monitor"
  Identifier  "Monitor0"
EndSection

Section   "Screen"

  Identifier "Screen0"
  Device "Card0"
  Monitor"Monitor0"
  DefaultDepth 24
  SubSection  "Display"
 Viewport   0 0
 Depth  24
 Modes "1024 x 768"
  EndSubSection
EndSection

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

2016-07-28 Thread Launchpad Bug Tracker
This bug was fixed in the package x11proto-randr - 1.5.0-1~trusty1

---
x11proto-randr (1.5.0-1~trusty1) trusty; urgency=medium

  * Backport for lts-xenial stack. (LP: #1577734)

 -- Timo Aaltonen   Tue, 03 May 2016 16:41:48 +0300

** Changed in: x11proto-randr (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1577734/+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 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

2016-07-28 Thread Launchpad Bug Tracker
This bug was fixed in the package libxrandr - 2:1.5.0-1~trusty1

---
libxrandr (2:1.5.0-1~trusty1) trusty; urgency=medium

  * Backport for lts-xenial stack. (LP: #1577734)

 -- Timo Aaltonen   Tue, 03 May 2016 16:25:01 +0300

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

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1577734/+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 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

2016-07-28 Thread Adam Conrad
Marking v-done, based on IRC feedback.

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1577734/+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 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

2016-07-28 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-3.8 -
1:3.8-2ubuntu3~trusty4

---
llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty4) trusty; urgency=medium

  * rules, libllvmX.Y.{links,install}.in: Rename libllvm3.8 to
libllvm3.8v4.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty3) trusty; urgency=medium

  * control: Rename libllvm3.8 to libllvm3.8v4 so upgrades to xenial
work.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty2) trusty; urgency=medium

  * Drop the libjsoncpp-dev Build-Depend, as it's in universe in trusty.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty1) trusty; urgency=medium

  * Backport to trusty. (LP: #1577734)
  * clang-X.Y.install.in: Drop cmake files, cmake in trusty is too old.

 -- Adam Conrad   Wed, 29 Jun 2016 21:20:51 -0600

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1577734/+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 1577734] Update Released

2016-07-28 Thread Adam Conrad
The verification of the Stable Release Update for x11proto-randr 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 libxrandr in Ubuntu.
https://bugs.launchpad.net/bugs/1577734

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1577734/+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 1443718] Re: nautilus crashed with SIGABRT in g_assertion_message() on "create new directory with selection"

2016-07-28 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message() on "create new
  directory with selection"

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The crash happens in a local folder.

  Operation to reproduce:
  - select 4 files
  - right-click and select creat new directory with this selection

  Expected:
  a "New Folder" directory with the 4 selected files moved inside it.

  Got:
  a "New Folder" with only 2 files inside it, and a nautilus crash.

  Additional:
  Operation was done while some other files were moved from ftp:// to a file:// 
other folder.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 14 02:36:56 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2011-11-05 (1256 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to vivid on 2015-04-11 (2 days ago)
  UserGroups: adm admin audio bumblebee cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1443718/+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 1589741] Re: package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to install/upgrade: в новой версии пакета нет этого сценария, отказ

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to
  install/upgrade: в новой версии пакета нет этого сценария, отказ

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  "Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file 
or directory
  var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it."

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-opencl-icd-361 361.45.11-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Tue Jun  7 07:03:09 2016
  Dependencies:
   gcc-6-base 6.1.1-4ubuntu11
   libc6 2.23-0ubuntu3
   libgcc1 1:6.1.1-4ubuntu11
   ocl-icd-libopencl1 2.2.9-1
  ErrorMessage: в новой версии пакета нет этого сценария, отказ
  RelatedPackageVersions:
   dpkg 1.18.7ubuntu1
   apt  1.3~exp1
  SourcePackage: nvidia-graphics-drivers-361
  Title: package nvidia-opencl-icd-361 361.45.11-0ubuntu2 failed to 
install/upgrade: в новой версии пакета нет этого сценария, отказ
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1589741/+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 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11

2016-07-28 Thread Tony Espy
The fix is currently in silo 005, and was just marked 'Lander Approved'.

The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and
should hopefully land in the next few days.


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

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

Title:
  [regression] [OTA-11] Adding new wifi networks (with long passwords)
  never connect at all since OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+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 1607478] Re: Please don't feature the GNOME Maps app

2016-07-28 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: Unknown => Confirmed

** Changed in: gnome-software
   Importance: Unknown => Medium

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

Title:
  Please don't feature the GNOME Maps app

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  The GNOME Maps app is the most prominent app in Ubuntu's Software app.
  It's the only app with a large wide-screen banner on the home page of
  the Software app.

  The Maps app currently doesn't work because the server it was using
  stopped providing free map tiles. See bug 1602035 for more info.

  This bug was originally reported at
  
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 28 14:15:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1607478/+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 1603501] Re: gimp: symbol lookup error: gimp: undefined symbol: gegl_param_multiline_get_type

2016-07-28 Thread 3vi1
This is fixed in the latest gimp package (2.8.16-2.2ubuntu1)

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

Title:
  gimp: symbol lookup error: gimp: undefined symbol:
  gegl_param_multiline_get_type

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  On fully up to date 16.10 installs, gimp no longer starts.

  1.  Run 'gimp' from console.
  2.  Console returns:  "gimp: symbol lookup error: gimp: undefined symbol: 
gegl_param_multiline_get_type" and exits, instead of starting the app.

  The installed package/version of gimp is 2.8.16-1ubuntu3.  Gimp was
  previously working fine on this install, so my guess is the symbol was
  deprecated/removed in a new version of some gegl lib.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gimp 2.8.16-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 15 11:41:37 2016
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1603501/+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 1555568] Re: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to he

2016-07-28 Thread Paulo Zúñiga
Hi!, I have the same computer model, and activate the "headset mic" in
alsamixer fix the problem (sorry for my English).

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

Title:
  [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant
  cracking sound, even when idel (no media playback). Muting and
  unmuting the sound seems to help for around half a minute...

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound constantly cracking, even when not playing any media. Muting and 
unmuting solves the problem for less than a minute. 
  Running kernel 4.4.4, but the problem was still present on the factory Ubuntu 
15.10 installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.4-040404-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseny 1639 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 10 13:22:09 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P96YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/13/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0P96YG:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/168/+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 1605408] Re: Don't set IM "xim" by default

2016-07-28 Thread Gunnar Hjalmarsson
I installed language-selector-{gnome,common} 0.165.4 from xenial-
proposed on a Xubuntu system, reproduced the test case, and can confirm
the changed behavior.

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

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

Title:
  Don't set IM "xim" by default

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Since the fix of  "cjkv" has been
  the system default in im-config for some flavors (e.g. Xubuntu,
  Lubuntu), which means that an IM framework is started and configured
  only if one of the CJKV languages is the selected display language.
  For other languages "cjkv" means that no IM related environment
  variables are set (value "none"). However, when starting gnome-
  language-selector first time after installation of one of those
  flavors, the selected IM method is set to "xim" automatically. This is
  undocumented behavior, and the background is commented in the bug
  description of .

  As illustrated in , the "xim"
  input method occasionally causes hard to debug keyboard problems. For
  this reason gnome-language-selector should not set "xim", but simply
  confirm the "none" default value from im-config.

  Some users need "xim" to access X11 dead key and compose key variants,
  and this means that they will always need to set it explicitly. The
  upside is that users who encounter problems with "xim" will do so as a
  result of an active measure, which increases the chance that they
  understand the causality.

  [Test Case]

  On a Xubuntu or Lubuntu system with a non-CJKV display language:

  * Remove already set user specific IM configuration:

rm -f ~/.xinputrc

  * Open gnome-language-selector, and find that the selected "keyboard
input method system" is "XIM".

  After installing the proposed version of language-selector-gnome,
  those steps instead result in the value "none".

  [Regression Potential]

  Low. This is only about the default value applied by gnome-language-
  selector, so it doesn't change an already set user specific IM
  configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1605408/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

2016-07-28 Thread radiantptz
Confirmed fixed on @robert123m post #5 above on ubuntu 16.04.1 LTS.
Can't thank you enough. Here is my env for reference:

$ dpkg -l | grep 'pulse\|bluetooth' 
ii  blueman 2.0.4-1ubuntu2
ii  gir1.2-gnomebluetooth-1.0:amd64 3.18.2-1ubuntu2
ii  gnome-bluetooth 3.18.2-1ubuntu2
ii  gstreamer1.0-pulseaudio:amd64   1.8.2-1ubuntu0.1
ii  libbluetooth3:amd64 5.37-0ubuntu5
ii  libcanberra-pulse:amd64 0.30-2.1ubuntu1
ii  libgnome-bluetooth13:amd64  3.18.2-1ubuntu2
ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3
ii  libpulse0:amd64 1:8.0-0ubuntu3
ii  libpulse0:i386  1:8.0-0ubuntu3
ii  libpulsedsp:amd64   1:8.0-0ubuntu3
ii  pulseaudio  1:8.0-0ubuntu3
ii  pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ii  pulseaudio-module-x11   1:8.0-0ubuntu3
ii  pulseaudio-utils1:8.0-0ubuntu3

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1607478] Re: Please don't feature the GNOME Maps app

2016-07-28 Thread Jeremy Bicha
This is actually a bug in the upstream part of GNOME Software and not
because of Ubuntu-specific customizations. So I attached the upstream
bug report.

** Bug watch added: GNOME Bug Tracker #769285
   https://bugzilla.gnome.org/show_bug.cgi?id=769285

** Also affects: gnome-software via
   https://bugzilla.gnome.org/show_bug.cgi?id=769285
   Importance: Unknown
   Status: Unknown

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

Title:
  Please don't feature the GNOME Maps app

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  New

Bug description:
  The GNOME Maps app is the most prominent app in Ubuntu's Software app.
  It's the only app with a large wide-screen banner on the home page of
  the Software app.

  The Maps app currently doesn't work because the server it was using
  stopped providing free map tiles. See bug 1602035 for more info.

  This bug was originally reported at
  
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 28 14:15:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1607478/+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 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

2016-07-28 Thread Daniel Richard G.
Maybe make display-manager.service into an actual service file (rather
than a symlink), and have that start whatever /etc/X11/default-display-
manager points to?

What I want is to be able to disable and then re-enable the display
manager starting on boot using similar administrative commands, like a
"systemctl disable/enable" pair. Even better if the argument to the
commands is the same in both cases.

(Possibly even better yet if default-display-manager could be set to
some "null" option, so you can disable/re-enable the display manager
without ever touching systemd...)

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  New

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1584575/+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 1598904] Re: X server crashes sporadically with a segfault

2016-07-28 Thread Christopher M. Penalver
Stefan Freyr, if you install the xenial xorg enablement stack following
https://wiki.ubuntu.com/Kernel/LTSEnablementStack is this issue still
reproducible?

** Tags removed: bios-outdated-1.24
** Tags added: latest-bios-1.25

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

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

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

Title:
  X server crashes sporadically with a segfault

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My desktop session crashes sporadically. Often this happens when I
  leave the computer and the screensaver starts (Euphoria GL
  screensaver). This bug is not reproducible on demand.

  Attached is my Xorg log file which seems to indicate that this problem
  is related to the i915 driver code.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2016-05-26 (59 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.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
  MachineType: LENOVO 20BWS18900
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7
  Tags:  trusty ubuntu
  Uname: Linux 4.6.3-040603-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS18900
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS18900
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 25 09:49:33 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1133
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598904/+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 1605408] Re: Don't set IM "xim" by default

2016-07-28 Thread Brian Murray
Hello Gunnar, or anyone else affected,

Accepted language-selector into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.165.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: language-selector (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Don't set IM "xim" by default

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Since the fix of  "cjkv" has been
  the system default in im-config for some flavors (e.g. Xubuntu,
  Lubuntu), which means that an IM framework is started and configured
  only if one of the CJKV languages is the selected display language.
  For other languages "cjkv" means that no IM related environment
  variables are set (value "none"). However, when starting gnome-
  language-selector first time after installation of one of those
  flavors, the selected IM method is set to "xim" automatically. This is
  undocumented behavior, and the background is commented in the bug
  description of .

  As illustrated in , the "xim"
  input method occasionally causes hard to debug keyboard problems. For
  this reason gnome-language-selector should not set "xim", but simply
  confirm the "none" default value from im-config.

  Some users need "xim" to access X11 dead key and compose key variants,
  and this means that they will always need to set it explicitly. The
  upside is that users who encounter problems with "xim" will do so as a
  result of an active measure, which increases the chance that they
  understand the causality.

  [Test Case]

  On a Xubuntu or Lubuntu system with a non-CJKV display language:

  * Remove already set user specific IM configuration:

rm -f ~/.xinputrc

  * Open gnome-language-selector, and find that the selected "keyboard
input method system" is "XIM".

  After installing the proposed version of language-selector-gnome,
  those steps instead result in the value "none".

  [Regression Potential]

  Low. This is only about the default value applied by gnome-language-
  selector, so it doesn't change an already set user specific IM
  configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1605408/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

2016-07-28 Thread Christopher M. Penalver
Oliver, in 14.04, which version of the nvidia driver were you using
specifically?

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

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.

  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases.
  Sometimes ubuntu freezes after lightdm restart and a hard reset has to
  be performed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
     Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: evdev: Dell Dell USB Wired Entry Keyboard: Unable to open 
evdev device "/dev/input/event7".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607212/+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 1587808] Re: Ubuntu-emulator no network on latest image

2016-07-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking-
xenial

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

Title:
  Ubuntu-emulator no network on latest image

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in phablet-tools package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test
  2. run ubuntu-emulator-run rc-test

  EXPECTED:
  Expected I expect there to be a mock sim installed and a network connection

  ACTUAL:
  You get the message from the wizard saying there is no sim installed and from 
the running setup you can not connect to the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+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 1511626] Re: gvfsd-smb crashed with signal 5 in g_settings_set_property()

2016-07-28 Thread Alistair Buxton
User error. XDG_DATA_DIRS was messed up by local configuration.

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

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

Title:
  gvfsd-smb crashed with signal 5 in g_settings_set_property()

Status in gvfs package in Ubuntu:
  Invalid

Bug description:
  Happens every time I try to mount a samba share.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gvfs-backends 1.24.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  Date: Fri Oct 30 06:32:26 2015
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb
  InstallationDate: Installed on 2015-07-12 (110 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   g_settings_set_property (object=0x1695f50 [GSettings], prop_id=, value=, pspec=) at 
/build/buildd/glib2.0-2.44.1/./gio/gsettings.c:521
   g_object_new_internal (nqueue=, value=, 
pspec=, object=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1415
   g_object_new_internal (class=0x7f1d6cc47c00 , 
class@entry=0x16a, params=0x0, params@entry=0x7ffea81b7370, n_params=1) at 
/build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1808
   g_object_new_valist (object_type=object_type@entry=23644640, 
first_property_name=first_property_name@entry=0x7f1d6d4efc4f "schema-id", 
var_args=var_args@entry=0x7ffea81b74c0) at 
/build/buildd/glib2.0-2.44.1/./gobject/gobject.c:2033
   g_object_new (object_type=23644640, first_property_name=0x7f1d6d4efc4f 
"schema-id") at /build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1617
  ThreadStacktrace: $4 = 0x4 
  Title: gvfsd-smb crashed with signal 5 in g_settings_set_property()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1511626/+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 1607478] Re: Please don't feature the GNOME Maps app

2016-07-28 Thread Jeremy Bicha
** Tags removed: gnome3-ppa third-party-packages
** Tags added: xenial

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

Title:
  Please don't feature the GNOME Maps app

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The GNOME Maps app is the most prominent app in Ubuntu's Software app.
  It's the only app with a large wide-screen banner on the home page of
  the Software app.

  The Maps app currently doesn't work because the server it was using
  stopped providing free map tiles. See bug 1602035 for more info.

  This bug was originally reported at
  
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 28 14:15:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1607478/+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 1607478] [NEW] Please don't feature the GNOME Maps app

2016-07-28 Thread Jeremy Bicha
Public bug reported:

The GNOME Maps app is the most prominent app in Ubuntu's Software app.
It's the only app with a large wide-screen banner on the home page of
the Software app.

The Maps app currently doesn't work because the server it was using
stopped providing free map tiles. See bug 1602035 for more info.

This bug was originally reported at
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jul 28 14:15:30 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-09 (109 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gnome3-ppa third-party-packages yakkety

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

Title:
  Please don't feature the GNOME Maps app

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The GNOME Maps app is the most prominent app in Ubuntu's Software app.
  It's the only app with a large wide-screen banner on the home page of
  the Software app.

  The Maps app currently doesn't work because the server it was using
  stopped providing free map tiles. See bug 1602035 for more info.

  This bug was originally reported at
  
https://www.reddit.com/r/Ubuntu/comments/4v0qip/since_gnome_maps_no_longer_works_perhaps_it/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 28 14:15:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1607478/+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 1587808] Re: Ubuntu-emulator no network on latest image

2016-07-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking

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

Title:
  Ubuntu-emulator no network on latest image

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in phablet-tools package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test
  2. run ubuntu-emulator-run rc-test

  EXPECTED:
  Expected I expect there to be a mock sim installed and a network connection

  ACTUAL:
  You get the message from the wizard saying there is no sim installed and from 
the running setup you can not connect to the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+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 1607470] [NEW] LightDM (in locked state) shows desktop if I try to change keyboard layout

2016-07-28 Thread Alex
Public bug reported:

This bug is related to bug#1606555. But this is also a security and
privacy threat.

release of Ubuntu: Ubuntu 16.04

What's happening:

I lock my machine(Super + L key)
LightDM greeter is showing.
If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
It's a privacy risk.

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

** Information type changed from Private Security to Public

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

Title:
  LightDM (in locked state) shows desktop if I try to change keyboard
  layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  This bug is related to bug#1606555. But this is also a security and
  privacy threat.

  release of Ubuntu: Ubuntu 16.04

  What's happening:

  I lock my machine(Super + L key)
  LightDM greeter is showing.
  If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
  It's a privacy risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1607470/+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 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

2016-07-28 Thread John McAleely
** Description changed:

  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387
  
  Flash phone with --bootstrap, and walk through the welcome wizard. Once
  you have a phone to use, visit the BT settings, and pair a mono 'HSP'
  headset. In my case an old Jabra OTE-1.
  
  Once the device is paired, make an incoming call to the handset. Use the
- button to answer the call.
+ headset button to answer the call.
  
  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.
  
  I heard no audio.
  
  Expected: Audio was heard on the headset during the call.
  
  Note that this does not occur on rc-proposed/meizu.en #381, so it seems
  to be a recent regression.

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

2016-07-28 Thread Levente Ábrók
"Tenten36 (tenten) wrote on 2016-07-27:

The problem still exists with kernel 4.6 and 4.7 from the mainline
build.

$ DRI_PRIME=1 glxgears

gives black screen"

That seems like a regression or the newest kernels weren't patched.
Currently using 4.4.14 and it still works.

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Desktop-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

2016-07-28 Thread John McAleely
I plan to capture logs, following the instructions here:

https://wiki.ubuntu.com/DebuggingBluetooth

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+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 1605291] Re: please merge llvm-toolchain-3.8 from Debian

2016-07-28 Thread Ariel Faigon
Confirming that this upgrade fixes the problem for me.
clang++ now links successfully vs. system boost libs.
Thanks to all involved!

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

Title:
  please merge llvm-toolchain-3.8 from Debian

Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released

Bug description:
  debdiff attached and build ongoing @ ppa:costamagnagianfranco
  /locutusofborg-ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1605291/+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 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

2016-07-28 Thread John McAleely
I discovered this apparent regression while testing the silo 60+37 combo
@koza is using to land bluez 5.41, but note that the bug appears (and
then disappears) on vanilla 387 vs 381.


** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+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 1607466] [NEW] Mono BT headset has no in-call audio on recent rc-proposed

2016-07-28 Thread John McAleely
Public bug reported:

MX4/arale
ubuntu-touch/rc-proposed/meizu.en #387

Flash phone with --bootstrap, and walk through the welcome wizard. Once
you have a phone to use, visit the BT settings, and pair a mono 'HSP'
headset. In my case an old Jabra OTE-1.

Once the device is paired, make an incoming call to the handset. Use the
button to answer the call.

The handset transitions to showing you an in-call UI, and appears to
claim the audio is routed to the headset.

I heard no audio.

Expected: Audio was heard on the headset during the call.

Note that this does not occur on rc-proposed/meizu.en #381, so it seems
to be a recent regression.

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

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

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

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

** Also affects: phone-app (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+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 1607464] [NEW] Postscript error during printing

2016-07-28 Thread Jonathan Scheff
Public bug reported:

Ubuntu 16.0.4
HP network printer
Prints document, except for last page, with this output:

ERROR:
undefined
OFFENDING COMMAND:
...Undefined
STACK:
{the rest of the error has varied; sometimes numbers like -699.95, -300.0, 
-mark-, and others}

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 E [28/Jul/2016:11:51:52 -0500] [cups-deviced] PID 19542 (gutenprint52+usb) 
stopped with status 1!
 E [28/Jul/2016:11:56:25 -0500] [cups-deviced] PID 19768 (gutenprint52+usb) 
stopped with status 1!
CurrentDesktop: Unity
Date: Thu Jul 28 12:11:59 2016
InstallationDate: Installed on 2016-07-25 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for Hewlett-Packard-HP-LaserJet-P2055dn: 
hp:/net/HP_LaserJet_P2055dn?ip=129.59.192.55
MachineType: Dell Inc. OptiPlex 9020
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd: Permission 
denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=314827a7-bd99-490e-b24f-2d38a73a9889 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0N4YC8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd01/08/2015:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9020
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Postscript error during printing

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 16.0.4
  HP network printer
  Prints document, except for last page, with this output:

  ERROR:
  undefined
  OFFENDING COMMAND:
  ...Undefined
  STACK:
  {the rest of the error has varied; sometimes numbers like -699.95, -300.0, 
-mark-, and others}

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   E [28/Jul/2016:11:51:52 -0500] [cups-deviced] PID 19542 (gutenprint52+usb) 
stopped with status 1!
   E [28/Jul/2016:11:56:25 -0500] [cups-deviced] PID 19768 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: Unity
  Date: Thu Jul 28 12:11:59 2016
  InstallationDate: Installed on 2016-07-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for Hewlett-Packard-HP-LaserJet-P2055dn: 
hp:/net/HP_LaserJet_P2055dn?ip=129.59.192.55
  MachineType: Dell Inc. OptiPlex 9020
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=314827a7-bd99-490e-b24f-2d38a73a9889 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd01/08/2015:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1607464/+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 753520] Re: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

2016-07-28 Thread aenertia
this occurs when using the Māori keyboard layout also

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

Title:
  remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

Status in freerdp:
  New
Status in remmina:
  New
Status in remmina package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: remmina

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy remmina
  remmina:
    Installed: 1.1.1-1ubuntu1
    Candidate: 1.1.1-1ubuntu1
    Version table:
   *** 1.1.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one has their default keyboard
  setting set to en_US > System Settings... > Text Entry > change to
  Input sources to use: Maori > close window > secondary click the Text
  Input tray icon and change from English to Maori > restart > open
  Remmina and it works.

  4) What happens instead is it crashes consistently:
  remmina
  Remmina plugin VNC (type=Protocol) registered.
  Remmina plugin VNCI (type=Protocol) registered.
  Remmina plugin RDP (type=Protocol) registered.
  Remmina plugin RDPF (type=File) registered.
  Remmina plugin RDPS (type=Preference) registered.
  Segmentation fault

  First reported against Ubuntu 11.04, remmina 0.9.3-2

  WORKAROUND: Use en_US.

  WORKAROUND: Remove remmina-plugin-rdp.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: remmina 0.9.3-2
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Apr  7 15:17:34 2011
  ExecutablePath: /usr/bin/remmina
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: remmina
  ProcEnviron:
   LANGUAGE=en_ZA:en
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc61738202b 
:   mov(%r12),%rdi
   PC (0x7fc61738202b) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   find_keyboard_layout_in_xorg_rules () from /usr/lib/libfreerdpkbd.so.0
   detect_keyboard_layout_from_xkb () from /usr/lib/libfreerdpkbd.so.0
   detect_and_load_keyboard () from /usr/lib/libfreerdpkbd.so.0
   freerdp_kbd_init () from /usr/lib/libfreerdpkbd.so.0
   remmina_plugin_rdpset_init () from 
/usr/lib/remmina/plugins/remmina-plugin-rdp.so
  Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/freerdp/+bug/753520/+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 753520] Re: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

2016-07-28 Thread aenertia
Appears fixed in remmina-next paa for yakkety https://launchpad.net
/~remmina-ppa-team/+archive/ubuntu/remmina-next

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

Title:
  remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()

Status in freerdp:
  New
Status in remmina:
  New
Status in remmina package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: remmina

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy remmina
  remmina:
    Installed: 1.1.1-1ubuntu1
    Candidate: 1.1.1-1ubuntu1
    Version table:
   *** 1.1.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one has their default keyboard
  setting set to en_US > System Settings... > Text Entry > change to
  Input sources to use: Maori > close window > secondary click the Text
  Input tray icon and change from English to Maori > restart > open
  Remmina and it works.

  4) What happens instead is it crashes consistently:
  remmina
  Remmina plugin VNC (type=Protocol) registered.
  Remmina plugin VNCI (type=Protocol) registered.
  Remmina plugin RDP (type=Protocol) registered.
  Remmina plugin RDPF (type=File) registered.
  Remmina plugin RDPS (type=Preference) registered.
  Segmentation fault

  First reported against Ubuntu 11.04, remmina 0.9.3-2

  WORKAROUND: Use en_US.

  WORKAROUND: Remove remmina-plugin-rdp.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: remmina 0.9.3-2
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Apr  7 15:17:34 2011
  ExecutablePath: /usr/bin/remmina
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: remmina
  ProcEnviron:
   LANGUAGE=en_ZA:en
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc61738202b 
:   mov(%r12),%rdi
   PC (0x7fc61738202b) ok
   source "(%r12)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   find_keyboard_layout_in_xorg_rules () from /usr/lib/libfreerdpkbd.so.0
   detect_keyboard_layout_from_xkb () from /usr/lib/libfreerdpkbd.so.0
   detect_and_load_keyboard () from /usr/lib/libfreerdpkbd.so.0
   freerdp_kbd_init () from /usr/lib/libfreerdpkbd.so.0
   remmina_plugin_rdpset_init () from 
/usr/lib/remmina/plugins/remmina-plugin-rdp.so
  Title: remmina crashed with SIGSEGV in find_keyboard_layout_in_xorg_rules()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/freerdp/+bug/753520/+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 1598904] Re: X server crashes sporadically with a segfault

2016-07-28 Thread Stefan Freyr
I have cleaned out my kernel packages and now I only have the official
trusty kernel package installed. So I'm running on kernel 3.13 now and
I've just experienced this crash again.

This time I was looking at Google maps on Chrome, so nothing special
really going on (except maybe if Google maps is using some hardware
acceleration similar to the ones that the Euphoria screensaver is
using).

But as I said, I'm now running on the official kernel so I'm re-
uploading the Xorg log file.

➜  ~ uname -a
Linux hyperion-stfs 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

** Attachment added: "xorg_crash_20160728_xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598904/+attachment/4708817/+files/xorg_crash_20160728_xorg.log

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

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

Title:
  X server crashes sporadically with a segfault

Status in xorg package in Ubuntu:
  New

Bug description:
  My desktop session crashes sporadically. Often this happens when I
  leave the computer and the screensaver starts (Euphoria GL
  screensaver). This bug is not reproducible on demand.

  Attached is my Xorg log file which seems to indicate that this problem
  is related to the i915 driver code.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2016-05-26 (59 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.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
  MachineType: LENOVO 20BWS18900
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7
  Tags:  trusty ubuntu
  Uname: Linux 4.6.3-040603-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS18900
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS18900
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 25 09:49:33 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1133
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11

2016-07-28 Thread Will Cooke
Added to Trello: https://trello.com/c/6XAwMt2L/25-bug-1588126
-regression-ota-11-adding-new-wifi-networks-with-long-passwords-never-
connect-at-all-since-ota-11

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

Title:
  [regression] [OTA-11] Adding new wifi networks (with long passwords)
  never connect at all since OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+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 1573720] Automatically added comment

2016-07-28 Thread Will Cooke
Added to Trello: https://trello.com/c/dRvmReff/24-bug-1573720
-unencrypted-private-keys-are-insecure-error-reported-even-when-key-is-
encrypted

** Tags removed: desktop-trello-import

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1573720/+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 1473246] Re: MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager

2016-07-28 Thread John Schimandle
Oops. Forgot to mention that I had to change the rule a little bit
because the idVendor is 4255 on the GoPro Hero 3+Black camera. You can
get the idVendor from the /var/log/syslog file when the device
enumerates.

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

Title:
  MediaTek Preloader on a mobile device triggers cdc_acm kernel module
  usage by ModemManager

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  This is an interesting bug that is triggered under some circumstances
  if one of the official, MediaTek-SoC-based Ubuntu phones is connected
  to a Linux host via USB.

  Tested host:
  Ubuntu 15.04 Desktop, kernel 3.19.0-21-generic, package linux-image-generic 
3.19.0.22.21 amd64, package modemmanager 1.4.0-1 

  Tested phones:
  Meizu MX4 (arale) and bq Aquaris E4.5 (krillin), image version irrelevant 
because the Preloader comes with all devices and cannot be changed

  How to reproduce, possibility 1:
  1. Disconnect the USB connection, if necessary.
  2. Turn off the phone.
  3. Connect the phone via USB. It will take a bit and then turn on, displaying 
the "charge animation".

  How to reproduce, possibility 2:
  1. Reboot the phone while it is still attached to the host.

  The kernel ringbuffer will contain the following log messages (example
  for krillin):

  [288774.244158] usb 1-1: new high-speed USB device number 22 using xhci_hcd
  [288774.373589] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000
  [288774.373593] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [288774.373594] usb 1-1: Product: MT65xx Preloader
  [288774.373596] usb 1-1: Manufacturer: MediaTek
  [288774.435247] cdc_acm 1-1:1.1: ttyACM26: USB ACM device
  [288774.874607] usb 1-1: USB disconnect, device number 22
  [288774.874755] cdc_acm 1-1:1.1: failed to set dtr/rts

  And syslog will contain the following log messages:

  Jul 10 00:58:07 fire ModemManager[1103]:   (tty/ttyACM27): released by 
modem /sys/devices/pci:00/:00:14.0/usb1/1-1
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Iridium) 
[ttyACM27] error when checking support: '(Iridium) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Cinterion) 
[ttyACM27] error when checking support: '(Cinterion) Missing port probe for 
port (tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Nokia) 
[ttyACM27] error when checking support: '(Nokia) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Generic) 
[ttyACM27] error when checking support: '(Generic) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   Couldn't find support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  The allocated ttyACMx device is never freed, and after a couple of
  days developing on the phone (with lots of phone restarts) I've
  noticed that my machine has accumulated an usage count of 58:

  $ lsmod | grep cdc_acm
  cdc_acm36864  58

  lsof show that ModemManager still holds the devices:

  # sudo lsof | grep ACM
  ModemMana  9214   root9u  CHR  166,1  
 0t07599355 /dev/ttyACM1 (deleted)
  ModemMana  9214   root   10u  CHR  166,0  
 0t07596974 /dev/ttyACM0 (deleted)
  ...

  Restarting ModemManager immediately reduces the usage count to 0 again
  and frees all devices.

  Why does this happen? Luckily I've read the MediaTek Preloader source
  code. The Preloader is the first-stage bootloader on MediaTek SoCs and
  exposes a proprietary USB interface that can be used for debugging
  purposes and to download firmware to the device. The implementation of
  this interface is rudimentary and emulates a CDC ACM serial port,
  which probably doesn't fully conform to the standard and also just
  falls from the bus after a short amount of time if the host doesn't
  initiate the proprietary protocol. So I think the kernel and
  ModemManager immediately try to use the emulated device when it
  becomes available, but because the implementation in the Preloader is
  incomplete some bug (timeout?) is triggered and ModemManager never
  closes the device.

  Sadly I don't have the expertise to decide if this is a bug in
  ModemManager or the kernel or both, so I file it with ModemManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1473246/+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 1473246] Re: MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager

2016-07-28 Thread John Schimandle
This also solved my problem on a serial communication issue I was having
with a GoPro Hero 3+Black camera over USB with a serial interface that
enumerates as ttyACM device files. The Linux host was a Banana Pi
running this build of Linux.

http://mirror.igorpecovnik.com/Armbian_4.2_Bananapi_Debian_jessie_4.1.6.zip

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

Title:
  MediaTek Preloader on a mobile device triggers cdc_acm kernel module
  usage by ModemManager

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  This is an interesting bug that is triggered under some circumstances
  if one of the official, MediaTek-SoC-based Ubuntu phones is connected
  to a Linux host via USB.

  Tested host:
  Ubuntu 15.04 Desktop, kernel 3.19.0-21-generic, package linux-image-generic 
3.19.0.22.21 amd64, package modemmanager 1.4.0-1 

  Tested phones:
  Meizu MX4 (arale) and bq Aquaris E4.5 (krillin), image version irrelevant 
because the Preloader comes with all devices and cannot be changed

  How to reproduce, possibility 1:
  1. Disconnect the USB connection, if necessary.
  2. Turn off the phone.
  3. Connect the phone via USB. It will take a bit and then turn on, displaying 
the "charge animation".

  How to reproduce, possibility 2:
  1. Reboot the phone while it is still attached to the host.

  The kernel ringbuffer will contain the following log messages (example
  for krillin):

  [288774.244158] usb 1-1: new high-speed USB device number 22 using xhci_hcd
  [288774.373589] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000
  [288774.373593] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [288774.373594] usb 1-1: Product: MT65xx Preloader
  [288774.373596] usb 1-1: Manufacturer: MediaTek
  [288774.435247] cdc_acm 1-1:1.1: ttyACM26: USB ACM device
  [288774.874607] usb 1-1: USB disconnect, device number 22
  [288774.874755] cdc_acm 1-1:1.1: failed to set dtr/rts

  And syslog will contain the following log messages:

  Jul 10 00:58:07 fire ModemManager[1103]:   (tty/ttyACM27): released by 
modem /sys/devices/pci:00/:00:14.0/usb1/1-1
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Iridium) 
[ttyACM27] error when checking support: '(Iridium) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Cinterion) 
[ttyACM27] error when checking support: '(Cinterion) Missing port probe for 
port (tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Nokia) 
[ttyACM27] error when checking support: '(Nokia) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   (Plugin Manager) (Generic) 
[ttyACM27] error when checking support: '(Generic) Missing port probe for port 
(tty/ttyACM27)'
  Jul 10 00:58:10 fire ModemManager[1103]:   Couldn't find support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  The allocated ttyACMx device is never freed, and after a couple of
  days developing on the phone (with lots of phone restarts) I've
  noticed that my machine has accumulated an usage count of 58:

  $ lsmod | grep cdc_acm
  cdc_acm36864  58

  lsof show that ModemManager still holds the devices:

  # sudo lsof | grep ACM
  ModemMana  9214   root9u  CHR  166,1  
 0t07599355 /dev/ttyACM1 (deleted)
  ModemMana  9214   root   10u  CHR  166,0  
 0t07596974 /dev/ttyACM0 (deleted)
  ...

  Restarting ModemManager immediately reduces the usage count to 0 again
  and frees all devices.

  Why does this happen? Luckily I've read the MediaTek Preloader source
  code. The Preloader is the first-stage bootloader on MediaTek SoCs and
  exposes a proprietary USB interface that can be used for debugging
  purposes and to download firmware to the device. The implementation of
  this interface is rudimentary and emulates a CDC ACM serial port,
  which probably doesn't fully conform to the standard and also just
  falls from the bus after a short amount of time if the host doesn't
  initiate the proprietary protocol. So I think the kernel and
  ModemManager immediately try to use the emulated device when it
  becomes available, but because the implementation in the Preloader is
  incomplete some bug (timeout?) is triggered and ModemManager never
  closes the device.

  Sadly I don't have the expertise to decide if this is a bug in
  ModemManager or the kernel or both, so I file it with ModemManager.

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

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

[Desktop-packages] [Bug 1578243] Re: Screen configuration is not preserved when logging out and logging back in

2016-07-28 Thread Donjan Rodic
Just upgraded from 14.04 to 16.04.1 and found this (and the workaround)
via googling.

I drop my laptop on a dock with two vertically oriented (rotated to
portrait) monitors. This was working fine before, now it lights them up
without the rotation. Rotating them manually via System Settings ->
Displays, undocking and docking again reverts to the wrong (landscape)
orientation.

The ~/.config/monitors.xml looks fine but seems to be ignored.
Reloading the settings with

  killall unity-settings-daemon

gives me the correct orientation, which is read from the monitor.xml
(editing the file by hand and killing u-s-d accepts whatever changes I
make), it just doesn't get triggered on docking changes.

That's the workaround for now: kill u-s-d every time I dock to the workplace.
It would be nice for patchlvl 1 LTS upgrades to not break such basic stuff.

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

Title:
  Screen configuration is not preserved when logging out and logging
  back in

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I have two identical monitors, with the dock on the left-hand side of
  the left monitor and the stickiness of the middle edge between the two
  monitors disabled.

  When I log out and immediately log back in, my monitor configuration
  changes and now both monitors are mirroring the same content. I have
  to hit Command-P to get them to switch back to the non-mirrored
  configuration they were displaying immediately before I logged out.

  This happens consistently, every time I log out and log back in.

  The monitor configuration should be preserved when I log out and log
  back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 10:27:26 2016
  DistUpgraded: 2016-04-28 15:18:23,890 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics 
Controller [1558:7410]
  MachineType: System76, Inc. Galago UltraPro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 
quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (5 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  upstart.unity7.log: JavaScript error: , line 0: uncaught exception: 2147746065
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 10:20:25 2016
  xserver.configfile: default
  xserver.errors: Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1578243] Re: Screen configuration is not preserved when logging out and logging back in

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen configuration is not preserved when logging out and logging
  back in

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I have two identical monitors, with the dock on the left-hand side of
  the left monitor and the stickiness of the middle edge between the two
  monitors disabled.

  When I log out and immediately log back in, my monitor configuration
  changes and now both monitors are mirroring the same content. I have
  to hit Command-P to get them to switch back to the non-mirrored
  configuration they were displaying immediately before I logged out.

  This happens consistently, every time I log out and log back in.

  The monitor configuration should be preserved when I log out and log
  back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  4 10:27:26 2016
  DistUpgraded: 2016-04-28 15:18:23,890 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics 
Controller [1558:7410]
  MachineType: System76, Inc. Galago UltraPro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 
quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (5 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  upstart.unity7.log: JavaScript error: , line 0: uncaught exception: 2147746065
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 10:20:25 2016
  xserver.configfile: default
  xserver.errors: Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1578243/+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 1600124] Re: Adjust KBL PCI-ID's

2016-07-28 Thread Seth Forshee
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+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 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

2016-07-28 Thread Martin Pitt
pitti | IIRC all *dm's postinsts need to set 
/etc/systemd/system/display-manager.service to
   | whatever was chosen in debconf
 pitti | setting Alias= sounds correct, but not WantedBy=
 pitti | we don't want *all* DMs to start
 pitti | the whole mechanics for that is still horribly complicated and 
redundant -- you can
   | use update-rc.d, debconf, /etc/X11/default-display-manager etc.
 pitti | I think /etc/X11/default-display-manager is still meant to be the 
canonical way to
   | configure this, that's why we skipped the [Install] sections so that 
you don't
   | introduce contradictions with systemctl enable/disable

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  New

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1584575/+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 1605117] Re: LightDM tray items disappear after logout

2016-07-28 Thread Sebastien Bacher
thanks Robert, I can confirm that this patch applied on the current
xenial package fixes the issue

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

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

Title:
  LightDM tray items disappear after logout

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  LightDM tray items disappear after logout

  Steps to reproduce:
  1) install latest LightDM updates (reboot)
  2) login
  3) logout

  Downgrading to LightDM 1.18.1-0ubuntu1 fix problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:57:44 2016
  InstallationDate: Installed on 2016-05-23 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1605117/+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 1586539] Re: Major screen flickering in Chromium and Google Chrome

2016-07-28 Thread Vasya Pupkin
Looks like this issue will never be fixed because no one cares about
xf86-video-intel. Newer version of Ubuntu and Debian distributions
switched to xf86-video-modesetting, more info can be found here:
http://phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-
Intel-DDX

So the solution is simple:

1. sudo apt-get purge xserver-xorg-video-intel
2. sudo rm /usr/share/X11/xorg.conf.d/20-intel.conf (for those who created this 
file before)
3. reboot

I've been testing this fix for 3 days and the only issue I found was
xbacklight tool no longer working, which is a known issue as well.

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in X.Org X server:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  WORKAROUND: Add in /usr/share/X11/xorg.conf.d/20-intel.conf:

  Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id  

[Desktop-packages] [Bug 1607190] Re: Feature request: activate screensaver, keep access to media player hotkeys

2016-07-28 Thread Sebastien Bacher
** 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/1607190

Title:
  Feature request: activate screensaver, keep access to media player
  hotkeys

Status in unity package in Ubuntu:
  Triaged

Bug description:
  Dear all,

  Let me share a feature request with you.

  Frequently, I start listening to music in Rhythmbox and then use FN +
  F3 on my keyboard to activate the lockscreen screensaver because it
  switches of my screen after a few seconds and thus saves conserves
  energy on my laptop.

  However, once the screensaver is active, I cannot any longer access my
  media player using my hotkeys FN + F10 (backwards), FN + F11
  (play/pause) and FN + F12 (forward).

  Would it be possible to keep access to these media player hotkeys with
  the screensaver lock screen being enabled?

  Thankfully,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1607190/+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 1573206] Re: GNOME Software does not install third-party .deb packages

2016-07-28 Thread tesoid
*** This bug is a duplicate of bug 1573408 ***
https://bugs.launchpad.net/bugs/1573408

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

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

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

Title:
  GNOME Software does not install third-party .deb packages

Status in gdebi:
  New
Status in GNOME Software:
  New
Status in GRadio:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nn_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdebi/+bug/1573206/+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 1607287] Re: [OTA12] Google Calendar webapp crashes on start

2016-07-28 Thread Alexandre Abreu
** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** No longer affects: webapps-applications (Ubuntu)

** Also affects: webapps-core
   Importance: Undecided
   Status: New

** Changed in: webapps-core
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

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

Title:
  [OTA12] Google Calendar webapp crashes on start

Status in Canonical System Image:
  New
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New

Bug description:
  After updating to OTA12 Google Calendar webapp crashes on start up,
  both in bq E5 and M10

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607287/+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 1607384] [NEW] Document Viewer does not remember window size

2016-07-28 Thread drwt
Public bug reported:

Evince does not remember it's window size so every time I start to view
a PDF I have to manually configure the window size which gets tedious
very quickly.

I would like Evince to remember it's fullscreen state so my workflow is
smoother.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: XFCE
Date: Thu Jul 28 16:54:11 2016
InstallationDate: Installed on 2016-06-02 (56 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  Document Viewer does not remember window size

Status in evince package in Ubuntu:
  New

Bug description:
  Evince does not remember it's window size so every time I start to
  view a PDF I have to manually configure the window size which gets
  tedious very quickly.

  I would like Evince to remember it's fullscreen state so my workflow
  is smoother.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jul 28 16:54:11 2016
  InstallationDate: Installed on 2016-06-02 (56 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1607384/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

2016-07-28 Thread Oliver
Hello Christopher,

here the answers to your questions. I hope it helps.

1) What release did you upgrade from where this problem wasn't
reproducible?

I was using the 14.04 (stable) beforehand and I can't recall having this 
problem.
Another thing is that I recently switched from a HDMI-DVI to a HDMI-HDMI cable. 
To my knowledge the problem didn't occur with the HDMI-DVI cable (even the 
sleep and suspend feature was working without any problems). 

2) In the prior working release, were you using the nvidia proprietary
drivers?

Yes, I was using the nvidia proprietary drivers.

3) If you uninstall the nvidia proprietary drivers does this provide a
WORKAROUND?

If I'm not to use the proprietary one the issue is even more persistent.
Xrandr is showing the second monitor as connected, but even a restart of
the lightdm service doesn't help. The monitor always shows "no signal".

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

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.

  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases.
  Sometimes ubuntu freezes after lightdm restart and a hard reset has to
  be performed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
     Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  

[Desktop-packages] [Bug 1607375] [NEW] After PC suspend screen is freezing and is white.

2016-07-28 Thread Jozsef Vasarhelyi
Public bug reported:

lsb_release -rd
Description:Ubuntu 14.04.4 LTS
Release:14.04

After PC suspend screen is freezing and is white.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-77-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Jul 28 15:15:43 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: vboxhost, 5.0.26, 3.16.0-77-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0695]
InstallationDate: Installed on 2015-06-29 (394 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Dell Inc. Inspiron 5548
ProcEnviron:
 LANGUAGE=hu
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-77-generic.efi.signed 
root=UUID=7b6f5337-e94f-46cb-8573-476093c584c8 ro plymouth:debug splash quiet 
drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 079JDM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Inspiron 5548
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jul 28 15:11:29 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4333 
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
   After PC suspend screen is freezing and is white.

Status in xorg package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  After PC suspend screen is freezing and is white.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul 28 15:15:43 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.26, 3.16.0-77-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0695]
  InstallationDate: Installed on 2015-06-29 (394 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 5548
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-77-generic.efi.signed 
root=UUID=7b6f5337-e94f-46cb-8573-476093c584c8 ro plymouth:debug splash quiet 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 079JDM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Inspiron 5548
  dmi.product.version: 

[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume

2016-07-28 Thread Loris Zinsou
I'm affected in the same way as lauricat: wifi reconnects after resuming
from suspend (I have Internet access), however only an unknown ethernet
connection icon is displayed by the network manager applet (while no
ethernet cable is connected to my laptop), and the list of available
wifi networks is absent from the network manager applet menu.

This laptop is a Dell Inspiron 15 2-in-1; model 5568.

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

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1380480/+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 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11

2016-07-28 Thread Tony Espy
** Changed in: network-manager (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  [regression] [OTA-11] Adding new wifi networks (with long passwords)
  never connect at all since OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+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 1607241] Re: gnome-software won't open

2016-07-28 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-software (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-software won't open

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  gnome-software won't open after launch, It doesn't show any errors or 
crashing.
  When I run it using terminal having these errors and not opening it.

  (gnome-software:8467): Gtk-WARNING **: Theme parsing error:
  gtk.css:7690:32: Missing name of pseudo-class

  (gnome-software:8467): Gs-WARNING **: Failed to create permission
  org.freedesktop.packagekit.trigger-offline-update:
  GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action
  org.freedesktop.packagekit.trigger-offline-update is not registered

  (gnome-software:8467): Gs-WARNING **: Failed to create permission
  org.freedesktop.packagekit.trigger-offline-update:
  GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action
  org.freedesktop.packagekit.trigger-offline-update is not registered

  (gnome-software:8467): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (gnome-software:8467): GLib-GObject-CRITICAL **: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jul 28 11:49:30 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1607241/+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 1607287] Re: [OTA12] Google Calendar webapp crashes on start

2016-07-28 Thread Sebastien Bacher
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  [OTA12] Google Calendar webapp crashes on start

Status in Canonical System Image:
  New
Status in webapps-applications package in Ubuntu:
  New

Bug description:
  After updating to OTA12 Google Calendar webapp crashes on start up,
  both in bq E5 and M10

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607287/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

2016-07-28 Thread Christopher M. Penalver
Oliver, thank you for reporting this and helping make Ubuntu better.

1) What release did you upgrade from where this problem wasn't reproducible?
2) In the prior working release, were you using the nvidia proprietary drivers?
3) If you uninstall the nvidia proprietary drivers does this provide a 
WORKAROUND? 

** Tags added: bios-outdated-1.11

** Description changed:

  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.
  
  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases. Sometimes
  ubuntu freezes after lightdm restart and a hard reset has to be
- performed. Another Problem is that if the display goes to sleep or is
- suspended the second monitor won't wake up anymore.
- 
- (Futhermore there are some graphical issues, which might be associated
- with the proprietary driver of the Nvidia)
- 
- Thank you very much for your help.
- 
- Ubuntu 16.04: 4.4.0-31-generic
- xorg:  Installed: 1:7.7+13ubuntu3
+ performed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
-Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
-Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
+  Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
+    Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
+    Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: evdev: Dell Dell 

[Desktop-packages] [Bug 1562431] Re: Huawei E3372 is not switched to modem mode automatically

2016-07-28 Thread Luigi Tarenga
checkout my bug report #1593669 . I found a solution, maybe works for
you.

regards
Luigi

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

Title:
  Huawei E3372 is not switched to modem mode automatically

Status in usb-modeswitch package in Ubuntu:
  Triaged

Bug description:
  This "modem key" worked out of the box for me in ubuntu 15.10.

  However now, in 16.04, the "usb mode switch" is not done automatically
  (both is the modem is plugged at boot or after).

  I suppose it's an udev regression. So there is no kernel problem for
  me.

  (first answered it in #1527914, also maybe related to #1431179)

  WORKAROUND: After plugging in the device (lsusb):
  Bus 002 Device 010: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 
(Mass storage mode)

  Execute at a terminal:
  usb_modeswitch -J -v 0x12d1 -p 0x1f01

  and now the device works as expected and can be selected in network manager. 
As per lsusb:
  Bus 002 Device 011: ID 12d1:14dc Huawei Technologies Co., Ltd.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Mar 27 03:08:34 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  MachineType: LENOVO 20BWS02G00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=3dd4b932-06dd-4c0b-8f63-1ee6b90969ed ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS02G00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BWS02G00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02G00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS02G00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1562431/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-07-28 Thread Robie Basak
@Sean

Thank you for the patch. This looks too big to review to me, although
other sponsors may disagree. So, though I don't usually work in the
desktop area, I disagree with your statement "Regression potential here
seems minimal". This might be why some other sponsors have been
unwilling to touch this. Can I suggest that you bisect the changes to
find the single fix needed to solve the problem, and then submit a
debdiff with just that change? SRU policy says that to minimise
regression risk to users, we should backport a minimal fix where
possible.

This might not apply if there is a bigger picture plan to update the
Intel driver, but I presume there isn't one since this bug has
languished for a while.

HTH.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Confirmed
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Confirmed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [SRU for Ubuntu 16.04]
  Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
  Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1

  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)]
   xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; 
urgency=medium
* Merge from Debian.

   xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium
* New upstream snapshot.
* fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting-
  handle-gen9+.diff: Dropped as the fallback to modesetting will be
  fully handled in the xserver.
* .docs: Include a minimal xorg.conf.

   xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; 
urgency=medium
* Merge from Debian.
* install-dri3info.diff: Install dri3info with the driver, add 
libxcomposite-dev
  to build-depends.

   xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium
* New upstream snapshot. (Closes: #823116)
* fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back
  on another driver when scrn create fails.

  [Regression Potential]
  Regression potential here seems minimal. However, as seen in the above Debian 
changelog, we have a new snapshot which includes several changes since March 25.

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1020756] Re: GtkTreeView keyboard binding are not intituive

2016-07-28 Thread sampablokuper
** Also affects: gnucash (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GtkTreeView keyboard binding are not intituive

Status in GTK+:
  New
Status in gnucash package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Most GUIs, like MacOS X, Microsoft Windows and Qt handle the keyboard bindings
  for its treeviews in the same way: user can easily expand, collapse and move
  into tree nodes using only the arrow keys.

  In Gtk+, however, is quite different. User needs to press "plus" and "minus"
  key to collapse and expand nodes, leaving Right and Left arrows with
  essentially null functionality. Well yeah, that keys allow to move 
horizontally
  into row cells.
  Seeing many of the applications written using Gtk+, there are not many cases
  where user find useful moving horizontally across the row with the keyboard,
  most GtkTreeView that I see are simple and used only to show information.
  So I guess the current GtkTreeView behaviour is crazy, not useful in most
  cases, goes against intuition and against good User Experience.

  I'm really not familiar with Gtk+ programming but, as user, I find this "bug"
  extremely annoying in my day to day.

  So, I make some changes in Gtk+ to enhance (from my point of view) the 
behavior
  of GtkTreeView with the keyboard.

  The attached patch to the 3.4 branch modifies the default GtkTreeView 
behaviour
  with the keyboard, expanding nodes with the right arrow and collapsing it with
  left arrow, selecting parent and child nodes when appropriate:
   - When user press Left on a collapsed node, Gtk+ select the parent node.
   - When user press right on an expanded node, Gtk+ select the first child 
node.
  Users that want to navigate into cells horizontally (as I can see, a non
  frecuent use case) will need to press Ctrl+. Users can still move
  to the parent node with the Backspace key, without collapsing anything.

  I don't know exactly if this behavior change break some expected behavior to
  application programmer, I hope not.

  
  A last question, Why Gtk+ programmers implemented the current GtkTreeView 
behavior
  knowing the big difference with other tested GUIs?

  Best Regards!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1020756/+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 1600576] Re: Screen rolling/rotating horizontally when using specific applications

2016-07-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen rolling/rotating horizontally when using specific applications

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

Bug description:
  Sometimes the following graphics glitch is triggered where the screen starts 
moving/rotating rapidly. See https://i.imgur.com/u6j5auo.gif (gedit on LXDE).
  This is triggered semi-randomly while using specific apps like Kate, gEdit, 
gVim, leafpad, embedded console inside Dolphin, KDevelop and rarely with 
Konsole.
  Also triggered for a few split-seconds when I move the mouse when in 
fullscreen mode in VLC but stabilises quickly. However, everything is stable 
when I just use Chrome or Firefox, LXTerminal, Clementine and Code::Blocks, 
even for hours.

  Whenever this is triggered, it can sometimes be fixed when I switch to 
desktop or Chrome or a different app while closing the trigger-er app while 
other times, rebooting is the only way. Sometimes (rarely) the screen becomes 
completely black after a while, with key-presses and mouse movements revealing 
the screen for split-seconds which allows me to properly shutdown/restart the 
laptop.
  I've tried to Google the problem with no results, I'm not even sure what to 
search for.

  And I apologize if this isn't the correct place to report. I've
  already tried a couple of places with no replies or help whatsoever.

  Some system details:
  OS: Lubuntu 16.04
  Kernel (uname -r): 4.4.0-28-generic
  Laptop: Lenovo G50-80 with Intel 5500 Integrated graphics chip (Broadwell-U 
Integrated Graphics, inside Core i3-5005U)

  Relevant lspci block:

  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Lenovo Broadwell-U Integrated Graphics
  Flags: bus master, fast devsel, latency 0, IRQ 48
  Memory at c000 (64-bit, non-prefetchable) [size=16M]
  Memory at b000 (64-bit, prefetchable) [size=256M]
  I/O ports at 4000 [size=64]
  Expansion ROM at  [disabled]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915
  Resolution from xrandr --verbose:

  1366x768 (0x47) 72.330MHz -HSync -VSync *current +preferred
  h: width  1366 start 1414 end 1446 total 1526 skew0 clock  
47.40KHz
  v: height  768 start  770 end  775 total  790   clock  60.00Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jul 10 15:06:25 2016
  InstallationDate: Installed on 2016-05-28 (43 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-intel
  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-intel/+bug/1600576/+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 1606959] Re: DPI setting is not correctly calculated on Ubuntu GNOME

2016-07-28 Thread Reuben Thomas
Wow, fast fix, thanks Chad!

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

Title:
  DPI setting is not correctly calculated on Ubuntu GNOME

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser,
  unlike any other app I've found, gets the wrong DPI, and starts up
  unscaled.

  On investigation, this appears to be because of a bug in
  desktop_screen_x11.cc (I checked this only in the sources for the
  currently shipped version of Chromium, against which I'm reporting
  this bug).

  The hardware is *correctly* queried via the GTK2 back-end in
  gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of
  desktop_screen_x11.cc.

  However, this is then unconditionally overridden lower down. In line
  356, density_indicator is set to 8 (this corresponds to a scale factor
  of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to
  read a value from the gsettings key /com/ubuntu/user-interface/scale-
  factor.

  Aside: Under Unity, I understand that this setting is populated with
  information about the connected displays (I did try to find where this
  happens, but I can only find references to the setting in unity-
  control-center, while presumably it must also be set whenever a new
  display is plugged or unplugged); under GNOME it seems not to be.

  The problem is that when the gsettings key /com/ubuntu/user-interface
  /scale-factor is empty, or absent, the default value of
  density_indicator is still used, overriding the hardware-provided
  value. The only circumstances in which the hardware-provided value
  will be used are when the key for the relevant display is explicitly
  set to 0.

  This means that scaling won't work on a GNOME system, which is ironic
  considering that the correct information has already been obtained
  from Gtk!

  As far as I can see, the fix is to change the setting of 8 in line 356
  to 0, so that if no gsettings value can be obtained, then the
  hardware-supplied value, which has already been calculated, is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM=
   dpms: On
   modes: 2560x1600
   enabled: enabled
   status: connected
  Date: Wed Jul 27 15:14:57 2016
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  Env:
   'None'
   '/home/rrt/.local/lib/x86_64-linux-gnu'
  InstallationDate: Installed on 2015-12-28 (212 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Load-Avg-1min: 0.49
  Load-Processes-Running-Percent:   0.1%
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-07-25 (2 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec 

[Desktop-packages] [Bug 1589550] Re: Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT

2016-07-28 Thread Daniel van Vugt
Looking good since around the time bug 1576260 got fixed.

** Changed in: lightdm
   Status: New => Incomplete

** Changed in: mir
   Status: New => Incomplete

** Changed in: lightdm (Ubuntu)
   Status: Confirmed => 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/1589550

Title:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT

Status in Light Display Manager:
  Incomplete
Status in Mir:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT.

  The result is a black screen, as Unity8 is running but the system
  defaults to the wrong VT so it's not visible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1589550/+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 1607337] [NEW] unespectted restart

2016-07-28 Thread Vanja Mihalić
Public bug reported:

i don't know. Computer periodicali restart with no reason.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jul 28 13:47:26 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] MSI Radeon HD 4850 512MB 
GDDR3 [1002:0502]
InstallationDate: Installed on 2016-07-13 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: BIOSTAR Group TP43D2-A7
ProcEnviron:
 LANGUAGE=hr
 PATH=(custom, no user)
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=6d023266-42cb-4c7f-8668-732075507141 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: None
dmi.board.name: TP43D2-A7
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd07/29/2008:svnBIOSTARGroup:pnTP43D2-A7:pvr6.0:rvnBIOSTARGroup:rnTP43D2-A7:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: TP43D2-A7
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Jul 28 13:44:16 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt USB Optical Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  unespectted restart

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't know. Computer periodicali restart with no reason.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 28 13:47:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] MSI Radeon HD 4850 512MB 
GDDR3 [1002:0502]
  InstallationDate: Installed on 2016-07-13 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: BIOSTAR Group TP43D2-A7
  ProcEnviron:
   LANGUAGE=hr
   PATH=(custom, no user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=6d023266-42cb-4c7f-8668-732075507141 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: None
  

[Desktop-packages] [Bug 1589975] Re: Ubuntu 16.04 has Networking problems

2016-07-28 Thread Stephen Rynas
Issue Still persists, despite the updates. 
I will do a totally "fresh" install of 16.04.1 in the near future.

I have installed ("fresh") 16.04 on another computer and it does not
have this networking problem.  Furthermore, the lack of others
reporting/having this problem points to it being specific to my one
computer.

Thanks for responding.

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589975/+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 1437862] Re: pg_upgradecluster fails: "could not get cluster locales"

2016-07-28 Thread Andrew B
Hi,

In my instance this error originated deep down in the call stack in
get_cluster_port in /usr/share/Perl5/Pgcommon.pm when attempting to
upgrade from 9.3 to 9.5

In my postgresql.conf for the old 9.3 cluster I had the port line
commented-out per the default configuration file:

#port = 5432

This worked fine in production since Postgres defaults to that port
number when not defined.  However its absence was causing
get_cluster_port to fail and this was propagating up the call stack to
get_encoding in pg_upgradecluster.

I decommented the port line:

port = 5432

and reran pg_upgradecluster with success.

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

Title:
  pg_upgradecluster fails: "could not get cluster locales"

Status in postgresql-common package in Ubuntu:
  Confirmed

Bug description:
  We upgrade a 12.04 LTS to 14.04 LTS and use the pg_upgradecluster
  command(usage as described in /usr/share/doc/README.Debian.gz). But we
  get a failure an no upgrade is done:

  pg_dropcluster 9.3 main --stop

  pg_upgradecluster 9.1 main
   psql: FATAL:  the database system is shutting down
   psql: FATAL:  the database system is shutting down
   Use of uninitialized value $out in pattern match (m//) at 
/usr/share/postgresql-common/PgCommon.pm line 883.
   psql: FATAL:  the database system is shutting down
   Use of uninitialized value $out in pattern match (m//) at 
/usr/share/postgresql-common/PgCommon.pm line 889.
   Use of uninitialized value $ctype in scalar chomp at 
/usr/share/postgresql-common/PgCommon.pm line 892.
   Use of uninitialized value $collate in scalar chomp at 
/usr/share/postgresql-common/PgCommon.pm line 893.
   Error: could not get cluster localesapt-get install postgresql-9.3

  apt-get install postgresql-9.3 postgresql-common postgresql-client-9.3
  postgresql-contrib-9.3 said, that all packages are in their newest
  version and

  dpkg said:
  iU  postgresql  9.3+154  all  
object-relational SQL database (supported version)
  ii  postgresql-9.1  9.1.15-0ubuntu0.12.04
amd64object-relational SQL database, version 9.1 server
  iU  postgresql-9.3  9.3.6-0ubuntu0.14.04 
amd64object-relational SQL database, version 9.3 server
  iU  postgresql-client   9.3+154  all  
front-end programs for PostgreSQL (supported version)
  ii  postgresql-client-9.1   9.1.15-0ubuntu0.12.04
amd64front-end programs for PostgreSQL 9.1
  iF  postgresql-client-9.3   9.3.6-0ubuntu0.14.04 
amd64front-end programs for PostgreSQL 9.3
  ii  postgresql-client-common154  all  
manager for multiple PostgreSQL client versions
  ii  postgresql-common   154  all  
PostgreSQL database-cluster manager
  iU  postgresql-contrib  9.3+154  all  
additional facilities for PostgreSQL (supported version)
  ii  postgresql-contrib-9.1  9.1.15-0ubuntu0.12.04
amd64additional facilities for PostgreSQL
  iU  postgresql-contrib-9.3  9.3.6-0ubuntu0.14.04 
amd64additional facilities for PostgreSQL
  ii  postgresql-doc  9.3+154  all  
documentation for the PostgreSQL database management system
  ii  postgresql-doc-9.1  9.1.15-0ubuntu0.12.04all  
documentation for the PostgreSQL database management system
  ii  postgresql-doc-9.3  9.3.6-0ubuntu0.14.04 all  
documentation for the PostgreSQL database management system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1437862/+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 1589975] Re: Ubuntu 16.04 has Networking problems

2016-07-28 Thread Paul White
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589975/+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 1589975] [NEW] Ubuntu 16.04 has Networking problems

2016-07-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does not
properly "see" the home network (LAN). Additionally, my printer which is
also attached to the LAN does not work correctly.

These are erratic issues, meaning that they don't appear all the time.
Further, no crash reports are generated either.

To explain further. The computer running 16.04 will frequently NOT show
up on the "network" screen. When I go over to the computer running
Ubuntu 14.04 it also does not show the computer running 16.04 as being
on the LAN.

In terms of printing, the printer queue shows the print job as "held".
When you try to release the print job it asks if the printer is
connected and then goes back to "holding" the print job.

These actions seem to imply that networking is not working correctly
with Ubuntu 16.04.

Please see the comment by Jerrylamos here:
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Tue Jun  7 08:41:00 2016
InstallationDate: Installed on 2016-04-13 (54 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
VarLogDistupgradeTermlog:

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
Ubuntu 16.04 has Networking problems
https://bugs.launchpad.net/bugs/1589975
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

-- 
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 1605291] Re: please merge llvm-toolchain-3.8 from Debian

2016-07-28 Thread Launchpad Bug Tracker
This bug was fixed in the package llvm-toolchain-3.8 - 1:3.8.1-4ubuntu1

---
llvm-toolchain-3.8 (1:3.8.1-4ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable (LP: #1605291).  Remaining changes:
- Add support for gcc's attribute abi_tag (needed for compatibility with
  GCC 5's libstdc++); taken from the trunk.
- Disable lldb on s390x.
- Remove the build tree before calling dh_strip; at least the amd64 buildd
  runs out of diskspace at this step.
- rules: Allow LLVM tests to fail on i386, we know dropping AVX512 breaks
  them.
- drop-avx512-from-skylake.diff: Don't enable AVX512 on Skylake, as it's
  a server cpu feature and breaks llvmpipe on workstations.

llvm-toolchain-3.8 (1:3.8.1-4) unstable; urgency=medium

  * Fix the FTBFS under mips/mipsel? (enable the link against atomic)
(Closes: #820537)
  * Bring back llvm-3.8-tools to life
  * ship clang-tblgen & yaml-bench as part of the libclang-common-X.Y-dev
package

 -- Gianfranco Costamagna   Thu, 21 Jul 2016
16:59:53 +0200

** Changed in: llvm-toolchain-3.8 (Ubuntu)
   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.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1605291

Title:
  please merge llvm-toolchain-3.8 from Debian

Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released

Bug description:
  debdiff attached and build ongoing @ ppa:costamagnagianfranco
  /locutusofborg-ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1605291/+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 1292398] Re: Second screen position isn't saved from one session to another

2016-07-28 Thread Donjan Rodic
Not sure if this is equivalent, as I run unity-settings-daemon instead
of gnome-settings-daemon (with the Compiz Unity-plugin turned off and
gnome-panel instead), but it seems similar enough.

Just upgraded from 14.04 to 16.04.1.

I drop my laptop on a dock with two vertically oriented (rotated to
portrait) monitors. This was working fine before, now it lights them up
without the rotation. Rotating them manually via System Settings ->
Displays, undocking and docking again reverts to the wrong (landscape)
orientation.

The ~/.config/monitors.xml looks fine but seems to be ignored.
Reloading the settings with

  killall unity-settings-daemon

gives me the correct orientation, which is read from the monitor.xml
(editing the file by hand and killing u-s-d accepts whatever changes I
make), it just doesn't get triggered on docking changes.

That's the workaround for now: kill u-s-d every time I dock to that workplace, 
which may help with g-s-d too.
It would be nice for patchlvl 1 LTS upgrades to not break such basic stuff.

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in gnome-settings-daemon:
  Unknown
Status in gnome-shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1606234] Re: Actions menu is displaced on high-dpi

2016-07-28 Thread Launchpad Bug Tracker
This bug was fixed in the package bamf -
0.5.3~bzr0+16.10.20160726.1-0ubuntu1

---
bamf (0.5.3~bzr0+16.10.20160726.1-0ubuntu1) yakkety; urgency=medium

  [ Andrea Azzarone ]
  * Unscale x/y coordinates returned by top_window_action_menu. (LP:
#1606234)

  [ Martin Pitt ]
  * Add support for starting bamf through user systemd units

 -- Marco Trevisan (Treviño)   Tue, 26 Jul 2016 09:08:41
+

** Changed in: bamf (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Actions menu is displaced on high-dpi

Status in bamf package in Ubuntu:
  Fix Released

Bug description:
  1. Scale to 2.0 using control center
  2. Open a window (e.g gedit)
  3. Open action menu using alt+space

  Expected
  The action menu is placed in the top left corner of the window

  Actual
  The action menu is displaced as in attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1606234/+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 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen

2016-07-28 Thread lendis
Confirm! In 16.04 it gets more annoying. Anybody can a see user's
desktop for second if just try to switch language!

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

Title:
  Keyboard shortcut for changing keyboard layout does not work on lock
  and login screen

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Shortcut for changing keyboard layout does not work on lock screen (to
  change keyboard layout for entering password).

  - Switch to some non-english layout (otherwise lock screen will not have 
layout indicator at all)
  - Lock the screen
  - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it 
will not change layout
  - Clicking layout indicator near password entry box works
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  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: Fri Oct 25 11:01:10 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-23 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548/+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 1528085] Re: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

2016-07-28 Thread LordOfRuin
I am no guru, however I did notice something which may help those who
are gurus:

I am having video tearing issues with nvidia gtx960m on an MSi Ge72 2qd
(side issue, but relevant).

1 -I installed the nvidia-364 drivers to test in current latest 3.x
kernel, also intending to test under 4.5.2 (under 14-04 trusty
installation).

2 - Rebooted after install of nvidia-364 drivers (found video tearing
still present), so...

3 - Ran dpkg -i *.deb (as root) from directory containing 4.5.2 amd64
.debs and got the error that this bugtrack is about.

4 - I had previously done the same (i.e. built and run 4.5.2) on another
unit runing 14.04 Trusty WITHOUT nvidia gpu/drivers in it without error
messages, so...

5 - Uninstalled nvidia drivers as root (apt-get remove nvidia* && apt-
get autoremove THEN apt-get purge nvidia*) - belt and braces I know but
purge does pick up 4 further items to remove.

6 - Ran dpkg -i *.deb (as root) from directory containing 4.5.2 amd64
.debs and GOT NO ERROR.

I have zero idea whether this is directly related to nvidia or to
proprietary video drivers in general - however this might help the devs
get on the right path to fixing it.

DEVS: feel free to contact me if you need any further info about my
system/setup

Cheers,

LOR

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

Title:
  bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 15.10
  Release:15.10

  Trying to update the kernal via package manager, expected it to
  install the kernal and process of dkms

  failed on dkms

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: bbswitch-dkms 0.7-2ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 4.2.0-22-generic
  Date: Mon Dec 21 02:48:41 2015
  DuplicateSignature: dkms:bbswitch-dkms:0.7-2ubuntu1:gcc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-12-17 (3 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageVersion: 0.7-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: bbswitch
  Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1528085/+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 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen

2016-07-28 Thread Semenov Pasha
+1 16.04.1 LTS 64 bit

Same as @chobit said.

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

Title:
  Keyboard shortcut for changing keyboard layout does not work on lock
  and login screen

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Shortcut for changing keyboard layout does not work on lock screen (to
  change keyboard layout for entering password).

  - Switch to some non-english layout (otherwise lock screen will not have 
layout indicator at all)
  - Lock the screen
  - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it 
will not change layout
  - Clicking layout indicator near password entry box works
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  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: Fri Oct 25 11:01:10 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-23 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548/+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 1607238] Re: In-browser video never plays in Xmir

2016-07-28 Thread Daniel van Vugt
** Summary changed:

- In-browser video never plays
+ In-browser video never plays in Xmir

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

Title:
  In-browser video never plays in Xmir

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  In-browser video never plays when using Chrome or Chromium under Xmir

  Surprisingly it also never plays even with Xmir -sw

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1607238/+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 1607287] [NEW] [OTA12] Google Calendar webapp crashes on start

2016-07-28 Thread Joan CiberSheep
Public bug reported:

After updating to OTA12 Google Calendar webapp crashes on start up, both
in bq E5 and M10

** Affects: webapps-applications (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [OTA12] Google Calendar webapp crashes on start

Status in webapps-applications package in Ubuntu:
  New

Bug description:
  After updating to OTA12 Google Calendar webapp crashes on start up,
  both in bq E5 and M10

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