date:20160629

This bug was fixed in the package libreoffice - 1:5.0.6-0ubuntu1

---
libreoffice (1:5.0.6-0ubuntu1) wily-security; urgency=medium

  * SECURITY UPDATE: Denial of service and possible arbitrary code execution
via a crafted RTF file
- CVE-2016-4324
  * new upstream release
  * fall back to SYSTEM_GCC_VERSION, when SYSTEM_GCJ_VERSION is empty
  * substitute xfonts-mathml with fonts-stix (lp: #1487148)
  * cherry-pick from Debian:
- readd conflicts against openoffice-unbundled to libreoffice-common.
  openoffice*-debian-menus contains /usr/bin/soffice
  * fix gug language description (thanks Rene)
  * add build version for "About LibreOffice"
  * create profile defaulting to human style on unity (lp: #1508177)
  * reenable Ubuntu palette
  * handle integral translations
  * adjust kde integration for upstream cb37698884c6f7af97c5fa9a0404a5893aa73c9d

 -- Bjoern Michaelsen   Fri, 24 Jun
2016 20:45:46 +0200

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4324

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

Title:
  [MIR] fonts-stix -- to replace xfonts-mathml

Status in fonts-stix package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in fonts-stix source package in Wily:
  New
Status in libreoffice source package in Wily:
  Fix Released

Bug description:
  [Availability]
  already in xenial

  
  [Rationale]
  The libreoffice-common package currently recommends xfonts-mathml, which was 
removed from Debian in 2014 with the rationale that it is superseded by 
fonts-stix (and that it has a license problem).  Please replace it with 
fonts-stix.

  [Security]
  no executable code

  [Quality assurance]
  no executable code

  [Dependencies]
  no further deps needed: see 
http://people.canonical.com/~ubuntu-archive/component-mismatches.txt

  [Standards compliance]
  trivial package, maintained by Debian

  [Maintenance]
  no executable code, maintained by Debian, stable/low frequency updates

  [Background information] 
  Since xfonts-mathml is only a Recommends: rather than Depends:, I'm going to 
go ahead and remove xfonts-mathml from wily.  If for some reason fonts-stix is 
not a suitable replacement and xfonts-mathml is still needed, please feel free 
to reupload it to the archive and close this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-stix/+bug/1487148/+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 1508177] Re: [SRU] Starting LibreOffice with an empty profile from the ISO creates a profile selecting galaxy, not human as theme

This bug was fixed in the package libreoffice - 1:5.0.6-0ubuntu1

---
libreoffice (1:5.0.6-0ubuntu1) wily-security; urgency=medium

  * SECURITY UPDATE: Denial of service and possible arbitrary code execution
via a crafted RTF file
- CVE-2016-4324
  * new upstream release
  * fall back to SYSTEM_GCC_VERSION, when SYSTEM_GCJ_VERSION is empty
  * substitute xfonts-mathml with fonts-stix (lp: #1487148)
  * cherry-pick from Debian:
- readd conflicts against openoffice-unbundled to libreoffice-common.
  openoffice*-debian-menus contains /usr/bin/soffice
  * fix gug language description (thanks Rene)
  * add build version for "About LibreOffice"
  * create profile defaulting to human style on unity (lp: #1508177)
  * reenable Ubuntu palette
  * handle integral translations
  * adjust kde integration for upstream cb37698884c6f7af97c5fa9a0404a5893aa73c9d

 -- Bjoern Michaelsen   Fri, 24 Jun
2016 20:45:46 +0200

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4324

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

Title:
  [SRU] Starting LibreOffice with an empty profile from the ISO creates
  a profile selecting galaxy, not human as theme

Status in Release Notes for Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Severely reduces the initial impression of LibreOffice on a fresh install 
from ISO.

  [Test Case]
  STEPS:
  1. Install the latest daily cd image
  2. Open libreoffice writer check the theme and close it

  EXPECTED:
  I expect the theme to always be human unless I explicitly change it

  ACTUAL:
  The default theme on a new install is galaxy, though human is installed.

  (Alternatively: Test what theme LibreOffice selects when
  ~/.config/libreoffice is rm-rfed and there are libreoffice-style-human
  and libreoffice-style-galaxy installed)

  [Regression Potential]
  Very low. No fallout expected from the change back to a better default theme: 
Trivial low risk two-line fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508177/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Ren

Sorry Anupam : I did not want to pollute this complex bug-id
but I wished to point out that the problem may be an 
interaction between several applications that use the system
sound notifications. I believe it...
I decided to create notifications at the same time for
several applications (sms/calendar/and clock alarm)
at 19:30 every day...
Soon, the sound becomes mute after first notification...
or after a while...

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1576726] Re: [SRU] network-manager 1.2.0

2016-06-29 Thread Mathew Hodson

network-manager-pptp (1.2.0-1) unstable; urgency=medium

  * New upstream release.

 -- Michael Biebl   Sat, 23 Apr 2016 00:44:17 +0200

** Tags added: upgrade-software-version

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

** No longer affects: freeplane (Ubuntu)

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

** Changed in: network-manager-pptp (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  Fix Released
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Fix Released
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1597314] Re: Support for apps which do not automatically connect to slots

2016-06-29 Thread Robert Ancell

Is this only an action that makes sense when the app is installed or at
any time? My guess is we should have a "connections" panel of some sort
that allows these to be toggled at a later date and perhaps an Android
style "this app is requesting these permissions" dialog when installing
(with the option of disabling them at that point).

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

Title:
  Support for apps which do not automatically connect to slots

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  With the addition of new interfaces there are some plugs which do not
  automatically connect and require action from the user in order to be
  connecte.

  As an example, VLC doesn't not automatically connect to the camera
  interface, but users may want to enable this, or maybe they dont.

  Some design considerations:

   * Do we want to ask users to toggle on/off connections they do/do not
  want.  i.e. a list of toggle buttons (what effect would this have on
  the application, would it fail gracefully or just not work (in which
  case the user could be made aware that it won't work without the
  permissions).

  vs

   * Do we want just a single Yes/No question where it's all the
  connections or none.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1597314/+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 1597314] Re: Support for apps which do not automatically connect to slots

2016-06-29 Thread Robert Ancell

Prior art in the phone - the modifiy existing permissions is in the
system settings.

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

Title:
  Support for apps which do not automatically connect to slots

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  With the addition of new interfaces there are some plugs which do not
  automatically connect and require action from the user in order to be
  connecte.

  As an example, VLC doesn't not automatically connect to the camera
  interface, but users may want to enable this, or maybe they dont.

  Some design considerations:

   * Do we want to ask users to toggle on/off connections they do/do not
  want.  i.e. a list of toggle buttons (what effect would this have on
  the application, would it fail gracefully or just not work (in which
  case the user could be made aware that it won't work without the
  permissions).

  vs

   * Do we want just a single Yes/No question where it's all the
  connections or none.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1597314/+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 1597431] Re: lightdm could run the X server without root privileges

2016-06-29 Thread Robert Ancell

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

** This bug has been marked a duplicate of bug 1292324
   Support non-root X

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

Title:
  lightdm could run the X server without root privileges

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  there is this old document:

https://wiki.ubuntu.com/X/Rootless

  that states the goal of the running the X server without root
  privileges.

  With kernel DRM this goal is now attainable.  gdm already implements
  this and it works on Ubuntu.  Here is what I have on another Ubuntu
  system where I use gdm:

  root  2588  0.0  0.0 285652  5256 ?Ssl  Jun25   0:00 
/usr/sbin/gdm3
  root  2593  0.0  0.0 267344  6448 ?Sl   Jun25   0:00 
gdm-session-worker 
  bonnaudl  2609  0.0  0.0  62320  4464 tty7 Ssl+ Jun25   0:00 
/usr/lib/gdm3/gdm-x-session 
  bonnaudl  2611  0.7  1.0 459736 165292 tty7Sl+  Jun25  43:40 
/usr/lib/xorg/Xorg vt7 -displayfd 3 

  So would it be possible to implement a similar thing in lightdm ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 29 17:58:21 2016
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1597431/+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 1510009] Re: Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK interaction

2016-06-29 Thread Mathew Hodson

** Bug watch removed: Debian Bug tracker #798131
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798131

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

Title:
  Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK
  interaction

Status in JOSM:
  Unknown
Status in java-atk-wrapper package in Ubuntu:
  Fix Released
Status in java-atk-wrapper package in Debian:
  Fix Released

Bug description:
  Since upgrading to Ubuntu 15.10 from Ubuntu 15.04, the various GUI
  applications that I run, including Netbeans and Minecraft have been
  suffering from dead/waitlocks which prevent them from operating
  properly. Since I have reproduced this issue these two completely
  different codebases, I am moving the bug further upstream.

  The original Netbeans bug report can be viewed here: 
https://netbeans.org/bugzilla/show_bug.cgi?id=256124
  Essentially, during routine interaction and calling of various AWT methods, 
somewhere between 8u45 (15.04) and 8u66 (15.10), something broke causing the 
application to hang intermittently when these methods are called.

  Some sample jstack traces are attached, the issue should be fairly
  obvious to spot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1510009/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2016-06-29 Thread zanonmark

Christopher, thanks for your time.

Please disregard comment #8, as I was just making a comparison between
two different machines - but probably that only added confusion.

Now, about the machine I reported the bug on:
* 12.04.0, 12.04.1, 12.04.2, 12.04.4: X does not start after boot, not even by 
'startx' (I attach /var/log/Xorg.0.log);
* 12.04.3 halts right after boot with a kernel panic ("Kernel panic - not 
syncing - Attempted to kill init!").

So the first distribution running X is effectively 12.04.5, with the
kernel reported above.

Thanks,
MZ

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+attachment/4692477/+files/Xorg.0.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/1574667

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell 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: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1596207] Re: Sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

2016-06-29 Thread Michael Terry

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

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

Title:
  Sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

Status in gucharmap package in Ubuntu:
  In Progress

Bug description:
  Please sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian, remaining Ubuntu changes:
* debian/control:
* debian/rules:
* debian/gir1.2-gucharmap-2.90.install:
* debian/libgucharmap-2-90-7.install:
* debian/libgucharmap-2-90-dev.install:
  - Multi-arch the package

  Changelog entries since current yakkety version 1:8.0.1-1ubuntu1:

  gucharmap (1:9.0.0-1) unstable; urgency=medium

* New upstream release.
* Bump Build-Depends on unicode-data accordingly.
* Refresh debian/patches/unicode-source-generation.patch.
* Instead of patching configure.ac, set PROG_UNZIP in debian/rules.
* Convert from cdbs to dh.
* Bump debhelper compatibility level to 9.
* Convert to multiarch. (Closes: #812955)

   -- Michael Biebl   Sat, 25 Jun 2016 03:43:46 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1596207/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

2016-06-29 Thread Brian Murray

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
  0: invalid start byte" when removing nvidia-current package

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Triaged

Bug description:
  $sudo apt-get remove nvidia-current
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'nvidia-current' is not installed, so not removed
  The following package was automatically installed and is no longer required:
linux-image-generic
  Use 'apt-get autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up nvidia-331 (331.38-0ubuntu7) ...
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 65, in 
  operation_status = main(options)
File "/usr/bin/quirks-handler", line 44, in main
  quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, 
path=quirks_path)
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in 
__init__
  self._system_info = self.get_system_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in 
get_system_info
  return quirk_info.get_dmi_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in 
get_dmi_info
  'class', 'dmi', 'id', item)).read().strip()
