[Bug 1697131] [NEW] ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

[Jacob de Lange-Hope]

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

Public bug reported:

After installing Ubuntu 17.04 and updating this occurs every time.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 10 15:20:55 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-10 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697131] Re: ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1695514] Re: Gnome shell 3.24 Gnome extensions not installing

[Jeremy Bicha]

This bug report is being closed due to your last comment that you can no
longer reproduce this issue. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

Next time, maybe try moving the extensions directory instead of deleting
it so that it could possibly be used to diagnose the issue.

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

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

Title:
  Gnome shell 3.24 Gnome extensions not installing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696849] Re: Ability to disable Hot Corner

[Nikita Yerenkov-Scott]

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

Yes, you're right, sorry, I'm just so used to using the bugzilla
interface now which only allows one affected product per bug.

** This bug has been marked a duplicate of bug 1543099
   Option to disable Hot Corner

** Summary changed:

- Ability to disable Hot Corner
+ Ability in gnome-shell to disable Hot Corner

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

Title:
  Ability in gnome-shell to disable Hot Corner

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697080] Re: gnome-shell crashed with signal 5 in _XIOError()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893274/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893276/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893280/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893281/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893282/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893283/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697080/+attachment/4893284/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697079] [NEW] glib/glib-autocleanups.h missing from package

[mike-g2]

Public bug reported:

I am trying to install R 3.3.1 from source, but it fails due to a lack
of the header file

/usr/include/glib-2.0/glib/glib-autocleanups.h

This file is found in later versions of the libglib2.0-dev but not in
version libglib2.0-dev 2.40.2-0ubuntu1 for 14.04.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1697079

Title:
  glib/glib-autocleanups.h missing from package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1697079/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

[Steve Langasek]

We believe this is most likely a duplicate of bug #1682499 which was
fixed in systemd 232-21ubuntu3.  If you can still reproduce this problem
after upgrading to the zesty-updates version of systemd, please reopen.

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

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

[Brian Murray]

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

[Dennis Carlstrom]

Here is an apport file following a 4 minute period of the window manager
being unresponsive!

** Attachment added: "bug.apport2"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/977744/+attachment/4893227/+files/bug.apport2

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Brian Murray]

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Also affects: network-manager (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd (Ubuntu Artful)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Confirmed

** Tags removed: rls-aa-incoming

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

[Dennis Carlstrom]

I've noticed a condition for this bug on my system.  It only happens
when the terminal window is vertically maximized.

Steps to reproduce:

1. open terminal
2. vertically maximize
3. resize horizontally (drag window edge)

Expected behaviour:

- terminal window resizes (contents re-flow live)

Actual behaviour:

- window manager becomes unresponsive for 10-60 seconds


Distro: Ubuntu 16.04.2 LTS
gnome-terminal: 3.18.3-1ubuntu1

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 977744] Re: resizing gnome-terminal windows to a bigger size take a uge time

[Launchpad Bug Tracker]

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

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

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

Title:
  resizing gnome-terminal windows to a bigger size take a uge time

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697062] Re: gnome-shell crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893198/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893200/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893204/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893205/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893206/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893207/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1697062/+attachment/4893208/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1689863
   gnome-shell crashed with SIGSEGV in 
js::GCMethods::needsPostBarrier()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in g_main_context_dispatch()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696395] Re: gnome-control-center crashed with SIGSEGV in um_carousel_select_item()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-control-center crashed with SIGSEGV in um_carousel_select_item()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 696435] Re: wait-for-root fails to detect nbd root

[ChristianEhrhardt]

Checking the issue that was referred shows it was handled and fixed in
1. Kernel 
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd 
230 which also means part of >=Yakkety.

I'm filing bug tasks for systemd and kernel to check and maybe consider
for Xenial

** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu)

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

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

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

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

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

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

** No longer affects: nbd (Ubuntu Xenial)

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

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

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

Title:
  wait-for-root fails to detect nbd root

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697052] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697052] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Chandan Kumar Rath]

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

Public bug reported:

crashed during software update

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed Jun  7 06:06:58 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-06 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1681242] Re: gnome-shell crashed with signal 5 in _XIOError()

[Launchpad Bug Tracker]

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

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

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

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

Title:
  gnome-shell crashed with signal 5 in _XIOError()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1502476] Re: Totem menubar is displayed in fullscreen mode during gnome-flaskback session

[CenterTest]

same problem on Ubuntu Studio 16.10

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

Title:
  Totem menubar is displayed in fullscreen mode during gnome-flaskback
  session

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1686393] Re: [MIR] gdm3

[Launchpad Bug Tracker]

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

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

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

Title:
  [MIR] gdm3

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1690182] Re: Update gnome-shell to 3.24.2

[Łukasz Zemczak]

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

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

Title:
  Update gnome-shell to 3.24.2

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1672175] Re: gnome-shell should recommend chrome-gnome-shell

