[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

Is this really related to the linked gnome-shell bug?  It doesn't look
related to me.  This bug is completely reproducible whereas the linked
one seems to be an intermittent complete failure of the shell.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1862910] Re: gnome-shell leaking memory when a customized AppImageLauncher is running

[Colin Law]

I have opened a new issue on AppImageLauncher.
https://github.com/TheAssassin/AppImageLauncher/issues/301

** Bug watch added: github.com/TheAssassin/AppImageLauncher/issues #301
   https://github.com/TheAssassin/AppImageLauncher/issues/301

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

Title:
  gnome-shell leaking memory when a customized AppImageLauncher is
  running

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Edited description:
  To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome)
  1. Install AppImageLauncher from 
https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 
2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and 
install it.  If necessary run
  sudo apt install -f
  to fix missing dependencies.

  2. Run it and change the appimage destination location to
  ~/apps/appimages.  It is necessary to change it away from the default
  setting in order for the problem to appear, though probably the actual
  destination is not important).  Ensure that Auto start auto-
  integration daemon is selected.

  3. Download an appimage (I downloaded Cura 4.4.1 from
  https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know
  whether any appimage would do, probably it would.  In fact I don't
  know whether this step and the next need to be done at all.

  4. Open it with appimagelauncher (this can be done by double clicking
  it in nautilus) and tell it to move it and run the application.  Then
  close the application.

  5. It may be necessary to reboot at this point I don't know.

  6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome-
  shell.  It may take a few minutes to get going but then the memory
  used will start increasing at several MB/minute.

  There is an issue open against appimage launcher which is likely the
  same problem.
  https://github.com/TheAssassin/AppImageLauncher/issues/294

  Original description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Colin Law]

A note for anyone finding this that if you have installed
AppImageLauncher then see bug #1862910.

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1862910] Re: gnome-shell leaking memory in interaction with appimagelauncher

[Colin Law]

I have managed to replicate it on another system, it was necessary to
change the destination location away from the default in
appimagelauncher for the problem to appear.  I have updated the
description above with detailed procedure for replicating.

There is already an open issue against appimagelauncher which is most likely 
related.  
https://github.com/TheAssassin/AppImageLauncher/issues/294

** Description changed:

+ Edited description:
+ To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome)
+ 1. Install AppImageLauncher from 
https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 
2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and 
install it.  If necessary run
+ sudo apt install -f
+ to fix missing dependencies.
+ 
+ 2. Run it and change the appimage destination location to
+ ~/apps/appimages.  It is necessary to change it away from the default
+ setting in order for the problem to appear, though probably the actual
+ destination is not important).  Ensure that Auto start auto-integration
+ daemon is selected.
+ 
+ 3. Download an appimage (I downloaded Cura 4.4.1 from
+ https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know
+ whether any appimage would do, probably it would.  In fact I don't know
+ whether this step and the next need to be done at all.
+ 
+ 4. Open it with appimagelauncher (this can be done by double clicking it
+ in nautilus) and tell it to move it and run the application.  Then close
+ the application.
+ 
+ 5. It may be necessary to reboot at this point I don't know.
+ 
+ 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome-
+ session.  It may take a few minutes to get going but then the memory
+ used will start increasing at several MB/minute.
+ 
+ There is an issue open against appimage launcher which is likely the
+ same problem.
+ https://github.com/TheAssassin/AppImageLauncher/issues/294
+ 
+ Original description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.
  
  See also bug #1856516
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

** Bug watch added: github.com/TheAssassin/AppImageLauncher/issues #294
   https://github.com/TheAssassin/AppImageLauncher/issues/294

** Description changed:

  Edited description:
  To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome)
  1. Install AppImageLauncher from 
https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 
2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and 
install it.  If necessary run
  sudo apt install -f
  to fix missing dependencies.
  
  2. Run it and change the appimage destination location to
  ~/apps/appimages.  It is necessary to change it away from the default
  setting in order for the problem to appear, though probably the actual
  destination is not important).  Ensure that Auto start auto-integration
  daemon is selected.
  
  3. Download an appimage (I downloaded Cura 4.4.1 from
  https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know
  whether any appimage would do, probably it would.  In fact I don't know
  whether this step and the next need to be done at all.
  
  4. Open it with appimagelauncher (this can be done by double clicking it
  in 

[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory in interaction with appimagelauncher

[Colin Law]

** Summary changed:

- gnome-shell leaking memory
+ gnome-shell leaking memory in interaction with appimagelauncher

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

Title:
  gnome-shell leaking memory in interaction with appimagelauncher

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1862910] Re: gnome-shell leaking memory

[Colin Law]

I had initially misunderstood which way round you wanted me to check
with the seconds setting, but I had checked carefully both ways and have
now checked again that I cannot see any discernable leakage with seconds
enabled, but I have got it disabled now.

I have also confirmed without doubt that it is appimagelauncher daemon
that is triggering the problem.  With it disabled there is no apparent
leakage and with it enabled there is.  However, rather irritatingly, I
have been unable to replicate this on another machine, so there must be
some additional interaction on the failing system.  Currently I have no
idea what that might be.

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1862910] Re: gnome-shell leaking memory

[Colin Law]

I think this may not be a gnome-shell issue at all.  I installed 
appimagelauncher [1] some time ago and if I disable the daemon and reboot then 
it seems the memory leak is no more.  At least I think that is the case, I need 
to do some more testing but thought I should report back immediately so that 
no-one wastes any more time on it.
I will follow up when I have reached a firm conclusion.

[1] https://github.com/TheAssassin/AppImageLauncher

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1862910] Re: gnome-shell leaking memory

[Colin Law]

** Attachment added: "glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327670/+files/glxinfo.txt

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1862910] Re: gnome-shell leaking memory

[Colin Law]

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327669/+files/lspcik.txt

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1862910] Re: gnome-shell leaking memory

[Colin Law]

1. Screenshot attached.  I have been using two screens but to simplify
things I have confirmed that only having one makes no difference, so I
am sticking to that whilst testing.

2. I did already have show seconds set, I have now tried without and it
doesn't seem to make a difference

3. I thought I had disabled all extensions, though I am not entirely
sure of the official method of doing that.  If I go to
https://extensions.gnome.org/local/ I see only Desktop Icons, Ubuntu App
Indicators and Ubuntu Dock and they are all disabled, but as you can see
from the screenshot I don't see exactly the same as I see if I logon
using Gnome.  For instance the Dock is not autohiding.  So I don't know
what is going on there.  Logging on using Gnome does not stop the leak
though.

I see I have a larger selection of logon options than I see in a clean
install, I have Gnome, Gnome Classic, Gnome on Xorg, Ubuntu, Ubuntu on
Wayland, and Unity.  I tried them all a few days ago and they all
exhibited the leak except Gnome Classic and Unity, though I have done a
lot of cleaning up trying to fix the problem since then so if it would
be useful I can repeat that test.


** Attachment added: "Desktop screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327658/+files/Screenshot%20from%202020-02-12%2014-02-37.png

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Colin Law]

Reported bug #1862910

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1862910] [NEW] gnome-shell leaking memory

[Colin Law]

Public bug reported:

On one of my machines which has been upgraded over several years and
is now running 19.10 just one of the configured users appears to be
seeing a dramatic memory leak in gnome-shell, even when nothing is
happening on the UI. Immediately after logging on, using the Ubuntu
selection from the logon screen, gnome shell shows as using about
134MB. From there it climbs at about 300MB per hour and after a few
hours the machine grinds to a crawl, not surprisingly. This happens
even if the user logs on and then the machine is left completely
alone. Logout and back in frees all the memory.
A test user I have configured sees no such problem.
I have uninstalled all extensions apart from the system ones, disabled
all the system ones and reset all the gnome settings using dconf reset
-f /org/gnome/ to no avail. Also I have removed
~/.local/share/gnome-shell and allowed it to recreate it.
Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
I can't see anything obvious in the log.
It must be something in my settings that is triggering it as the other
user does not see it, but I have run out of ideas on what to try.

See also bug #1856516

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 12 08:54:21 2020
DisplayManager: gdm3
InstallationDate: Installed on 2014-10-21 (1939 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  gnome-shell leaking memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On one of my machines which has been upgraded over several years and
  is now running 19.10 just one of the configured users appears to be
  seeing a dramatic memory leak in gnome-shell, even when nothing is
  happening on the UI. Immediately after logging on, using the Ubuntu
  selection from the logon screen, gnome shell shows as using about
  134MB. From there it climbs at about 300MB per hour and after a few
  hours the machine grinds to a crawl, not surprisingly. This happens
  even if the user logs on and then the machine is left completely
  alone. Logout and back in frees all the memory.
  A test user I have configured sees no such problem.
  I have uninstalled all extensions apart from the system ones, disabled
  all the system ones and reset all the gnome settings using dconf reset
  -f /org/gnome/ to no avail. Also I have removed
  ~/.local/share/gnome-shell and allowed it to recreate it.
  Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2.
  I can't see anything obvious in the log.
  It must be something in my settings that is triggering it as the other
  user does not see it, but I have run out of ideas on what to try.

  See also bug #1856516

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 08:54:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-10-21 (1939 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Colin Law]

Unfortunately when I run ubuntu-bug gnome-shell it collects the
information but then when I tell it to send it just returns to the
command line immediately rather than sending me to launchpad, so I will
have to get that sorted first.

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Colin Law]

I don't know whether a problem I have is related to this issue or not.  On one 
of my machines which has been upgraded over several years and is now running 
19.10 just one of the configured users is seeing a dramatic leak in 
gnome-shell, even when nothing is happening on the UI.  Immediately after 
logging on using the Ubuntu selection from the logon screen gnome shell shows 
as using about 134MB. From there it climbs at about 300MB per hour and after a 
few hours the machine starts using swap and performance grinds to a crawl.  
This happens even if the user logs on and then the machine is left completely 
alone.  Logout and back in frees all the memory.
A test user I have configured sees no such problem.
I have uninstalled all extensions apart from the system ones, disabled all the 
system ones and reset all the gnome settings using dconf reset -f /org/gnome/ 
to no avail.  Also I have removed ~/.local/share/gnome-shell and allowed it to 
recreate it.
I can't see anything obvious in the log.
It must be something in my settings that is triggering it but I have run out of 
ideas on what to try.

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

I don't seem to be able to change the status back to confirmed for some
reason.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

I am still seeing this in 19.10 (eoan).


** Tags added: eoan

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1725779] Re: Gnome network manager cannot find authentication binary

[Colin Law]

@simongkelly if the symptom was fixed by a reboot then it is not the
same issue

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1725779] Re: Gnome network manager cannot find authentication binary

[Colin Law]

Please ignore my previous comment, I was thinking of the wrong bug!

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

@Arnaud D this bug is specifically about the Authorization dialog in the
Software and Updates app.  It is not a general problem with the mouse.
In fact it is nothing to do with the mouse at all.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

It is still an issue on 19.04.
Steps to replicate:
Open Software & Updates and switch to the Other Software tab and click one of 
the checkboxes. The window loses focus but the authentication dialog does not 
appear. If however a checkbox on the Ubuntu Software tab is clicked then the 
authentication dialog does appear.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

It doesn't seem to be to do with user settings as I have tried making a new 
user and it fails for that user also.
I can also confirm that it is ok on Wayland, which is not surprising.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

For myself, I have not got any other applications open, and I have not got any 
Gnome shell extensions enabled (according to Gnome Tweaks).
There must be something significant about the fact that it only fails from the 
Other Software tab, it works from the Ubuntu S/W, Updates and Developer Options 
tabs.
There must be something unusual about the failing systems though, but what it 
is remains a mystery.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

Log attached, this is from the Disco system

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734095/+attachment/5256487/+files/journalctl.log

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

Just to confirm I can reproduce this 100% reliably in 18.10 and in Disco, as 
follows.
Open Software & Updates and switch to the Other Software tab and click one of 
the checkboxes the window loses focus but the authentication dialog does not 
appear (I have checked it is not under another window). If however I click a 
checkbox on the Ubuntu Software tab then the authentication dialog does appear.

** Tags added: disco

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

[Colin Law]

@experimancer it is not correct to say that this problem affects all
18.04 and 18.10 installations, none of mine are seriously affected by
it.  It seems it only affects a small minority.  This does not change
the fact that for those affected it is a serious issue that needs to be
addressed but it does explain why it has not been dealt with more
urgently.

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Colin Law]

It has only been marked Won't Fix in Yakkety, because Yakkety is well
past it's sell by date.  It is still open on Xenial.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

Just to confirm I am still seeing this in 18.10.  A few more details:
If I open Software & Updates and switch to the Other Software tab and click one 
of the checkboxes the window loses focus but the authentication dialog does not 
appear (I have checked it is not under another window).  If however I click a 
checkbox on the Ubuntu Software tab then the authentication dialog does appear.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: cosmic

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1734095/+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 1725779] Re: Gnome network manager cannot find authentication binary

[Colin Law]

@geez your first para is exactly what I have seen. No problem with clean
install of 18.04, but there were problems with an system upgraded from
17.10.  My comment about the upgraded system was ambiguous, it is on a
system upgraded from 17.10 that I see the problem.  My suggestion is
that is the upgrader that takes the system from 17.10 to 18.04 that is
the problem, in not installing those packages.

You have misread my comment on the packages to check.  They are network-
manager-pptp-gnome and network-manager-openvpn-gnome.  On my system
upgraded from 17.10 these were not installed (I don't know whether they
were on 17.10).

When you say everything works as expected is that on the system upgraded
from 17.10 which is showing this bug?  In which case I don't understand.

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1725779] Re: Gnome network manager cannot find authentication binary

[Colin Law]

Has anyone tried this (or confirmed that they already have 
network-manager-pptp-gnome and network-manager-openvpn-gnome installed)?  It 
has fixed it for me, I suspect that is an issue with the upgrader.  A fresh 
install of 18.04 has it, but my upgraded system did not.
I do see, though, that one person with the problem has already got it installed 
so maybe there is more than one issue here.

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1725779] Re: Gnome network manager cannot find authentication binary

[Colin Law]

Does installing network-manager-pptp-gnome help?
I had the same issue using openvp and installing network-manager-openvpn-gnome 
fixed it (though I still don't get the padlock shown, but it does connect).

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1772066] Re: Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10, 17.04

[Colin Law]

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

Try installing
network-manager-openvpn-gnome

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

Title:
  Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10,
  17.04

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

Bug description:
  Under Kubuntu 18.04 and Ubuntu 18.04 (both installed multiboot on a
  Thinkpad X230T), OpenVPN won't connect to a host that worked under
  Kubuntu 17.10 and 17.04.  This host continues to be accessible under
  Deepin Linux.

  Here is a log from today's attempt on Kubuntu 18.04.

  -- begin paste --

  $ grep VPN /var/log/syslog
  May 18 12:19:28 mycomputer systemd[1]: Stopped OpenVPN service.
  May 18 12:20:02 mycomputer systemd[1]: Starting OpenVPN service...
  May 18 12:20:02 mycomputer systemd[1]: Started OpenVPN service.
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.0028] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 Started the VPN service, PID 3113
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.2667] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: starting (3)
  May 18 12:22:19 mycomputer nm-openvpn[3116]: OpenVPN 2.4.4 
x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] 
[AEAD] built on Feb 10 2018
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5365] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: failed: connect-failed (1)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5365] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: failed: connect-failed (1)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5370] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: stopping (5)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5381] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: stopped (6)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5396] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN service disappeared

  -- end paste --

  Just in case it's not included from the ubuntu-bug network-manager-
  openvpn

  -- begin paste --

  $ lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  $ apt-cache policy network-manager-openvpn
  network-manager-openvpn:
Installed: 1.8.2-1
Candidate: 1.8.2-1
Version table:
   *** 1.8.2-1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  -- end paste --

  And here's the results of an attempt on Ubuntu 18.04 a few days ago.

  -- begin paste --

  daviding@mycomputer:~$ grep VPN /var/log/syslog
  May 16 13:09:38 mycomputer NetworkManager[935]:   [1526490578.0785] 
keyfile: add connection /etc/NetworkManager/system-connections/UTorVPN 
(0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN")
  May 16 13:09:38 mycomputer NetworkManager[935]:   [1526490578.0794] 
audit: op="connection-add" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635 uid=1000 result="success"
  May 16 13:11:11 mycomputer gnome-shell[2018]: VPN plugin at 
/usr/lib/NetworkManager/nm-openvpn-auth-dialog is not executable
  May 16 13:11:11 mycomputer gnome-shell[2018]: Invalid VPN service type 
(cannot find authentication binary)
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3080] 
audit: op="connection-activate" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635 uid=1000 result="success"
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3167] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 Started the VPN service, PID 5807
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3231] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 Saw the service appear; activating connection
  May 16 13:11:42 mycomputer NetworkManager[935]:  [1526490702.3286] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 plugin NeedSecrets request #1 failed: Invalid connection type.
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3361] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 VPN service disappeared
  May 16 13:11:43 mycomputer NetworkManager[935]:   [1526490703.3431] 
audit: op="connection-activate"H uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635 uid=1000 result="success"
  May 16 13:11:43 mycomputer 

[Desktop-packages] [Bug 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

@Darius, the point is the bug is not about gnome-software it is about 
software-properties-gtk.  To run it from a terminal use the command
/usr/bin/python3 /usr/bin/software-properties-gtk

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1734095/+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 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

@Darius this bug is about the Software & Updates app, which is the one
that controls sources.list etc.  The bug is that it does not popup the
Authorization dialog.  It seems to be in no way related to your issue.

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1734095/+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 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors

[Colin Law]

Hi Lukasz

Unfortunately(?) the bug seems no longer to exhibit itself on my (18.04)
system with the current version, 0.9.1, it seemed to fix itself
(presumably with an upgrade to something) a little while ago.

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

Title:
  gnome-shell crash using ubuntu-dock with dual monitors

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Using Ubuntu 17.04 on a laptop with an external display on its right
  hand side all is well with dash-to-dock provided the laptop display is
  set to the primary display. However if I set the external display to
  be the primary display (with dash-to-dock disabled) then as soon as I
  enable it gnome-shell crashes and I am logged off. See attached
  excerpt from syslog. I have to remove .local/share/gnome-shell in
  order to recover the situation.

  [ Test case ]

  Plug an external monitor to a laptop, with the external monitor on the
  right side and configure the externals primary monitor.

  Login and Logout

  Gnome shell shouold not crash.

  [ Regression Potential ]

  The dock won't be temporarily shown in a monitor

  
  ---

  To replicate on Artful daily on a laptop, plug in an external monitor
  with the external monitor to the right of the laptop and configure the
  external monitor as the primary display. On configuration it works ok,
  but on logging out and back in gnome-shell crashes.  The problem is
  only seen if the external monitor is the primary display.

  I think it likely that this is the same issue reported for dash-to-dock:
  https://github.com/micheleg/dash-to-dock/issues/493

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:29:17 2017
  InstallationDate: Installed on 2017-08-22 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170821)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712661/+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 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Colin Law]

I am also seeing very similar effects. The menu doesn't show the wifi
connection points at all and sometimes the network icon in the top panel
disappears completely.  As others have found control via Settings works
fine. Ubuntu 18.04 on a Lenovo Lifebook.

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+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 1713205] Re: Slow suspend when wifi active

[Colin Law]

Still present in 17.10

** Tags added: artful

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1713205/+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 1734095] [NEW] After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup

[Colin Law]

Public bug reported:

After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and
Updates app and attempt to change anything it does not popup the
authorization dialog and will not let changes through.  In sylog I see

Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 
identities that can be used for authentication. Only considering one.
Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal 
failed
Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to 
show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

Before the upgrade it was ok.
Other apps that require authorisation function as expected.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Nov 23 10:07:44 2017
DisplayManager: lightdm
InstallationDate: Installed on 2014-10-21 (1128 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  After upgrade to ubuntu 17.10 Software & Updates not showing
  authorization popup

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734095/+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 1691676] Re: Mouse cursor (pointer) is missing during desktop zoom in gnome-shell

[Colin Law]

@skuck71 presumably you had zoom on before the upgrade.

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

Title:
  Mouse cursor (pointer) is missing during desktop zoom in gnome-shell

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Mouse cursor (pointer) is missing during desktop zoom in gnome-shell

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:24:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1691676/+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 1721963] [NEW] No mouse cursor on Wayland when Universal Access > Zoom is selected

[Colin Law]

Public bug reported:

Using default login on 17.10 Beta, which I believe is Wayland, when
Universal Access > Zoom is selected the mouse cursor disappears. The
mouse continues to function, but no cursor is visible.

It is ok when used with X login.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  7 15:33:04 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 
'ubuntu-amazon-default.desktop', 'gnome-control-center.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
InstallationDate: Installed on 2017-10-03 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171003)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  No mouse cursor on Wayland when Universal Access > Zoom is selected

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using default login on 17.10 Beta, which I believe is Wayland, when
  Universal Access > Zoom is selected the mouse cursor disappears. The
  mouse continues to function, but no cursor is visible.

  It is ok when used with X login.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 15:33:04 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-10-03 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171003)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721963/+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 1712283] Re: Cannot resolve DNS in artful daily

[Colin Law]

@prefec2 that sounds like a different bug. This one is not intermittent.
If the workaround in comment #6 does not fix it for you then I suggest
filing a new bug.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@litinoveweedle this bug is marked fixed. If you are still seeing a
similar symptom then I suggest opening a new bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1713205] [NEW] Slow suspend when wifi active

[Colin Law]

Public bug reported:

Running 17.04 (upgraded over several versions) I see a ten second
additional delay on suspend if wifi is in use. Looking at the journal
this looks to be debian wpa bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=835648

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: wpasupplicant 2.4-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 26 08:13:04 2017
InstallationDate: Installed on 2014-10-21 (1039 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
SourcePackage: wpa
UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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


** Tags: amd64 apport-bug zesty

** Description changed:

  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
- this looks to be debian wpa bug #835648
+ this looks to be debian wpa bug 835648
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835648
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

** Description changed:

  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
- this looks to be debian wpa bug 835648
- 
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835648
+ this looks to be debian wpa bug https://bugs.debian.org/cgi-
+ bin/bugreport.cgi?bug=835648
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  New

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1713205/+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 1712283] Re: Cannot resolve DNS in artful daily

[Colin Law]

I can confirm that for me removing /etc/resolv.conf and replacing it
with a link to stub-resolv.conf using

sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

and rebooting (probably I could just have restarted the appropriate
service) restores DNS functionality.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1702071] Re: Search spins forever, returns no results.

[Colin Law]

Robert - yes I think you are right. In fact the issue went away after I
rebooted (at least I think that was what did it). I need to re-install
the OS and see if it happens again.

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

Title:
  Search spins forever, returns no results.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  alan@gort:~$ apt-cache policy gnome-software
  gnome-software:
Installed: 3.20.5-0ubuntu0.16.04.1.1
Candidate: 3.20.5-0ubuntu0.16.04.1.1
Version table:
   *** 3.20.5-0ubuntu0.16.04.1.1 500
  500 http://ppa.launchpad.net/ubuntu-desktop/gnome-software/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I mentioned to Robert last week that I keep getting the spinner and no
  results returned when searching in g-s on 16.04. He suggested I update
  to the version in the PPA and enable logging to capture what's
  happening. Log attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1702071/+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 1702071] Re: Search spins forever, returns no results.

[Colin Law]

I am seeing this on a fresh install of Artful. In addition to the search
running forever (or at least a long time) there are no apps to be seen
in the various categories (just rectangles with ... inside) and the
featured app and editor's picks just show dots.

Should I report this as a new bug or is it the same one?

** Tags added: artful

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

Title:
  Search spins forever, returns no results.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  alan@gort:~$ apt-cache policy gnome-software
  gnome-software:
Installed: 3.20.5-0ubuntu0.16.04.1.1
Candidate: 3.20.5-0ubuntu0.16.04.1.1
Version table:
   *** 3.20.5-0ubuntu0.16.04.1.1 500
  500 http://ppa.launchpad.net/ubuntu-desktop/gnome-software/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I mentioned to Robert last week that I keep getting the spinner and no
  results returned when searching in g-s on 16.04. He suggested I update
  to the version in the PPA and enable logging to capture what's
  happening. Log attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1702071/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Colin Law]

@Willem, since this bug is specifically about invoking the HUD from
firefox, and it seems from your description that you are not using
firefox and you are not seeing the problem specifically when you open
the HUD, I think your problem does not fit the description of this bug.
You would probably be better to start a new bug.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@exander77 there is no need for personal abuse here. In that case the
description of this bug should have been updated to include that.
However I see there is debate on that bug about whether it is fixed by
the version of dnsmasq which fixes this bug. If not then it is
definitely a different bug. I suggest opening a new bug. It will not get
duplicated to this one if the dnsmasq fix does not fix the problem.
There is no point commenting further on this bug as it is marked as
fixed so no-one will do anything about it.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Colin Law]

@exander77 this bug is specifically about a failure after
suspend/resume. If your issue does not relate to suspend/resume it is a
different bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt

[Colin Law]

I don't know whether it is significant but I notice in syslog that for
the second connection to the vpn I see the additional line

systemd-resolved[1001]: Using degraded feature set (UDP+EDNS0+DO) for
DNS server 127.0.1.1.

and I notice that a similar message is present in the log in comment #1

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

Title:
  Network Manager + OpenVPN does not respond to DNS server change on
  second connection attempt

Status in dnsmasq:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Scenario:
  Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I 
only have the one computer to test with, the 16.10 is definitely relevant (I 
did not have this problem on 16.04)  but I can't tell if the upgrade is part of 
it,  (the upgrade may or may not be relevant).

  Have "full time"  wired or wireless connection  (does not matter which used)
  Part time OpenVPN connection set up via NetworkManager.

  Steps to reproduce
  1. Fresh boot
  2.  ping a device on the VPN network  (eg amachine.remotelan ) Result:  
"ping: amachine.remotelan: Name or service not known"
  3.  Connect to the VPN service via Network Manager.
  4. ping amachine.remotelan  -  result:
   PING amachine.remotelan (192.168.68.44) 56(84) bytes of data.
64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 
time=7.75 ms
  5.  Disconnect from the VPN service again.
ping result again "ping: amachine.remotelan: Name or service not known"

  6. Reconnect to the VPN again, and ping again

  Observed: 
 "ping: amachine.remotelan: Name or service not known"

However "ping 192.168.68.44"  responds successfully as expected

  Expected:
  PING ... 192.168 64 bytes from .. etc   to the ping by name

  ---
  Further info I'm going to add in a subsequent comment. (just annotating 
syslog right now!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dnsmasq/+bug/1644098/+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 1617204] Re: NM does not offer VPN options

[Colin Law]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  NM does not offer VPN options

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  network-manager-pptp is installed, but when I select "Configure VPN"
  NM offers only Hardware and Virtual options, no VPN options.,

  Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything
  works as expected on Lubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Aug 26 09:05:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-08 (17 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IpRoute:
   default via 172.16.0.27 dev wlp2s0  proto static  metric 600 
   172.16.0.0/16 dev wlp2s0  proto kernel  scope link  src 172.16.0.182  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617204/+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 1627839] [NEW] Tab title text is almost invisible in libreoffice

[Colin Law]

Public bug reported:

On tabbed dialogs in libreoffice on up to date Yakkety the tab title
text is virtually invisible. See screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice-common 1:5.2.1~rc2-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 26 21:07:48 2016
InstallationDate: Installed on 2014-10-21 (706 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
PackageArchitecture: all
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-09-17 (9 days ago)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "FormatCells.png"
   
https://bugs.launchpad.net/bugs/1627839/+attachment/4748971/+files/FormatCells.png

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

Title:
  Tab title text is almost invisible in libreoffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On tabbed dialogs in libreoffice on up to date Yakkety the tab title
  text is virtually invisible. See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-common 1:5.2.1~rc2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 21:07:48 2016
  InstallationDate: Installed on 2014-10-21 (706 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-09-17 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1627839/+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 1160046] Re: terminal does not resize correctly after maximise by sliding to top panel

[Colin Law]

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

** This bug has been marked a duplicate of bug 1521302
   gnome-terminal maximize than un-maximize behaves odd

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

Title:
  terminal does not resize correctly after maximise by sliding to top
  panel

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  On up to date Raring.  To replicate
  Open gnome terminal
  Slide title bar to top panel to maximise window
  Slide away from top panel to restore it
  It should return to original size, but instead it remains near maximised size.

  If instead the terminal is maximised using the window control then it
  correctly restores the size (whichever method is used to restore the
  window).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-terminal 3.6.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: i386
  Date: Mon Mar 25 21:37:23 2013
  InstallationDate: Installed on 2012-08-01 (236 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1160046/+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 1160046] Re: terminal does not resize correctly after maximise by sliding to top panel

[Colin Law]

Not so much still a problem as an old problem returned.  It was not
present in 14.04 to 15.10 (at least for me) but has returned with 16.04.

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

Title:
  terminal does not resize correctly after maximise by sliding to top
  panel

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  On up to date Raring.  To replicate
  Open gnome terminal
  Slide title bar to top panel to maximise window
  Slide away from top panel to restore it
  It should return to original size, but instead it remains near maximised size.

  If instead the terminal is maximised using the window control then it
  correctly restores the size (whichever method is used to restore the
  window).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-terminal 3.6.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: i386
  Date: Mon Mar 25 21:37:23 2013
  InstallationDate: Installed on 2012-08-01 (236 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1160046/+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 1555729] [NEW] Security & Privacy missing from System Settings

[Colin Law]

Public bug reported:

On a Xenial system upgraded (some time ago) from 15.10 Security &
Privacy is missing from System Settings.  I don't know whether it has
been missing since the upgrade or whether it disappeared more recently.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160216-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 10 17:06:59 2016
InstallationDate: Installed on 2014-10-21 (506 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to xenial on 2016-03-06 (4 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Security & Privacy missing from System Settings

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

Bug description:
  On a Xenial system upgraded (some time ago) from 15.10 Security &
  Privacy is missing from System Settings.  I don't know whether it has
  been missing since the upgrade or whether it disappeared more
  recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 10 17:06:59 2016
  InstallationDate: Installed on 2014-10-21 (506 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1555729/+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 1228567] Re: at-spi2 daemon error messages in .xsession-errors

[Colin Law]

@Cerin: I believe this bug has little impact.  If your machine is
unusable then it is likely a different problem.

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

Title:
  at-spi2 daemon error messages in .xsession-errors

Status in at-spi2-core package in Ubuntu:
  Fix Released

Bug description:
  Sometimes I get the following messages in .xsession-errors

  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd respawning too fast, stopped

  I use a Lenovo Thinkpad Twist convertible with touch screen, using
  Onboard in tablet mode.

  Can perhaps have a relation with bug 1227173.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1371928] Re: Main window content fully transparent

[Colin Law]

If using nvidia graphics then possibly this is related to compiz bug
#1072206

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

Title:
  Main window content fully transparent

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I launch Gimp, the main window is fully transparent
  with the exception of the normal frame (title bar, buttons, ...).

  The only way to fix the problem is to exit and restart Gimp.

  Ubutun 14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1371928/+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 1432317] Re: [systemd] should now depend on systemd/upstart, not upstart-bin

[Colin Law]

I am still seeing this in up to date Wily, with unity-greeter 15.10.1-0ubuntu1. 
 Should I still be seeing it?
upstart: upstart-event-bridge main process (1442) terminated with status 1
upstart: upstart-event-bridge respawning too fast, stopped

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

Title:
  [systemd] should now depend on systemd/upstart, not upstart-bin

Status in One Hundred Papercuts:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released

Bug description:
  Vivid now use systemd

  upstart-bin is still a dependency needed by unity-greeter
  (which is a transitional package since upstart now contains upstart-bin 
binaries.)

  unity-greeter might also use systemd to replace upstart

  .xsession-errors is now filed with:

  upstart: upstart-event-bridge main process (4982) terminated with status 1
  upstart: upstart-event-bridge main process ended, respawning

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-greeter 15.04.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Mar 15 10:56:10 2015
  SourcePackage: unity-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1432317/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Colin Law]

@va_crone  you have not told us which version you are using now.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1470748] Re: Corrupted displays when hot plugging second monitor

[Colin Law]

It seems this has been fixed so marking accordingly.

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

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

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

Title:
  Corrupted displays when hot plugging second monitor

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

Bug description:
  On up to date Wily running on a laptop, when a second monitor is hot
  plugged in, the image on the laptop monitor is cropped so only lower
  two thirds are visible and the second monitor shows a black screen
  with occasional flashes.

  If the machine is booted with both monitors connected the displays
  work as expected.

  Same setup works ok on Vivid.

  This report generated with the system in the error condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:34:19 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2015-07-01 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150609)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.8-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.8-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jul  2 08:25:52 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.17.1-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1470748/+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 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Colin Law]

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

Status in gedit package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Invalid

Bug description:
  Gedit crashed just after opening a (small) text file from nautilus
  with "Open with".

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1
  Uname: Linux 4.2.0-11-lowlatency x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Sep 25 16:05:28 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2014-12-13 (285 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gedit crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago)
  UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+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 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Colin Law]

Is bug #1499575 (gnucash crashed with SIGABRT in g_assertion_message())
which seems to have a similar stack top probably the same issue?  It is
causing gnucash to be completely unusable on Wily (for me anyway).

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

Status in gedit package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Gedit crashed just after opening a (small) text file from nautilus
  with "Open with".

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gedit 3.10.4-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1
  Uname: Linux 4.2.0-11-lowlatency x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Sep 25 16:05:28 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2014-12-13 (285 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gedit crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago)
  UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+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 1438128] Re: gedit crashed with SIGSEGV in gtk_action_group_get_action()

[Colin Law]

For me this happened when closing gedit.  One or more of the files had
changed in the background and I said to close without saving.  That may
or may not be significant.

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

Title:
  gedit crashed with SIGSEGV in gtk_action_group_get_action()

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  just opened two tabs with text in gedit

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gedit 3.10.4-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 13:36:37 2015
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2015-03-27 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcCmdline: gedit /home/username/Desktop/gpuintel
  SegvAnalysis:
   Segfault happened at: 0x7f8764f5796c :   
cmp%rax,0x0(%rbp)
   PC (0x7f8764f5796c) ok
   source "%rax" ok
   destination "0x0(%rbp)" (0x4) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   gtk_action_group_get_action () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gedit crashed with SIGSEGV in gtk_action_group_get_action()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1438128/+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 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@vedavata I imagine that it is because (according to comment #397 you
are using Xubuntu.  This bug is about Unity, where it has been fixed.
If you have a problem on Xubuntu you should file a bug for that or
extend this bug to Xubuntu.  I don't know what the appropriate package
on Xubuntu would be.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  
  
  

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of "misses" when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  "invisible" region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System >
  Preferences > Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1318863] Re: unity dash loses ability to search for applications

[Colin Law]

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

** This bug is no longer a duplicate of bug 1322864
   Sometimes the app search doesn't work in the Dash
** This bug has been marked a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

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

Title:
  unity dash loses ability to search for applications

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Every so often, about once a day (I haven't identified a trigger for this 
behaviour), the unity dash loses the ability to search for applications.  I can 
open the dash and type, say "firefox" and nothing shows up. Rebooting does not 
seem to fix the problem.  However if I type, as recommended here 
 (note this 
is a slightly different bug, I can still search for files and the like):
  rm ~/.local/share/zeitgeist/activity.sqlite
  unity --reset &

  Unity restarts and searches for things normally. Somewhat to my
  annoyance a lot of settings get lost, for instance the custom sizing
  of my launcher icons. Fortunately, I can keep working, but I'd like
  this problem to go away if possible.

  I am running Ubuntu 12.04
  Kernel 3.2.0-58-generic

  I am running the kernel released by siddhu in this bug report
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093217 because
  it fixes a problem where the computer hangs while booting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1318863/+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 1424744] Re: Dash don't find the applications

[Colin Law]

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

** This bug is no longer a duplicate of bug 1322864
   Sometimes the app search doesn't work in the Dash
** This bug has been marked a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

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

Title:
  Dash don't find the applications

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Sometimes, when i use the dash, its only find the files, not the
  application.  To fix it, i need to restart the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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 Feb 23 14:18:18 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:4140]
  InstallationDate: Installed on 2015-02-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: PHILCO 15A
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=ee87b79c-9da0-4561-b371-1f9ffefc1793 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: 15A
  dmi.board.vendor: PHILCO
  dmi.board.version: D02A
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/27/2011:svnPHILCO:pn15A:pvrNotApplicable:rvnPHILCO:rn15A:rvrD02A:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 15A
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PHILCO
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 23 11:58:47 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 592 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1424744/+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 1233079] Re: [xmir] Screen stops updating after unplugging second monitor

[Colin Law]

I am not seeing the problem in 15.10. Marking as invalid.

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

** Changed in: unity-system-compositor
   Status: Incomplete => Invalid

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [xmir] Screen stops updating after unplugging second monitor

Status in Mir:
  Invalid
Status in Unity System Compositor:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On unplugging the second monitor the remaining monitor flashes and
  seems to half update (half the launcher is shown with a white
  background) and the screen will not update further.  Switching to VT
  (ctrl alt F1) and back refreshes the screen, showing full launcher and
  wallpaper, but it will not update further.  I can't see any errors in
  the logs.  unity-system-compositor process is still running.

  I am running with the workaround for bug #1222602
  (MESA_GL_VERSION_OVERRIDE=1.4).

  The failure is consistent every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-system-compositor 0.0.1+13.10.20130926.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Mon Sep 30 11:07:53 2013
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:0240]
  InstallationDate: Installed on 2012-08-01 (424 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: unity-system-compositor
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.libdrm: libdrm2 2.4.46-1
  version.lightdm: lightdm 1.7.17-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1233079/+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 1295908] Re: Sometimes applications stop showing up in the Dash

[Colin Law]

I am still seeing it intermittently on 15.10.  See uploaded screenshot

** Attachment added: "Screenshot showing dash with nothing found"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295908/+attachment/4466827/+files/Screenshot%20from%202015-09-17%2013-56-18.png

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

** Changed in: unity (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Sometimes applications stop showing up in the Dash

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
   1. Open Dash
   2. Type a name of an application installed on your system, like "calculator"
   3. press escape

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

  How to fix it once it happens:
  A)type something and either hit escape or delete what you have typed.
  B)Check "application" in filters in the Dash (it gets unchecked)

  From the comments, it seems this might have something to do with
  people having online searches disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 21 19:12:19 2014
  InstallationDate: Installed on 2013-10-05 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-12-10 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295908/+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 1474182] Re: Mystery keyring password prompts pop up for no reason

[Colin Law]

I am also seeing this (on 15.04), it started happening a few weeks ago.
As suggested above it is associated with oneconf.  Immediately before
the popup appears (or as it appears) data in
.cache/oneconf//package_list_... and host are updated and after a
valid pwd is entered last_sync is updated.  In auth.log the following is
seen after entering the pwd

Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: completed password prompt for 
callback :1.96@/org/gnome/keyring/Prompt/p1
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: encrypting data
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: sending the secret exchange: 
[sx-aes-1]\npublic=[snipped]
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: calling the PromptReady method 
on /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: returned from the PromptReady 
method on /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: received PerformPrompt call 
from callback /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for 
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: closing the prompt
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for 
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for 
prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for 
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for 
prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for 
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for 
prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: calling the PromptDone on 
/org/gnome/keyring/Prompt/p1@:1.96, and ignoring reply
Aug 31 07:54:50 tigger gcr-prompter[]: 10 second inactivity timeout, 
quitting
Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: unregistering prompter
Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: disposing prompter
Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: finalizing prompter

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

Title:
  Mystery keyring password prompts pop up for no reason

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  A prompt box periodically pops up for no apparent reason asking me for
  my default keyring password.If I click Cancel, it re-appears again
  after a few minutes.  There is absolutely no information about what
  program is asking or why.   Is this a phishing scam?!?

  I'm marking this as "security vulnerability" because the "mystery"
  prompt is asking for extremely sensitive information which users
  should not give out without knowing what program will use it.

  * My homedir is not encrypted
  * I do use automatic login, but it succeeded and everything works, including 
network.
  * My system has slept/resumed a few times (don't know if that's relevant)
  * I use a wired Ethernet connection, not WiFi (so no password is needed for 
network access).
  * I am not running any commands that I know of which use encryption or 
require access to my private keys.

  Since I am  not doing anything which actually requires my private key,
  something is asking to unlock the keyring wrongly;

  Or else a background process (or trojan) is trying to communicate with
  somebody behind my back, using my private keys.

  This seems to be new (REGRESSION) as of 15.04, it did not occur before
  upgrading.

  The programs I *am* running are:
   *  Firefox
   * Thunderbird (I typed in it's Master Password previously, and it is working 
fine)
   *  Terminals
   *  A Java based web app (Interactive Brokers Trader Workstation)

  /var/log/auth.log contains the following:

  : Executing command [USER=root] [TTY=unknown] 
[CWD=/home/] [COMMAND=/usr/lib/update-notifier/package-system-locked]
  bus acquired: org.gnome.keyring.SystemPrompter
  Gcr: registering prompter
  bus acquired: org.gnome.keyring.PrivatePrompter
  Gcr: received BeginPrompting call from callback 
/org/gnome/keyring/Prompt/p22@:1.259
  Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p22@:1.259
  Gcr: creating new GcrPromptDialog prompt
  Gcr: automatically selecting secret exchange protocol
  Gcr: generating public key
  Gcr: beginning the secret exchange: 

[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work

[Colin Law]

@Edward Falk that is nothing to do with this bug, which is about custom
shortcuts added by the user.

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

Title:
  Custom keyboard shortcuts don't work

Status in gnome-control-center:
  New
Status in libxfce4ui:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in libxkbcommon package in Ubuntu:
  Confirmed

Bug description:
  Just noticed that adding custom keyboard shortcuts does not have any
  effect. If, for example, I add a custom keyboard shortcut for Evince
  and set it to Ctrl+Alt+E, pressing this key combination won't launch
  Evince.

  * What happens *
When I add a custom keyboard shortcut (and bind it to some key 
combination), the shortcut does not run the associated command.

  * What I expect *
After adding the custom shortcut, I expect that the shortcut launches the 
associated command.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  gnome-control-center:
Installed: 1:3.6.3-0ubuntu36
Candidate: 1:3.6.3-0ubuntu36
Version table:
   *** 1:3.6.3-0ubuntu36 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu36
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic i686
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: i386
  Date: Thu Sep 12 19:21:56 2013
  InstallationDate: Installed on 2013-08-31 (12 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+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 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@vedavrata this bug applies to Unity, and is effectively closed.  If you
are seeing a problem on Xubuntu then I suggest you file a new bug.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@Jeremy Huddleston, I see you are right, apologies (except that the fix
appeared only in Unity-3D, it was worse in Unity-2D than it was before
Unity-2D appeared).  Does Xubuntu use Metacity?  If not then my point is
still valid, that it would be best to file a new bug for Xubuntu if the
problem exists there, describing in detail exactly what the problem is.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in emerald:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in metacity:
  In Progress
Status in ubuntu-mate:
  Opinion
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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

[Colin Law]

It is fixed for me on Ubuntu 15.04 (and was on 14.10).  In System
Settings  Mouse  Touchpad I see Mouse Pointer Speed ok.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-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 Mouseid=10   [slave  
keyboard (3)]
  ↳ Dell Dell USB Keyboard  id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  and from lsusb:
  Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser 
Mouse SMWLL11]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 23 09:40:41 2013
  InstallationDate: Installed on 2012-08-01 (205 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+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 1470748] [NEW] Corrupted displays when hot plugging second monitor

[Colin Law]

Public bug reported:

On up to date Wily running on a laptop, when a second monitor is hot
plugged in, the image on the laptop monitor is cropped so only lower two
thirds are visible and the second monitor shows a black screen with
occasional flashes.

If the machine is booted with both monitors connected the displays work
as expected.

Same setup works ok on Vivid.

This report generated with the system in the error condition.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.3-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jul  2 08:34:19 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:17a9]
InstallationDate: Installed on 2015-07-01 (0 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150609)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=4ab50317-49e7-45c9-b675-d9391fbfd0e3 ro quiet splash
SourcePackage: unity
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
version.libdrm2: libdrm2 2.4.60-3
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.8-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.8-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Jul  2 08:25:52 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13890 
 vendor SEC
xserver.version: 2:1.17.1-0ubuntu4

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


** Tags: apport-bug compiz-0.9 i386 ubuntu wily

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

Title:
  Corrupted displays when hot plugging second monitor

Status in unity package in Ubuntu:
  New

Bug description:
  On up to date Wily running on a laptop, when a second monitor is hot
  plugged in, the image on the laptop monitor is cropped so only lower
  two thirds are visible and the second monitor shows a black screen
  with occasional flashes.

  If the machine is booted with both monitors connected the displays
  work as expected.

  Same setup works ok on Vivid.

  This report generated with the system in the error condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:34:19 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2015-07-01 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150609)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 

[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult

[Colin Law]

@Jluc I believe it has been long fixed and is not seen in 15.04 or
later.  As in the first paragraph of the bug description it will not be
fixed in Unity-2D.

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

Title:
  Resizing windows by grabbing window borders is difficult

Status in Ayatana Design:
  Fix Released
Status in Decorator for compiz-fusion:
  New
Status in One Hundred Papercuts:
  Fix Released
Status in The Metacity Window Manager:
  In Progress
Status in Release Notes for Ubuntu:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 2D:
  Invalid
Status in light-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug is fixed in unity-3d since ubuntu 11.04.
  It still exists in unity-2d and will never be fixed as unity-2d is no longer 
supported since ubuntu 12.10 (see comment #343).

  *

  This should mostly be fixed for Natty and might get backported to
  earlier releases as well.

  For Precise (12.04)  this is again broken for unity-2d (as of 17.7.2012 
unity-2d 5.12.0-0ubuntu1.1).
  Note that if the window has a scrollbar, you can grab that to resize the 
window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see 
comment 320)?

  *

  *Blueprint for Natty, Ubuntu 11.04:

  https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-
  dx-n-resizing-windows

  Work items1 * Make sure the new resize grip fits in current applications; 
doesn't interfere with anything. We should make some noise about this during 
the Natty cycle so people keep their eyes open and file bugs.
  2 * Invisible window resize area - around 3px invisible area to allow resize 
on all sides.

  *

  Working grip backported to gtk2 already available in ppa :
  https://launchpad.net/~bratsche/+archive/gtk

  *

  Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window
  most comfortably.

  Workaround:  Edit /usr/share/themes/Ambiance/metacity-1/metacity-
  theme-1.xml.  Set the following values in frame_geometry_normal as
  desired:

  distance name=left_width value=3/
  distance name=right_width value=3/
  distance name=bottom_height value=3/

  

  Binary package hint: metacity

  - The issue has been an issue for users (especially of large) screens
  for several releases- Trackpad users seem to be particularly impacted
  by this- The issue appears to have been significantly aggravated in
  Lucid by changing the border width from 3 pixels to 1 pixel

  The window borders in metacity are far too thin to be used for
  comfortable window resizing, and resize handles are not available in
  all applications (or even most). In fact, of all the windows I have
  open right now, not a single one of them has a resize handle. The
  result is that I get a lot of misses when I try to drag a window
  border, which usually results in my clicking on the wrong window
  altogether. The best fix for this usability bug is to create an
  invisible region around each non-maximized window about 4px thick
  that can be used for resizing (in addition to the visible border). Or
  perhaps there should be a border thickness option on the System 
  Preferences  Windows dialog (although the default thickness should
  still be increased considerably). Ideally all windows would also have
  a resize handle but I realize that these have to be application
  controlled (at least that seems to be the position of the metacity
  team).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

@Terry could you add yourself to 'affects me' so that it increases the
visibility.  Thanks.

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

Title:
  Laptop + external display does not suspend on lid close

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

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+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 1414420] Re: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

[Colin Law]

I get the unable to connect message about 10 secs after boot but no
further lightdm messages, and no obvious ill effect, so perhaps it is
unrelated to the PAM messages.  In fact the only lightdm messages I see
are:

$ grep -i lightdm /var/log/syslog
Apr  6 09:57:14 tigger kernel: [   10.835217] audit: type=1400 
audit(1428310634.471:2): apparmor=STATUS operation=profile_load 
profile=unconfined name=/usr/lib/lightdm/lightdm-guest-session pid=512 
comm=apparmor_parser
Apr  6 09:57:21 tigger lightdm[1449]: initctl: Unable to connect to Upstart: 
Failed to connect to socket /com/ubuntu/upstart: Connection refused

syslog contained the complete boot sequence, and more.

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

Title:
  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  That vivid system booted with systemd (systemd-sysv installed) have
  logged to journalctl:

  lightdm[1195]: initctl: Unable to connect to Upstart: Failed to connect to 
socket /com/ubuntu/upstart: Connection refused
  lightdm[1220]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  lightdm[1220]: PAM adding faulty module: pam_kwallet.so
  lightdm[1220]: pam_unix(lightdm-greeter:session): session opened for user 
lightdm by (uid=0)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 25 11:35:37 2015
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1414420/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

@Martin, could you clarify what is meant by dock events please?  Also exactly 
what you want me to do in the VT.
Currently if I switch to a VT and close the lid then as far as I can tell 
absolutely nothing happens apart from the laptop monitor switching off.  Under 
Unity  the external display briefly blanks and then comes back with windows 
that were on the laptop moved to the external display, so it is switching to 
single monitor mode.

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

Title:
  Laptop + external display does not suspend on lid close

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

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

More evidence, of a rather confusing nature.
With default /etc/systemd/logind.conf (which has everything commented out).

With only the laptop display
Unity and VT both suspend ok when lid is closed

With laptop display + external display
Neither Unity nor VT suspend when lid is closed.


With HandleLidSwitchDocked=suspend in /etc/systemd/logind.conf

With only the laptop display
Unity and VT both suspend ok when lid is closed

With laptop display + external display
Unity does not suspend the first time the lid is closed, but does the second, 
in fact it suspends every second time the lid is closed (though not absolutely 
sure this is completely consistent).  I think once it was not till the third 
time that it suspended.
VT suspends ok when lid is closed.

This is software so there is some sense there somewhere.   It is just a
matter of finding it.

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

Title:
  Laptop + external display does not suspend on lid close

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

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

Which .desktop file is the one that should be in the launcher?  In 
/usr/share/applications I have three which have Name=Files:
nautilus.desktop
nautilus-folder-handler.desktop
org.gnome.Nautilus.desktop

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

I am still seeing a second nautilus icon opening in the launcher.
$ apt-cache policy unity
unity:
  Installed: 7.3.2+15.04.20150330-0ubuntu1
  Candidate: 7.3.2+15.04.20150330-0ubuntu1
  Version table:
 *** 7.3.2+15.04.20150330-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

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

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

On a vivid which was originally updated from Trusty and is up to date I created 
a new user (via System Settings  User Accts) and logged in as that user.  
Clicking on Files opens a new icon in the launcher.
The desktop file the system has put in the launcher is 
org.gnome.Nautilus.desktop

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

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

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

I am pretty sure that a couple of years ago the gnome guys decided that the 
laptop should not suspend if an external monitor is plugged in (which was a 
change to the previous strategy).  I think that by popular request this was 
reverted back to suspend (possibly only in Ubuntu, I don't know).  I am sure 
there was a bug for this but I can't find it.  Now it has apparently changed 
again.
I can see that for some it makes sense to not suspend, but for those who use 
the laptop in a dock with both displays active it is annoying to have to use 
the menus to suspend.  I would have thought it more appropriate to have the 
default stay as it has been for many years.  Ideally there could be an 
additional option in the settings to allow a choice of lid closure actions when 
there are two displays.  Currently the option is to suspend or not.  It does 
not say suspend, but only if there is no external display connected.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

For clarity I am not actually using a dock, I just have the external
monitor plugged in to the laptop, and it does not suspend when I close
the lid.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+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 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

I am still seeing the problem when connected via wifi (Ok on wired).

Adding After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section appears to
fix it.

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

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 945482] Re: Loud hiss on audio converting mp4 to mpg with avconv or ffmpeg

[Colin Law]

The problem is no longer seen with up to date 14.04 or 15.04

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

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

Title:
  Loud hiss on audio converting mp4 to mpg with avconv or ffmpeg

Status in the libav multimedia framework:
  New
Status in libav package in Ubuntu:
  Fix Released

Bug description:
  Using avconv on up to date Precise.
  Converting mp4 (downloaded using get-iplayer but I don't know whether this is 
significant) using the command
  avconv -i test.mp4 -target pal-dvd test.mpg
  yields a file with audio that is mostly hiss, with an undercurrent of the 
audio underneath.  The terminal o/p is:

  $ avconv -i test.mp4 -target pal-dvd test.mpg
  avconv version 0.8-4:0.8-1ubuntu2, Copyright (c) 2000-2011 the Libav 
developers
built on Feb  9 2012 08:21:31 with gcc 4.6.2
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x9a54260] multiple edit list entries, a/v desync 
might occur, patch welcome
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4':
Metadata:
  major_brand : isom
  minor_version   : 512
  compatible_brands: isomiso2avc1mp41
  encoder : Lavf53.20.0
  media_type  : 10
  copyright   : � 2012 British Broadcasting Corporation, all rights 
reserved
  title   : Rugged Wales
  artist  : BBC One
  album_artist: BBC TV
  album   : Rugged Wales
  composer: BBC iPlayer
  genre   : Factual
  comment : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  date: 2012-03-01T20:00:00Z
  description : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  show: Rugged Wales
  episode_id  : b01cywyz
  network : BBC One
Duration: 00:58:58.16, start: 0.00, bitrate: 1502 kb/s
  Stream #0.0(und): Video: h264 (Main), yuv420p, 832x468 [PAR 117:117 DAR 
16:9], 1401 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
  Stream #0.1(und): Audio: aac, 48000 Hz, stereo, s16, 94 kb/s
  [buffer @ 0x9a59f00] w:832 h:468 pixfmt:yuv420p
  [scale @ 0x9a59d60] w:832 h:468 fmt:yuv420p - w:720 h:576 fmt:yuv420p 
flags:0x4
  Incompatible sample format 's16' for codec 'ac3', auto-selecting format 'flt' 
  - possibly significant  -|
  Output #0, dvd, to 'test.mpg':
Metadata:
  major_brand : isom
  minor_version   : 512
  compatible_brands: isomiso2avc1mp41
  network : BBC One
  media_type  : 10
  copyright   : � 2012 British Broadcasting Corporation, all rights 
reserved
  title   : Rugged Wales
  artist  : BBC One
  album_artist: BBC TV
  album   : Rugged Wales
  composer: BBC iPlayer
  genre   : Factual
  comment : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  date: 2012-03-01T20:00:00Z
  description : Iolo Williams explores some of the best wild and 
industrial landscapes in Wales.
  show: Rugged Wales
  episode_id  : b01cywyz
  encoder : Lavf53.20.0
  Stream #0.0(und): Video: mpeg2video, yuv420p, 720x576 [PAR 64:45 DAR 
16:9], q=2-31, 6000 kb/s, 90k tbn, 25 tbc
  Stream #0.1(und): Audio: ac3, 48000 Hz, stereo, flt, 448 kb/s
  Stream mapping:
Stream #0:0 - #0:0 (h264 - mpeg2video)
Stream #0:1 - #0:1 (aac - ac3)
  Press ctrl-c to stop encoding
  Input stream #0:1 frame changed from rate:48000 fmt:s16 ch:2 to rate:48000 
fmt:flt ch:2
  [mpeg2video @ 0x9a57420] rc buffer underflow
  ^Cframe=  123 fps= 32 q=2.0 Lsize=2360kB time=4.74 bitrate=4082.2kbits/s 
dup=4 drop=0
  video:2042kB audio:259kB global headers:0kB muxing overhead 2.574681%
  Received signal 2: terminating.

  If I add the option -acodec ac3_fixed then the sound is ok, so
  possibly it is a problem with ac3 codec.

  The problem is not seen on an earlier version of ffmpeg.

  I can provide a sample mp4 file showing the problem if necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libav-tools 4:0.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  Date: Sat Mar  3 09:43:31 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 
(2029.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1422466] Re: Nautilus window not being matched to launcher icon in Ubuntu 15.04

[Colin Law]

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

But with version 3.14.2-0ubuntu6  bookmarks no longer appear when the
launcher is right clicked.  See bug #1436297 for a further workaround
for that.

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

Title:
  Nautilus window not being matched to launcher icon in Ubuntu 15.04

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of
  bringing up the current window.

  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.

  WORKAROUND: Add to the end of the [Desktop Entry] section of 
/usr/share/applications/nautilus.desktop the line
  StartupWMClass=nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1422466/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

A workaround for the missing bookmarks is to is to unlock the nautilus shortcut 
from the launcher and instead drag across 
/usr/share/applications/nautilus.desktop and lock that to the launcher (in the 
files view of that folder three items show as Files, it is the one that is 
about 600 bytes long that is wanted).  Then to fix the duplicate icon problem 
add to the end of the [Desktop Entry] section of that file the line
StartupWMClass=nautilus

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

Unfortunately this fix has resulted in the loss of the right click
bookmarks feature of the nautilus icon in the launcher.  For me at
least.

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

Having tried with wifi connection (was previously wired) I also still
see the problem if connected via wifi.

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

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

[Colin Law]

Is the fact that WPA Supplicant has been stopped significant?

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network{, -online}.target

[Colin Law]

Great, is it as simple as adding
Before=network-online.target network.target
to Unit section of /lib/systemd/system/NetworkManager.service?

Having tried it that does appear to fix the problem (including the
problem with the init script in the duplicate bug, where it was timing
out on a umount command).

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

Title:
  cifs mount hangs on shutdown - NetworkManager needs to stop after
  network{,-online}.target

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 1422466] Re: Nautilus window not being matched to launcher icon in Ubuntu 15.04

[Colin Law]

** Description changed:

  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of bringing
  up the current window.
  
  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.
+ 
+ WORKAROUND:  Move away the file
+ /usr/share/applications/org.gnome.Nautilus.desktop
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nautilus window not being matched to launcher icon in Ubuntu 15.04

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of
  bringing up the current window.

  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.

  WORKAROUND:  Move away the file
  /usr/share/applications/org.gnome.Nautilus.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1422466/+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 1422466] Re: Nautilus window not being matched to launcher icon in Ubuntu 15.04

[Colin Law]

** Description changed:

  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of bringing
  up the current window.
  
  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.
+ 
+ WORKAROUND: Add to the end of the [Desktop Entry] section of 
/usr/share/applications/nautilus.desktop the line
+ StartupWMClass=nautilus
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nautilus window not being matched to launcher icon in Ubuntu 15.04

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of
  bringing up the current window.

  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.

  WORKAROUND: Add to the end of the [Desktop Entry] section of 
/usr/share/applications/nautilus.desktop the line
  StartupWMClass=nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1422466/+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 1292560] Re: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

[Colin Law]

** Tags added: vivid

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

Title:
  unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I booted the system and got this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 14 11:03:04 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0b5c9ae583 malloc_consolidate+307:   cmp
0x18(%rax),%rbx
   PC (0x7f0b5c9ae583) ok
   source 0x18(%rax) (0x7f0b5ccee7e80018) not located in a known VMA region 
(needed readable region)!
   destination %rbx ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f0b5ccee760 main_arena) at malloc.c:4157
   _int_malloc (av=av@entry=0x7f0b5ccee760 main_arena, 
bytes=bytes@entry=1056) at malloc.c:3423
   __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3219
   pa_xmalloc0 () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_hashmap_new () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
  Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to trusty on 2013-12-06 (97 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1292560/+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 1422466] Re: Nautilus window not being matched to launcher icon in Ubuntu 15.04

[Colin Law]

** Description changed:

  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of bringing
  up the current window.
  
  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.
- 
- WORKAROUND:  Move away the file
- /usr/share/applications/org.gnome.Nautilus.desktop
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nautilus window not being matched to launcher icon in Ubuntu 15.04

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of
  bringing up the current window.

  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1422466/+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 1422466] Re: Nautilus window not being matched to launcher icon in Ubuntu 15.04

[Colin Law]

Note that in order to see this it is necessary to /drag/ the application from 
the dash into the launcher, not open it.  The situation is also seen on the 
default install.
What seems to be happening is that the launcher icon is the file 
/usr/share/applications/nautilus.desktop, but when this is clicked it brings up 
in the launcher /usr/share/applications/org.gnome.Nautilus.desktop
It is important that the one in the launcher is nautilus.desktop as this is the 
one that gets populated with bookmarks for right click.

In order to see what is happening it is helpful to edit the desktop
files and change the Name= line in each so they can be distinguished in
the launcher.

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

Title:
  Nautilus window not being matched to launcher icon in Ubuntu 15.04

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  When I click on the Nautilus launcher icon in the Unity taskbar, it
  creates another icon for the window. Repeated clicks on the original
  launcher icon will just spawn more Nautilus windows instead of
  bringing up the current window.

  Steps to reproduce:
  1.) Drag Nautilus launcher from Applications to taskbar.
  2.) Click on launcher.
  3.) Notice that another Nautilus icon appears on the taskbar for the window, 
instead of being matched with the original icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bamfdaemon 0.5.1+15.04.20150202-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 16 11:04:30 2015
  InstallationDate: Installed on 2015-01-20 (27 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150119)
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1422466/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

In terms of the kernel version I don't know exactly as I do not suspend
very often, but I never saw the problem before upgrade from Utopic.  I
have just tried booting into a live Utopic image which was the release
candidate on 17th Oct 14 and uname shows 3.16.0-22 and it suspends ok
there.  Perhaps it is not purely a kernel issue.

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

In fact I see from my bug #1384454 that Utopic with kernel 3.16.0-23 and
with 3.18.0-031800rc1 both suspended ok with external screen (though
they did suffer from windows moving workspaces as in that bug).

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

It is the same situation with v3.16-utopic.  Closing the lid with ext
monitor connected causes windows to move to ext monitor but does not
suspend.

I have discovered another symptom that may possibly be related.  With
any of the kernels and with the external monitor not connected, closing
the lid does nothing during the first four minutes after booting.  After
that time it suspends ok (ext monitor not connected).  If closed during
first four minutes then nothing happens, but if left closed it does
suspend after that time has elapsed.  Since discovering this I have gone
back and checked the other kernels again and waited till it will suspend
with no ext monitor and re-confirmed that it does not suspend with the
ext monitor connected.

As a matter of interest are others seeing suspend ok with external
monitor?

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Since update to Vivid, laptop does not suspend on lid close if an external 
monitor is connected, even though suspend is selected in the power settings for 
lid close. The display flashes and apps move to external display. Syslog shows 
no attempt to suspend. On Utopic it suspended ok with external monitor. In the 
logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are 
messages in syslog at that time but I suspect they may be a different issue:
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment

  WORKAROUND: Suspend via the menu.

  WORKAROUND: Disconnect external monitor first.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415958/+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 1415958] Re: Laptop + external display does not suspend on lid close

[Colin Law]

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

Bug still present with BIOS version 1.19

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

** This bug has been marked a duplicate of bug 1426123
   Laptop does not suspend on lid close when external monitor connected

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

Title:
  Laptop + external display does not suspend on lid close

Status in xorg package in Ubuntu:
  New

Bug description:
  Running up to date Vivid on laptop with external display, closing the
  lid does not suspend even though suspend is selected in the power
  settings for lid close.  The display flashes and apps move to external
  display.  Syslog shows no attempt to suspend.

  With no external display connected the laptop suspends as expected.

  In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30
  There are messages of the form
  i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  in syslog at that time but I suspect they may be a different issue.

  Not sure whether xorg is the correct package for this, hopefully
  someone will redirect if appropriate.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  Uname: Linux 3.18.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 29 15:04:52 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:17a9]
  InstallationDate: Installed on 2014-12-27 (33 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.17
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan 29 15:00:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.16.2.901-1ubuntu3

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