File "/usr/lib/python3.4/codecs.py", line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  dpkg: error processing package nvidia-331 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nvidia-331
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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 1510009] Re: Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK interaction

2016-06-29 Thread Mathew Hodson

** Package changed: openjdk-8 (Debian) => java-atk-wrapper (Debian)

** Package changed: openjdk-8 (Ubuntu) => java-atk-wrapper (Ubuntu)

** Changed in: java-atk-wrapper (Ubuntu)
   Importance: Undecided => High

** Bug watch removed: Debian Bug tracker #797595
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797595

** Bug watch removed: Iced Tea Bugzilla #857
   http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=857

** Bug watch removed: Debian Bug tracker #705511
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705511

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

Title:
  Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK
  interaction

Status in JOSM:
  Unknown
Status in java-atk-wrapper package in Ubuntu:
  Fix Released
Status in java-atk-wrapper package in Debian:
  Fix Released

Bug description:
  Since upgrading to Ubuntu 15.10 from Ubuntu 15.04, the various GUI
  applications that I run, including Netbeans and Minecraft have been
  suffering from dead/waitlocks which prevent them from operating
  properly. Since I have reproduced this issue these two completely
  different codebases, I am moving the bug further upstream.

  The original Netbeans bug report can be viewed here: 
https://netbeans.org/bugzilla/show_bug.cgi?id=256124
  Essentially, during routine interaction and calling of various AWT methods, 
somewhere between 8u45 (15.04) and 8u66 (15.10), something broke causing the 
application to hang intermittently when these methods are called.

  Some sample jstack traces are attached, the issue should be fairly
  obvious to spot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1510009/+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 1510009] [NEW] Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK interaction

You have been subscribed to a public bug:

Since upgrading to Ubuntu 15.10 from Ubuntu 15.04, the various GUI
applications that I run, including Netbeans and Minecraft have been
suffering from dead/waitlocks which prevent them from operating
properly. Since I have reproduced this issue these two completely
different codebases, I am moving the bug further upstream.

The original Netbeans bug report can be viewed here: 
https://netbeans.org/bugzilla/show_bug.cgi?id=256124
Essentially, during routine interaction and calling of various AWT methods, 
somewhere between 8u45 (15.04) and 8u66 (15.10), something broke causing the 
application to hang intermittently when these methods are called.

Some sample jstack traces are attached, the issue should be fairly
obvious to spot.

** Affects: josm
 Importance: Critical
 Status: Unknown

** Affects: java-atk-wrapper (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: java-atk-wrapper (Debian)
 Importance: Unknown
 Status: Fix Released

-- 
Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK interaction
https://bugs.launchpad.net/bugs/1510009
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to java-atk-wrapper 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 1593805] Re: libsignon-glib fail to authenticate account

2016-06-29 Thread Pat McGowan

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

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

Title:
  libsignon-glib fail to authenticate account

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in webapps-sprint:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress

Bug description:
  While using syncevolution to sync multiple calendars, we noticed that
  some accounts are failing to authenticate.

  The error returned by 'libsignon-glib' shows the dbus process as
  service name, what is different from the app requested.

  Check syslog attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593805/+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 1597389] Re: Please fix probleam

2016-06-29 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  Please fix probleam

Status in xorg package in Ubuntu:
  New

Bug description:
  Resolution do not set 1024x900.

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jun 29 20:52:15 2016
  InstallationDate: Installed on 2016-06-10 (19 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1597389/+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 1597472] Re: keychain password prompt prevents screen lock

2016-06-29 Thread Seth Arnold

** Information type changed from Private Security to Public Security

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

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

Title:
  keychain password prompt prevents screen lock

Status in seahorse package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I have a standard ubuntu installation with deja-dup running daily and a 
screen lock.
  deja-dup saves to a SMB share whose password is saved in the seahorse 
keychain.

  When I boot my system and log in, and just leave it running, after
  some time deja-dup starts backing up and causes seahorse to prompt for
  my keychain password. This prompt prevents the screen from locking
  automatically. When I enter my password, the screen is locked at once.

  In Ubuntu 14.04, this effect was the same - but sometimes the keychain
  password prompt would even overlay the already locked screen.  I have
  not seen this in 16.04.

  I think this is a security vulnerability since this makes the
  automatic screen lock unreliable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: seahorse 3.18.0-2ubuntu1
  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: Unity
  Date: Wed Jun 29 20:20:28 2016
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: seahorse
  UpgradeStatus: Upgraded to xenial on 2016-06-09 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1597472/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Jim Hodapp

@Anupam: no worries, refer to Pat's comment in #53. We're pretty
confident we've tracked down the source of the problem and how to fix
it.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3

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

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  when gcc and g++ are set to v4.8 instead of default v5.3

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

Bug description:
  after a routine system update, Linux kernel was upgraded to
  4.4.0-24-generic. Since then, the nvidia graphic drivers simply
  refuses to build:

  
  > Building initial module for 4.4.0-24-generic
  > Error! Bad return status for module build on kernel: 4.4.0-24-generic 
(x86_64)
  > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-24-generic
  Date: Sun Jun 12 19:45:40 2016
  DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-10-31 (225 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591785/+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 1597471] ProcEnviron.txt

2016-06-29 Thread Tankypon

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1597471/+attachment/4692458/+files/ProcEnviron.txt

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

Title:
  No auto login in Ubuntu Xenial

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Hi,

  Since I installed the new version of Ubuntu, it is not auto login anymore. 
Now it's annoying me at every boot of Ubuntu, so I report the problem here. I 
used Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
  I put two logs produced by lightdm, hope it can help someone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (68 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: unity-greeter 16.04.2-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages xenial
  Uname: Linux 4.6.2-040602-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1597471/+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 1597471] Re: No auto login in Ubuntu Xenial

2016-06-29 Thread Tankypon

apport information

** Tags added: apport-collected third-party-packages xenial

** Description changed:

  Hi,
  
  Since I installed the new version of Ubuntu, it is not auto login anymore. 
Now it's annoying me at every boot of Ubuntu, so I report the problem here. I 
used Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
  I put two logs produced by lightdm, hope it can help someone.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-21 (68 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: unity-greeter 16.04.2-0ubuntu1
+ PackageArchitecture: amd64
+ Tags: third-party-packages xenial
+ Uname: Linux 4.6.2-040602-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1597471/+attachment/4692456/+files/Dependencies.txt

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

Title:
  No auto login in Ubuntu Xenial

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Hi,

  Since I installed the new version of Ubuntu, it is not auto login anymore. 
Now it's annoying me at every boot of Ubuntu, so I report the problem here. I 
used Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
  I put two logs produced by lightdm, hope it can help someone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (68 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: unity-greeter 16.04.2-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages xenial
  Uname: Linux 4.6.2-040602-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1597471/+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 1597471] JournalErrors.txt

2016-06-29 Thread Tankypon

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1597471/+attachment/4692457/+files/JournalErrors.txt

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

Title:
  No auto login in Ubuntu Xenial

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Hi,

  Since I installed the new version of Ubuntu, it is not auto login anymore. 
Now it's annoying me at every boot of Ubuntu, so I report the problem here. I 
used Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
  I put two logs produced by lightdm, hope it can help someone.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-21 (68 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: unity-greeter 16.04.2-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages xenial
  Uname: Linux 4.6.2-040602-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1597471/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Anupam

@Jim I tried that, but didn't seem helpful. It only changed speaker
volume.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1597471] Re: No auto login in Ubuntu Xenial

2016-06-29 Thread Amr Ibrahim

Please run this in terminal to collect more info about the bug:

apport-collect 1597471

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

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

Title:
  No auto login in Ubuntu Xenial

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Hi,

  Since I installed the new version of Ubuntu, it is not auto login anymore. 
Now it's annoying me at every boot of Ubuntu, so I report the problem here. I 
used Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
  I put two logs produced by lightdm, hope it can help someone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1597471/+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 1443052] Re: User accounts login history showing incorrect history

** Description changed:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which is
  meant to show the login history for that account), it will show you when
  you last logged in as "Session Started", but it will show that you
  "Session Ended" just before you login the next time.
  
  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I logged
  out, and then this morning I logged into my account somewhere around
  11:20, it will show this:
  
  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started
  
  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.
  
  I have attached a screenshot to show my example as I see it in the
  History GUI.
  
- I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
- Ubuntu GNOME 15.10 with GNOME 3.18.
+ I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
+ Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
+ 3.20.

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1597471] [NEW] No auto login in Ubuntu Xenial

You have been subscribed to a public bug:

Hi,

Since I installed the new version of Ubuntu, it is not auto login anymore. Now 
it's annoying me at every boot of Ubuntu, so I report the problem here. I used 
Ubuntu 16.04 on my laptop with a Nvidia GPU with the proprietary driver.
I put two logs produced by lightdm, hope it can help someone.

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

-- 
No auto login in Ubuntu Xenial
https://bugs.launchpad.net/bugs/1597471
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity-greeter 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 1443052] Re: User accounts login history showing incorrect history

It seems as though the GNOME upstream change if applied to the 'unity-
control-center' will also fix the problem as it is the same file, same
code.

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

** Also affects: gnome-control-center-signon (Ubuntu Yakkety)
   Importance: Critical
   Status: Fix Released

** Also affects: account-plugins (Ubuntu Yakkety)
   Importance: Critical
   Status: Fix Released

** Changed in: gnome-control-center-signon (Ubuntu Yakkety)
Milestone: ubuntu-16.04.1 => None

** Changed in: account-plugins (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: gnome-control-center-signon (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1547647] Re: CRITICAL: please remove libqt5webkit dependancy

** Also affects: signon-ui (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: signon-ui (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Released

** Changed in: signon-ui (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: signon-ui (Ubuntu Yakkety)
Milestone: ubuntu-16.04.1 => None

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

Title:
  CRITICAL: please remove libqt5webkit dependancy

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  New
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11) depends
  on libqt5webkit5

  https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-
  updates/

  
  Can it be resolved so new LTS wont be released with known webkit1 
bugs/security exploits?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1547647/+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 1596207] Re: Sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

2016-06-29 Thread Michael Terry

** Changed in: gucharmap (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

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

Title:
  Sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

Status in gucharmap package in Ubuntu:
  New

Bug description:
  Please sync gucharmap 1:9.0.0-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian, remaining Ubuntu changes:
* debian/control:
* debian/rules:
* debian/gir1.2-gucharmap-2.90.install:
* debian/libgucharmap-2-90-7.install:
* debian/libgucharmap-2-90-dev.install:
  - Multi-arch the package

  Changelog entries since current yakkety version 1:8.0.1-1ubuntu1:

  gucharmap (1:9.0.0-1) unstable; urgency=medium

* New upstream release.
* Bump Build-Depends on unicode-data accordingly.
* Refresh debian/patches/unicode-source-generation.patch.
* Instead of patching configure.ac, set PROG_UNZIP in debian/rules.
* Convert from cdbs to dh.
* Bump debhelper compatibility level to 9.
* Convert to multiarch. (Closes: #812955)

   -- Michael Biebl   Sat, 25 Jun 2016 03:43:46 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1596207/+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 1547647] Re: CRITICAL: please remove libqt5webkit dependancy

** Changed in: signon-ui (Ubuntu)
Milestone: None => ubuntu-16.04.1

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

Title:
  CRITICAL: please remove libqt5webkit dependancy

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  New
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11) depends
  on libqt5webkit5

  https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-
  updates/

  
  Can it be resolved so new LTS wont be released with known webkit1 
bugs/security exploits?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1547647/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

** Changed in: gnome-control-center-signon (Ubuntu)
Milestone: None => ubuntu-16.04.1

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

** Summary changed:

- Allow plugins to decide which username to set on new accounts
+ [SRU] Allow plugins to decide which username to set on new accounts

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1597447] Re: vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab) under Workstation 12 Player

Alternatively installing xserver-xorg-input-libinput seems to supercede
vmmouse and give me mouse back without uninstalling vmmouse itself. That
actually matches my experience with Fedora 23 in the past few days..

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

Title:
  vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab)
  under Workstation 12 Player

Status in xserver-xorg-input-vmmouse package in Ubuntu:
  New

Bug description:
  Having xserver-xorg-input-vmmouse installed in my virtual machine
  sticks the mouse pointer to the middle of the screen.

  Tried to use ubuntu-bug to report this, but since it relies on Firefox
  (and there's no mouse..) it is frustratingly difficult to achieve.

  Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
  but we lose the grab/ungrab functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+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 1597447] Re: vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab) under Workstation 12 Player

FYI udev monitoring shows no events on the

** Attachment added: "udevadm-event0,1,2,3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+attachment/4692412/+files/udevadm-event0%2C1%2C2%2C3.txt

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

Title:
  vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab)
  under Workstation 12 Player

Status in xserver-xorg-input-vmmouse package in Ubuntu:
  New

Bug description:
  Having xserver-xorg-input-vmmouse installed in my virtual machine
  sticks the mouse pointer to the middle of the screen.

  Tried to use ubuntu-bug to report this, but since it relies on Firefox
  (and there's no mouse..) it is frustratingly difficult to achieve.

  Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
  but we lose the grab/ungrab functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2016-06-29 Thread Martin

Maybe duplicate?
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1381013

(While that bug is radeon driver, if the fix is the same in both
drivers, this can still be considered duplicate maybe?)

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xorg-server package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  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: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 29 12:21:13 2016
  DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
  InstallationDate: Installed on 2015-11-12 (229 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" -

[Desktop-packages] [Bug 1597447] Re: vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab) under Workstation 12 Player

** Attachment added: "udevadmin-mouse0,1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+attachment/4692411/+files/udevadmin-mouse0%2C1.txt

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

Title:
  vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab)
  under Workstation 12 Player

Status in xserver-xorg-input-vmmouse package in Ubuntu:
  New

Bug description:
  Having xserver-xorg-input-vmmouse installed in my virtual machine
  sticks the mouse pointer to the middle of the screen.

  Tried to use ubuntu-bug to report this, but since it relies on Firefox
  (and there's no mouse..) it is frustratingly difficult to achieve.

  Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
  but we lose the grab/ungrab functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+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 1597447] Re: vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab) under Workstation 12 Player

Installed VM is Ubuntu 16.04 x86-64 (UEFI) and the host is Windows 7
64-bit.

Are we missing a udev rule? Xorg log seems to report that the input1 or
mouse1 device is being ignored since no driver is specified. The current
udev rule only seems to match against "i8042 AUX port".

** Attachment added: "Xorg.1.log"

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+attachment/4692410/+files/Xorg.1.log

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

Title:
vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab)
under Workstation 12 Player

Status in xserver-xorg-input-vmmouse package in Ubuntu:
New

Bug description:
Having xserver-xorg-input-vmmouse installed in my virtual machine
sticks the mouse pointer to the middle of the screen.

Tried to use ubuntu-bug to report this, but since it relies on Firefox
(and there's no mouse..) it is frustratingly difficult to achieve.

Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
but we lose the grab/ungrab functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+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 1597447] [NEW] vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab) under Workstation 12 Player

Public bug reported:

Having xserver-xorg-input-vmmouse installed in my virtual machine sticks
the mouse pointer to the middle of the screen.

Tried to use ubuntu-bug to report this, but since it relies on Firefox
(and there's no mouse..) it is frustratingly difficult to achieve.

Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
but we lose the grab/ungrab functionality.

** Affects: xserver-xorg-input-vmmouse (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  vmmouse not functional (mouse pointer stuck, no auto-grab/ungrab)
  under Workstation 12 Player

Status in xserver-xorg-input-vmmouse package in Ubuntu:
  New

Bug description:
  Having xserver-xorg-input-vmmouse installed in my virtual machine
  sticks the mouse pointer to the middle of the screen.

  Tried to use ubuntu-bug to report this, but since it relies on Firefox
  (and there's no mouse..) it is frustratingly difficult to achieve.

  Uninstalling xserver-xorg-input-vmmouse solves the stuck mouse problem
  but we lose the grab/ungrab functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1597447/+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 1443052] Re: User accounts login history showing incorrect history

2016-06-29 Thread Jeremy Bicha

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

** Bug watch added: freedesktop.org Bugzilla #94497
   https://bugs.freedesktop.org/show_bug.cgi?id=94497

** Also affects: accountsservice via
   https://bugs.freedesktop.org/show_bug.cgi?id=94497
   Importance: Unknown
   Status: Unknown

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2016-06-29 Thread Martin

This Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=1307204
looks to me to be the same issue, and says that the cause is

'The problem is that xorg 1.17 or 1.18 replaced "HAS_DIRTYTRACKING2" with 
"HAS_DIRTYTRACKING_ROTATION" in pixmap.h and the old version of xf86-video-ati 
still looks for HAS_DIRTYTRACKING2.  The newest version of xf86-video-ati looks 
for either:
#if !defined(HAS_DIRTYTRACKING_ROTATION) && !defined(HAS_DIRTYTRACKING2)'

and it appears to have patches for both ati and nouveau drivers.  But I
can't tell if that is a fedora-only patch or an upstream patch that can
be brought to Ubuntu (or will eventually be brought in the normal course
of version advances).  Of course I am not an X expert so that fedora bug
could be subtly different and thus not the same fix.

** Bug watch added: Red Hat Bugzilla #1307204
   https://bugzilla.redhat.com/show_bug.cgi?id=1307204

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xorg-server package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  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: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 29 12:21:13 2016
  DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:

[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

A fix for this bug has been released upstream for the gnome-control-
center (see the linked upstream bug report).

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

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

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

Title:
  User accounts login history showing incorrect history

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

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1443052/+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 1443052] Re: User accounts login history showing incorrect history

The issue also affected Ubuntu GNOME 16.04 with GNOME 3.20.

** Tags added: xenial

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

Title:
  User accounts login history showing incorrect history

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

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1443052/+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 1597437] [NEW] X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2016-06-29 Thread Martin

Public bug reported:


Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

"Could not switch the monitor configuration" (bold text with do-not-enter icon)
"could not set the configuration for CRTC 64" (normal text)

After logging in (gnome flashback Metacity session) the same 3 monitors
are alive and the same pop-up appears.

Using Applications > System Tools > System Settings > Displays,
the 4th monitor is shown in grey and when clicking it, it shows that the slider 
is off.  When turning it to On (leaving default resolution and rotation) and 
clicking Apply

"The selected configuration for displays could not be applied" (bold text with 
do-not-enter icon)
"could not set the configuration for CRTC 64" (normal text)

a few seconds later (if the first one is not closed) another pop up with
do-not-enter icon:

"Failed to apply configuration: %s"
"Timeout was reached"

or trying again, if the first pop-up is closed within a few seconds, the
second one is

"Failed to apply configuration: %s"
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

...and the Displays GUI makes it look like the 4th monitor is enabled
but it is still blank.

At the time of doing this, /var/log/Xorg.0.log shows:
[ 96283.251] resize called 7680 1080
[ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
[ 96283.299] randr: failed to set shadow slave pixmap
[ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device


I have also tried this with xrandr command line:

$ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
xrandr: Configure crtc 3 failed

...and the Xorg.0.log at this time is almost the same as above, plus the
(I guess) fall back resizing to 3 monitors (5760x1080):

[ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
[ 96645.224] randr: failed to set shadow slave pixmap
[ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
[ 96645.227] resize called 0 0
[ 96645.227] -22
[ 96645.228] resize called 0 0
[ 96645.228] -22
[ 96645.229] resize called 7680 1080
[ 96645.281] resize called 5760 1080


I have previously tried to get around this with /etc/X11/xorg.conf with various 
Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

The 2-connector video cards to all four monitors are connected with DVI
cables.  The monitors are LG E2240TI, the video cards are (lspci):

01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
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: None
CurrentDesktop: GNOME-Flashback:Unity
Date: Wed Jun 29 12:21:13 2016
DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
 NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
InstallationDate: Installed on 2015-11-12 (229 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=1887ea54-959f-479e-9f3f-d1e5da317805 ro nomdmonddf nomdmonisw
SourcePackage: xorg-server
UpgradeStatus: Upgraded to xenial on 2016-06-23 (6 days ago)
dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1305
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version:

[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

** Branch linked: lp:~ci-train-bot/libunity/libunity-ubuntu-xenial-
landing-063

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+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 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapp

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-063

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

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-settings-daemon.  This problem was most recently seen
  with version 15.04.1+15.10.20150818-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6e9dcc008057a747fb5c2e65cd47f07e5b672724
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1503758/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-063

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 1571640] Re: lightdm changing resolution

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-063

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

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in unity-greeter source package in Xenial:
  New
Status in unity-greeter source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1510344] Re: Keyboard Backlight Turns on at boot

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-063

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1597431] [NEW] lightdm could run the X server without root privileges

2016-06-29 Thread Laurent Bonnaud

Public bug reported:

Hi,

there is this old document:

  https://wiki.ubuntu.com/X/Rootless

that states the goal of the running the X server without root
privileges.

With kernel DRM this goal is now attainable.  gdm already implements
this and it works on Ubuntu.  Here is what I have on another Ubuntu
system where I use gdm:

root  2588  0.0  0.0 285652  5256 ?Ssl  Jun25   0:00 /usr/sbin/gdm3
root  2593  0.0  0.0 267344  6448 ?Sl   Jun25   0:00 
gdm-session-worker 
bonnaudl  2609  0.0  0.0  62320  4464 tty7 Ssl+ Jun25   0:00 
/usr/lib/gdm3/gdm-x-session 
bonnaudl  2611  0.7  1.0 459736 165292 tty7Sl+  Jun25  43:40 
/usr/lib/xorg/Xorg vt7 -displayfd 3 

So would it be possible to implement a similar thing in lightdm ?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.2-0ubuntu1
Uname: Linux 4.6.3-040603-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jun 29 17:58:21 2016
EcryptfsInUse: Yes
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)

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


** Tags: amd64 apport-bug gnome3-ppa package-from-proposed third-party-packages 
xenial

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

Title:
  lightdm could run the X server without root privileges

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  there is this old document:

https://wiki.ubuntu.com/X/Rootless

  that states the goal of the running the X server without root
  privileges.

  With kernel DRM this goal is now attainable.  gdm already implements
  this and it works on Ubuntu.  Here is what I have on another Ubuntu
  system where I use gdm:

  root  2588  0.0  0.0 285652  5256 ?Ssl  Jun25   0:00 
/usr/sbin/gdm3
  root  2593  0.0  0.0 267344  6448 ?Sl   Jun25   0:00 
gdm-session-worker 
  bonnaudl  2609  0.0  0.0  62320  4464 tty7 Ssl+ Jun25   0:00 
/usr/lib/gdm3/gdm-x-session 
  bonnaudl  2611  0.7  1.0 459736 165292 tty7Sl+  Jun25  43:40 
/usr/lib/xorg/Xorg vt7 -displayfd 3 

  So would it be possible to implement a similar thing in lightdm ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 29 17:58:21 2016
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1597431/+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 1589022] Re: gnome-calendar assert failure: * stack smashing detected *: /usr/bin/gnome-calendar terminated

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

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

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

Title:
  gnome-calendar assert failure: *** stack smashing detected ***:
  /usr/bin/gnome-calendar terminated

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  I got this error a few times today, even after rebooting. I haven't
  intentionally run gnome-calendar today so it must be syncing with my
  Google calendar (set up with GNOME Online Accounts) in the background.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-calendar 3.20.2-0ubuntu3
  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
  AssertionMessage: *** stack smashing detected ***: /usr/bin/gnome-calendar 
terminated
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Jun  3 19:50:12 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2016-04-09 (55 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-calendar
  Stacktrace: $8 = 0x0
  StacktraceTop:
   
  Title: gnome-calendar assert failure: *** stack smashing detected ***: 
/usr/bin/gnome-calendar terminated
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1589022/+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 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapp

** Branch linked: lp:~unity-settings-daemon-team/unity-settings-
daemon/x-sru2

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

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-settings-daemon.  This problem was most recently seen
  with version 15.04.1+15.10.20150818-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6e9dcc008057a747fb5c2e65cd47f07e5b672724
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1503758/+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 1510344] Re: Keyboard Backlight Turns on at boot

** Branch linked: lp:~unity-settings-daemon-team/unity-settings-
daemon/x-sru2

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1518775] Re: gnome-panel cannot show newly installed software icons

2016-06-29 Thread Dmitry Shachnev

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

Andrea has uploaded a different patch for gnome-menus which adds a two
seconds timeout (in gnome-menus 3.13.3-6ubuntu4).

** This bug has been marked a duplicate of bug 1506744
   Newly installed applications do not show in the dash

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

Title:
  gnome-panel cannot show newly installed software icons

Status in gnome-menus:
  Confirmed
Status in gnome-panel package in Ubuntu:
  Confirmed

Bug description:
  1) First => sudo apt-get install gnome-session-flashback

  
  2) Then => re-login user with "Gnome Flashback (Metacity)" session

  
  3) Next => install a software that does not exist in gnome-panel menu list 
previously, such as "sudo apt-get install mousepad"

  However, after installion of mousepad, its icons doesn't show in
  gnome-panel menu list. I have to:

  4) killall gnome-panel

  5) gnome-panel &

  Then, the mousepad icon can be shown in gnome-panel menu list.

  This might be caused by forgetting to update icon menu list from
  gnome-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-panel 1:3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Nov 23 06:13:43 2015
  GsettingsChanges:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority', 'warning'] failed with 
exit code 1: Hint: You are currently not seeing messages from other users and 
the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-menus/+bug/1518775/+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 1571640] Re: lightdm changing resolution

** Branch linked: lp:~unity-settings-daemon-team/unity-settings-
daemon/x-sru2

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

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in unity-greeter source package in Xenial:
  New
Status in unity-greeter source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Branch linked: lp:~unity-settings-daemon-team/unity-settings-
daemon/x-sru2

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

2016-06-29 Thread Federico Leoni

I've tried to boot with a keylogger loaded on rc.local and as an option on 
lightdm to see if the keys are captured but I got no input from the moment I 
leave GRUB and the kernel start to load until the infamous 15 seconds after 
LighDM is loaded.
 
Since the issue seems to be strongly related to i8042, I've tested some kernel 
options:

i8042.direct - Put keyboard port into non-translated mode
i8042.dumbkbd - Pretend that controller can only read data from keyboard and 
cannot control its state (Don't attempt to blink the leds)
i8042.noaux - Don't check for auxiliary (== mouse) port
i8042.noloop - Disable the AUX Loopback command while probing for the AUX port
i8042.nomux - Don't check presence of an active multiplexing controller
i8042.nopnp - Don't use ACPIPnP / PnPBIOS to discover KBD/AUX controllers
i8042.reset - Reset the controller during init and cleanup

Again without any tangible results.

I've extracted from dmesg all the information from i8042 (with
'i8042.debug' option on GRUB).


** Attachment added: "i8042.debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1596200/+attachment/4692296/+files/i8042.debug.txt

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New
Status in xinput package in Ubuntu:
  New

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  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

[Desktop-packages] [Bug 1574693] Re: No shadows under menus on Unity.

2016-06-29 Thread Sebastien Bacher

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/3.18.9-1ubuntu4

SRU uploaded to xenial as well, it's in the queue and needs to get
reviewed

** Changed in: ubuntu
   Status: In Progress => Fix Released

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

Title:
  No shadows under menus on Unity.

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  After a fresh install of Ubuntu 16.04 in a new SSD, there aren't
  shadows under menus on application decoration borders and Unity panel.

  I've seen the same problem in Askubuntu:
  
http://askubuntu.com/questions/761842/no-shadows-under-menus-on-application-decoration-borders-and-unity-panel/762487#762487

  Thanks!!

  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: Mon Apr 25 16:38:08 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:143c]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=231aae18-0f30-4b65-943c-646a217d0d72 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 62.3D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  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: Mon Apr 25 16:23:48 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1574693/+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-06-29 Thread Matthias Klose

this is wrong, the libllvm3.8 package needs a renaming to libllvm3.8v4
or else upgrades to xenial will fail.


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

-- 
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:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  New

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 1574693] [NEW] No shadows under menus on Unity.

You have been subscribed to a public bug:

Hi,

After a fresh install of Ubuntu 16.04 in a new SSD, there aren't shadows
under menus on application decoration borders and Unity panel.

I've seen the same problem in Askubuntu:
http://askubuntu.com/questions/761842/no-shadows-under-menus-on-application-decoration-borders-and-unity-panel/762487#762487

Thanks!!

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: Mon Apr 25 16:38:08 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:143c]
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
InstallationDate: Installed on 2016-04-25 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP G62 Notebook PC
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=231aae18-0f30-4b65-943c-646a217d0d72 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 143C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 62.3D
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 059411252710001020100
dmi.sys.vendor: Hewlett-Packard
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: Mon Apr 25 16:23:48 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: Fix Released


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
No shadows under menus on Unity.
https://bugs.launchpad.net/bugs/1574693
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in [XPS 15 9550]

2016-06-29 Thread Cruz Fernandez

Aclaration: After boot, I have to select in the
Settings->Sound->Headphones to be able to hear though.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in [XPS 15 9550]

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

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

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1510344] Re: Keyboard Backlight Turns on at boot

** Branch linked: lp:unity-settings-daemon/16.04

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in [XPS 15 9550]

2016-06-29 Thread Cruz Fernandez

This seems fixed for latest kernel 4.4.0-28-generic. (I had to clean up my 
pulseaudio with 
'pulseaudio -k && rm -rf ~/.pulse && rm -rf ~/.config/pulse' ), and both were 
fixed (startup with jack connected and plugging in headphone)

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1506744] Re: Newly installed applications do not show in the dash

** Branch linked: lp:~unity-team/libunity/x-sru1

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Pat McGowan

This is most likely a symptom of bug #1506953 (mediahub crashes) or bug
#1596329 (mediahub hangs). It can be recreated by killing the media-hub-
server process, in most cases neither SMS or screenshot sounds are
played.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1560162] Re: Xenial: scaling is horribly out on xps13 install session

2016-06-29 Thread Ara Pulido

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

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  New
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in metacity source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  New

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1560162/+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 1560162] Re: Xenial: scaling is horribly out on xps13 install session

2016-06-29 Thread Ara Pulido

** Also affects: metacity (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  New
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in metacity source package in Xenial:
  New
Status in ubiquity source package in Xenial:
  New

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1560162/+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 1471998] Re: [enhancement] Support copy-paste between X and Mir

2016-06-29 Thread Christopher Townsend

Adding Libertine to this as it will have a new "pasted" daemon that
handles the transfer of pasteboard content between Xmir and content-hub.

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

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

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

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

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

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

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

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.3

** Changed in: libertine/trunk
Milestone: None => 1.3

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

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Libertine:
  In Progress
Status in Libertine devel series:
  In Progress
Status in Libertine trunk series:
  Triaged
Status in Mir:
  Fix Released
Status in libertine package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1471998/+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 1591503] Re: missing fcitx-mozc.mo

2016-06-29 Thread Gunnar Hjalmarsson

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

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-pack-ja-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-pack-zh-hans-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-pack-zh-hant-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: mozc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-pack-ja-base (Ubuntu Xenial)

** No longer affects: language-pack-zh-hans-base (Ubuntu Xenial)

** No longer affects: language-pack-zh-hant-base (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

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

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

** Changed in: mozc (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

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

** Changed in: mozc (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: mozc (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  missing fcitx-mozc.mo

Status in langpack-o-matic:
  Triaged
Status in language-pack-ja-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hans-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hant-base package in Ubuntu:
  Confirmed
Status in mozc package in Ubuntu:
  In Progress
Status in mozc source package in Xenial:
  In Progress

Bug description:
  $ LANG=C dpkg -S fcitx-mozc.mo
  dpkg-query: no path found matching pattern *fcitx-mozc.mo*

  Please include it for upcoming next translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1591503/+subscriptions

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

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

2016-06-29 Thread domnulnopcea

Hi,

you said

You can check in NM, under the connection's IPv4 and IPv6 tabs, behind
the "Routes.." button, if "Use this connection only for the resources on
its network" checkbox is checked. If you want all traffic to go through
the VPN, it *MUST NOT* be checked. If you want to use split tunnelling,
then it can, but you should configure your VPN to pass search domains
along with the nameservers to ensure they are only used on the right
domains.

I use split tunneling but I did not configure VPN to pass search domains
along with the nameservers. Can't this be done automatically? For
example the same vpn configuration works flawlessly in debian jessie.
There I do not have to configure search domains and nameservers...

thanks

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

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

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

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

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

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

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

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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

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

2016-06-29 Thread Mathieu Trudel-Lapierre

I've maintained NetworkManager for a while, and routinely use OpenVPN
for various things. Pushing nameservers from the openvpn server to the
client works as intended, as far as I can tell. If you use the default
settings, which I believe are to tunnel everything through the VPN, you
will only use the nameservers pushed by your VPN, and if using split
tunnelling, you will use any nameservers already defined for you "local"
connection, PLUS VPN nameservers.

All this is handled by dnsmasq, and largely depends on what information
it is fed. In the case where there are no search domains passed by the
VPN server, all we can do is add the nameserver from the VPN as an IP
address. In this case, if split tunnelling is enabled, DNS requests may
happen on any of the nameservers defined, regardless of whether they
come from the ISP, from the VPN, or elsewhere.

If no split-tunnelling is being done; then the VPN nameserver(s)
REPLACES the nameserver otherwise set in dnsmasq. Along with the fact
that all the traffic is routed through the VPN, this means all the
network traffic will happen over the VPN, including DNS requests.

You can check in NM, under the connection's IPv4 and IPv6 tabs, behind
the "Routes.." button, if "Use this connection only for the resources on
its network" checkbox is checked. If you want all traffic to go through
the VPN, it *MUST NOT* be checked. If you want to use split tunnelling,
then it can, but you should configure your VPN to pass search domains
along with the nameservers to ensure they are only used on the right
domains.

Things have been working this way at least for a few releases, probably
since Trusty (14.04). Bugs happen here and there of course, but we've
been fixing them as they popped up. The important thing here is that
they need to be well defined, explained so that we really understand
what is the issue you're facing, what kind of VPN you use, and how your
system (and more importantly your VPN connection) is configured.

Setting up VPNs correctly typically requires a fair amount of
understanding of how networks work in general, along with the extra
knowledge of what VPNs do exactly. If you're not the person who
configured the VPN servers, it's *much* better to ask them to file a bug
here to explain the issue in as much detail as possible, and including
any non-security-sensitive details about the VPN setup as they can.

Additionally, we've done a "minor" fix in 16.10 (the development
release) to avoid leaking search domains (see
https://launchpad.net/ubuntu/+source/network-manager/1.2.2-0ubuntu4). If
you feel like you've been seeing this, you may want to try out Ubuntu
using a live CD to see if the fix provided helps with your particular
setup.

Finally; from the looks of things and from my experience with these
kinds of bugs, there are far too many comments on this bug for everyone
to be having the exact same issue, considering things appear to largely
work correctly to me. What this means is that many of the commenters
here are actually seeing quite different issues; maybe related to VPN,
maybe not -- any bugs can be fixed, but they need to be isolated
correctly...

In other words, if you think you are seeing this bug here, and that the
description and comments above look like a problem you've been having,
then please file a new bug report, just for you (or have your VPN
administrator do it), with as much information as possible about the
issue, and we'll look at them individually. It's easier to mark bugs as
duplicates later if they really are the same than to split them up when
there are tons of me-toos.

In the meantime, I'm setting this bug as Incomplete; there currently
isn't enough information to know what has been happening exactly; and
I'd rather see individual good bug reports than risk ignoring one
genuine problem among a sea of comments.

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

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

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

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

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

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

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

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

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

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

2016-06-29 Thread Chris J Arges

Hello Andrew, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.1 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: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  Windows can not be moved above the top of screen because the coordinates 
system used is wrong.

  [Test Case]
  * Launch a non-CSD application, such as Firefox or Thunderbird;
  * Try Alt-dragging it above the top of the screen.

  [Regression Potential]
  The fix is changing the coordinates system to the right one and should not 
cause any regressions.

  -

  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect

  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+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 1592953] Re: Nautilus bookmarks folders leave permanent 'icon' on desktop

2016-06-29 Thread Chris J Arges

Hello Alexandros, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.1 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: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Nautilus bookmarks folders leave permanent 'icon' on desktop

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
    https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
    https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  When using drag-and-drop, the temporary windows are unmapped but never 
destroyed. This makes the compositor still draw them, which leads to unwanted 
artifacts on desktop.

  [Test Case]
  * Try dragging a bookmark from nautilus window to desktop;
  * There should be no artifacts remaining on the desktop.

  [Regression Potential]
  The fix is adding two lines and should not cause any regressions.

  -

  I'm using metacity in 16.04.

  Having opened nautilus with some folders on the left area (with favorite 
locations) if a accidentaly drag one location a permanent rectangular area with
  the name of that folder will remain on desktop in that location that the drop 
was 'made' and sits on top of every windwos sth very annoyning.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1592953/+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 1596574] Re: Cannot resize window by dragging the top edge

2016-06-29 Thread Chris J Arges

Hello Cui, or anyone else affected,

Accepted metacity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.18.5-0ubuntu0.1 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: metacity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Cannot resize window by dragging the top edge

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  This affects only users of Metacity with compositing mode disabled (which are 
usually users on old hardware or virtualized systems).

  [Test Case]
  * gsettings set org.gnome.metacity compositing-manager false;
  * Try resizing a window by dragging its top edge.

  [Regression Potential]
  The fix is one-line and should not cause any regressions.

  -

  Bug Version: 1:3.18.4-0ubuntu0.3

  Metacity running without composite manager.

  Users cannot resize window by dragging its top edge.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.4-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jun 27 23:18:31 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1596574/+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 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2016-06-29 Thread Joey Yakimowich-Payne

For me, I'm using a Microsoft Wireless Mobile Mouse 4000, and no
workarounds were working. lxinput and xset both did nothing, however I
did manage to get xinput to work.

I got the id of my mouse from here:

$> xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® Nano Transceiver v2.0id=13   [slave  pointer 
 (2)] <- I picked this one
⎜   ↳ Microsoft Microsoft® Nano Transceiver v2.0id=14   [slave  pointer 
 (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Sleep Button  id=8[slave  keyboard (3)]
↳ HD Webcam C615id=9[slave  keyboard (3)]
↳ Apple, Inc Apple Keyboard id=10   [slave  keyboard (3)]
↳ Apple, Inc Apple Keyboard id=11   [slave  keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver v2.0id=12   [slave  
keyboard (3)]

I picked 13, since there were multiple id's with the same name, and
listed the properties:

$> xinput list-props 13
Device 'Microsoft Microsoft® Nano Transceiver v2.0':
Device Enabled (152):   1
Coordinate Transformation Matrix (154): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Product ID (269):1118, 1861
Device Node (270):  "/dev/input/event6"
Evdev Axis Inversion (285): 0, 0
Evdev Axes Swap (287):  0
Axis Labels (288):  "Rel X" (162), "Rel Y" (163), "Rel Horiz Wheel" 
(277), "Rel Dial" (278), "Rel Vert Wheel" (279), "Rel Misc" (280)
Button Labels (289):"Button Left" (155), "Button Middle" (156), 
"Button Right" (157), "Button Wheel Up" (158), "Button Wheel Down" (159), 
"Button Horiz Wheel Left" (160), "Button Horiz Wheel Right" (161), "Button 
Side" (275), "Button Extra" (276), "Button Unknown" (273), "Button Unknown" 
(273), "Button Unknown" (273), "Button Unknown" (273)
Evdev Scrolling Distance (290): 1, 1, 1
Evdev Middle Button Emulation (291):0
Evdev Middle Button Timeout (292):  50
Evdev Third Button Emulation (293): 0
Evdev Third Button Emulation Timeout (294): 1000
Evdev Third Button Emulation Button (295):  3
Evdev Third Button Emulation Threshold (296):   20
Evdev Wheel Emulation (297):0
Evdev Wheel Emulation Axes (298):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (299):10
Evdev Wheel Emulation Timeout (300):200
Evdev Wheel Emulation Button (301): 4
Evdev Drag Lock Buttons (302):  0

Notice how there is no mention of "Mouse Acceleration" or any such
thing. I suspected that "Coordinate Transformation Matrix" had something
to do with it, so I tried changing the values:

&> xinput --set-prop 13 "Coordinate Transformation Matrix" 1.30,
0.00, 0.00, 0.00, 1.30, 0.00, 0.00, 0.00,
1.00

It worked! I just multiplied the first 2 "1.000"'s by the same
number (which I guess are X and Y speed) and now my mouse has a good
speed.

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  On up to date Raring alpha, on System Settings > Mouse & Touchpad the
  Mouse settings are completely missing.  The General and Touchpad
  sections are there but none for mouse.  See attached screenshot.

  xinput --list shows
  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MOSART Semi. 2.4G Keyboard Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ MOSART Semi. 2.4G Keyboard

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Jim Hodapp

@Anupam: can you try doing the top portion of comment #5 where you try
and turn up the volume. Like Pat said this can be tricky, but see if
you're able to do that. This will help confirm if it's indeed a volume
issue or some other PulseAudio configuration issue.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-29 Thread Jim Hodapp

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Medium => High

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

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

2016-06-29 Thread Graham Inggs

** Changed in: llvm-toolchain-3.8 (Ubuntu)
   Status: New => In Progress

** Changed in: llvm-toolchain-3.8 (Ubuntu)
 Assignee: (unassigned) => Graham Inggs (ginggs)

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

Title:
  please merge llvm-toolchain-3.8 from Debian unstable

Status in llvm-toolchain-3.8 package in Ubuntu:
  In Progress

Bug description:
  debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1593952/+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 1597314] Re: Support for apps which do not automatically connect to slots

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Support for apps which do not automatically connect to slots

Status in gnome-software package in Ubuntu:
  New

Bug description:
  With the addition of new interfaces there are some plugs which do not
  automatically connect and require action from the user in order to be
  connecte.

  As an example, VLC doesn't not automatically connect to the camera
  interface, but users may want to enable this, or maybe they dont.

  Some design considerations:

   * Do we want to ask users to toggle on/off connections they do/do not
  want.  i.e. a list of toggle buttons (what effect would this have on
  the application, would it fail gracefully or just not work (in which
  case the user could be made aware that it won't work without the
  permissions).

  vs

   * Do we want just a single Yes/No question where it's all the
  connections or none.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1597314/+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 1596200] Re: Ubuntu 16.04: unable to use internal keyboard for 15 sec on boot

2016-06-29 Thread Federico Leoni

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

** Summary changed:

- Ubuntu 16.04: unable to use internal  keyboard for 15 sec on boot
+ Ubuntu 16.04: unresponsive keyboard (15 sec) on boot

** Summary changed:

- Ubuntu 16.04: unresponsive keyboard (15 sec) on boot
+ Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New
Status in xinput package in Ubuntu:
  New

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  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: Sat Jun 25 12:00:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19778 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1597268] Re: Nautilus tooltip doesnt close on left click if within ~100px radius of top left corner

2016-06-29 Thread Stefan

Desktop Environment: Gnome

Yes you are right, i meant the context menu (the one that has options
like 'new folder', 'open in terminal',.. )

A bit more in depth:
It does not matter where the click is, clicking either inside the main pane, 
the sidebar, the toolbar, even clicking outside the window doesn't work (no 
matter if left or right). pressing the escape key always closes the menu 
instantly. if you move away for more than 100px it closes instantly aswell.

heres something odd:

I'm using the numix GTK theme (no shell theme). in numix the radius is much 
larger and multiple clicks on the same spot do not change anything.
when switching to the default adwaita theme the radius becomes much smaller and 
clicking twice (no matter the delay between the clicks) also closes the context 
menu.

im not convinced this is an issue of nautilus, but all the other
context-menus of other programs im using are working perfectly fine.

let me know if i can provide additional information.

** Description changed:

  1. Open a nautilus window
  2. Rightclick somewhere to make a tooltip appear
  3. Can't close it by left clicking if the click is in an area (estimated 
100px) near the top left corner (outside of the tooltip)
  
  OS: Ubuntu 16.04 LTS
  Nautilus: 3.14.3
+ Desktop Environment: Gnome

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

Title:
  Nautilus tooltip doesnt close on left click if within ~100px radius of
  top left corner

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  1. Open a nautilus window
  2. Rightclick somewhere to make a tooltip appear
  3. Can't close it by left clicking if the click is in an area (estimated 
100px) near the top left corner (outside of the tooltip)

  OS: Ubuntu 16.04 LTS
  Nautilus: 3.14.3
  Desktop Environment: Gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1597268/+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 1597314] [NEW] Support for apps which do not automatically connect to slots