[Łukasz Zemczak]

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety

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

Title:
  gnome-shell should recommend chrome-gnome-shell

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697006] Re: Gnome-shell "Power Off" dialog does not have focus

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome-shell "Power Off" dialog does not have focus

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697006] [NEW] Gnome-shell "Power Off" dialog does not have focus

[Cubic PPA]

Public bug reported:


The gnome-shell "Power Off" dialog does not have focus when activated.
As a result, the user has to click twice to select an action:
- The first click is to give the dialog focus.
- The second click is to actually make a selection.


RECREATE ISSUE:

1. Click the "power button" icon at the top right of the Gnome-shell task bar.
2. Select the "Power button" icon.
3. The screen darkens, and the "Power Off" dialog is displayed, showing three 
options/buttons:
   Cancel, Restart, and Power Off.
4. Hover over the three buttons, and notice the buttons do not highlight on 
hover. [ISSUE]
5. Click an option, for example "Restart."
6. Notice that nothing happens (there are no visual indicators that the dialog 
did not have focus, and now has focus). [ISSUE]
7. Hover over the three buttons, and notice the buttons now *DO* highlight on 
hover.
8. Click an option, for example "Cancel."
9. Since the "Power Off" dialog now has focus (from step 6) the click action is 
handled.


DESIRED BEHAVIOR:

1. Click the "power button" icon at the top right of the Gnome-shell task bar.
2. Select the "Power button" icon.
3. The screen darkens, and the "Power Off" dialog is displayed, showing three 
options/buttons:
   Cancel, Restart, and Power Off.
4. The "Power Off" dialog *SHOULD* have focus.
5. Hover over the three buttons, and *DO* highlight on hover.
6. Click an option, for example "Restart," the click action is handled.


SYSTEM INFORMATION

Distribution: Ubuntu Gnome

$ gnome-shell --version
GNOME Shell 3.24.1

$ uname -a
Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

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

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

Title:
  Gnome-shell "Power Off" dialog does not have focus

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1695742] Re: Fn keys recognised but not handled after 17.04 upgrade

[Donjan Rodic]

Update: the Unity session as well as the sessions from the packages 
ubuntu-mate-desktop and cinnamon-desktop correctly handle all Fn keys.
I'm stuck with Cinnamon for now.

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

Title:
  Fn keys recognised but not handled after 17.04 upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1695253] Re: Archive Manager hangs Mouse clicks

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1695253

Title:
  Archive Manager hangs Mouse clicks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1695253/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696970] [NEW] softlockup DoS causes systemd-journald.service to abort with SIGABORT

[Colin Ian King]

Public bug reported:

I was running the new stress-ng softlockup stressor and observed that
systemd-journald gets killed with an abort and this corrupts the systemd
journal.

How to reproduce:

git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make clean; make

sudo ./stress-ng --softlockup 0 -t 360 -v

..and wait for 360 seconds.  dmesg shows the following, 100%
reproduceable:


[  875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 
3min)!
[  875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 
(systemd-timesyn) with signal SIGABRT.
[  875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, 
code=killed, status=6/ABRT
[  875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed state.
[  875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 
'watchdog'.
[  875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off 
time, scheduling restart.
[  875.327954] systemd[1]: Stopped Network Time Synchronization.
[  875.328845] systemd[1]: Starting Network Time Synchronization...
[  875.525071] systemd[1]: Started Network Time Synchronization.
[  875.539619] systemd[1]: systemd-journald.service: Main process exited, 
code=dumped, status=6/ABRT
[  875.544257] systemd-journald[5214]: File 
/run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or 
uncleanly shut down, renaming and replacing.

** Affects: systemd (Ubuntu)
 Importance: High
 Status: New

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

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

Title:
  softlockup DoS causes systemd-journald.service to abort with SIGABORT

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696952] [NEW] Touchpad doesn't recoginze input when hw button is pressed

[Steffen Schuhmann]

Public bug reported:

My touchpad doesn't recoginze any input when the the hardware button
(underneath the touchpad) is presssed.

My Laptop model is a xiaome 12.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jun  9 11:29:41 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-06-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Touchpad doesn't recoginze input when hw button is pressed

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696945] [NEW] Ubuntu's red close button is too far left in Gnome Shell (Ambiance and Radiance)

[Daniel van Vugt]

Public bug reported:

Ubuntu's red close button is too far left in Gnome Shell (Ambiance and
Radiance)

Although this is only a problem in client-side decorated titlebars (the
thick ones like in Nautilus and Settings)

** Affects: ubuntu-themes
 Importance: Undecided
 Status: New

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gnome-shell (Ubuntu) => ubuntu-themes (Ubuntu)

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Description changed:

  Ubuntu's red close button is too far left in Gnome Shell (Ambiance and
  Radiance)
+ 
+ Although this is only a problem in client-side decorated titlebars (the
+ thick ones like in Nautilus and Settings)

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

Title:
  Ubuntu's red close button is too far left in Gnome Shell (Ambiance and
  Radiance)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696929] Re: X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy

[Bug Watch Updater]

** Changed in: libinput
   Status: Unknown => Confirmed

** Changed in: libinput
   Importance: Unknown => Medium

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

Title:
  X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused

[Łukasz Zemczak]

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  Gnome on-screen keyboard doesn't appear when a text field is focused

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1690938] Re: Allow lightdm to be an alternate recommends for gdm3

[Łukasz Zemczak]

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  Allow lightdm to be an alternate recommends for gdm3

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1684205] Re: Screen lock button missing when using LightDM

[Łukasz Zemczak]

** Tags removed: verification-done
** Tags added: verification-done-xenial verification-done-yakkety 
verification-done-zesty

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

Title:
  Screen lock button missing when using LightDM

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696929] Re: Laptop touchpads are unresponsive (with hysteresis enabled by default)

[Daniel van Vugt]

See also:
https://bugs.freedesktop.org/show_bug.cgi?id=98839
https://bugs.freedesktop.org/show_bug.cgi?id=94986

Hmm, if blacklisting or writing custom configs is the solution then
maybe this bug should be hardware-specific.

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

** Summary changed:

- Laptop touchpads are unresponsive (with hysteresis enabled by default)
+ X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy

** Description changed:

  Some laptop touchpads are annoyingly unresponsive when the software
  implements any kind of hysteresis. This includes Lenovo X1 Carbon gen 4
  and 5. Such devices have lower precision and higher lag in the touchpad
  hardware than you might expect, so need the software to not slow them
  down further.
  
  The problem now is that using libinput by default slows down all
  touchpads and makes them less precise. For hardware that was already
  unresponsive, introducing software that further reduces the
  responsiveness is very frustrating, borderline unusable.
  
  When we were using Xorg the simple solution was to adjust hysteresis
  with 'synclient'. However now we're using Wayland we're stuck with
- libinput and I don't know how to fix it any more. Even Xorg logins don't
- seem to use libinput now, so there's no 'synclient' workaround available
+ libinput and I don't know how to fix it any more. Even Xorg logins seem
+ to use libinput now, so there's no 'synclient' workaround available
  there anymore either.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libinput10 1.6.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun  9 14:52:18 2017
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  SourcePackage: libinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696929] Re: Laptop touchpads are unresponsive (with hysteresis enabled by default)

[Daniel van Vugt]

An interesting test is to move your finger around in small circles on
the touchpad. If the hysteresis is too high then you will see the cursor
move in a more square-like shape.

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

Title:
  Laptop touchpads are unresponsive (with hysteresis enabled by default)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696929] [NEW] Laptop touchpads are unresponsive (with hysteresis enabled by default)

[Daniel van Vugt]

Public bug reported:

Some laptop touchpads are annoyingly unresponsive when the software
implements any kind of hysteresis. This includes Lenovo X1 Carbon gen 4
and 5. Such devices have lower precision and higher lag in the touchpad
hardware than you might expect, so need the software to not slow them
down further.

The problem now is that using libinput by default slows down all
touchpads and makes them less precise. For hardware that was already
unresponsive, introducing software that further reduces the
responsiveness is very frustrating, borderline unusable.

When we were using Xorg the simple solution was to adjust hysteresis
with 'synclient'. However now we're using Wayland we're stuck with
libinput and I don't know how to fix it any more. Even Xorg logins don't
seem to use libinput now, so there's no 'synclient' workaround available
there anymore either.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libinput10 1.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
Date: Fri Jun  9 14:52:18 2017
InstallationDate: Installed on 2017-06-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
SourcePackage: libinput
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libinput
 Importance: Unknown
 Status: Unknown

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

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


** Tags: amd64 apport-bug artful

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

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

** Description changed:

  Some laptop touchpads are annoyingly unresponsive when the software
- implements any kind of hysteresis. This include Lenovo X1 Carbon gen 4
+ implements any kind of hysteresis. This includes Lenovo X1 Carbon gen 4
  and 5. Such devices have lower precision and higher lag in the touchpad
- hardware than you might expect so need the software to not slow them
+ hardware than you might expect, so need the software to not slow them
  down further.
  
  The problem now is that using libinput by default slows down all
  touchpads and makes them less precise. For hardware that was already
  unresponsive, introducing software that further reduces the
  responsiveness is very frustrating, borderline unusable.
  
  When we were using Xorg the simple solution was to adjust hysteresis
  with 'synclient'. However now we're using Wayland we're stuck with
  libinput and I don't know how to fix it any more. Even Xorg logins don't
  seem to use libinput now, so there's no 'synclient' workaround available
  there anymore either.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libinput10 1.6.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun  9 14:52:18 2017
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  SourcePackage: libinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  Laptop touchpads are unresponsive (with hysteresis enabled by default)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs