[Bug 1741928] Re: Automatic time zone not working

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  Automatic time zone not working

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

> Do you have a keyboard backlight at all? Or an external keyboard
plugged in?

Yes my keyboard has some automatic backlight

> What does your journalctl output say after that? Can you paste it
here?

Will attach the full output, I think the culprit is:

janv. 10 07:54:48 hephaistos gnome-session[2639]: gnome-session-binary[2639]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de 
l’appel de StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente 
est dépassé
janv. 10 07:54:48 hephaistos gnome-session-binary[2639]: CRITICAL: Unable to 
create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de 
StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente est dépassé
janv. 10 07:54:48 hephaistos gnome-screensav[2776]: Couldn't get presence 
status: The name org.gnome.SessionManager was not provided by any .service files
janv. 10 07:54:48 hephaistos dbus-daemon[2632]: Successfully activated service 
'org.gnome.ScreenSaver'

Thanks for your help :)

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1741928] Re: Automatic time zone not working

[Daniel van Vugt]

Ah yes. It appears that issue has already been reported:
https://bugzilla.gnome.org/show_bug.cgi?id=788714

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

** Package changed: gnome-shell (Ubuntu) => gnome-control-center
(Ubuntu)

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

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

Title:
  Automatic time zone not working

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

Full output of journactl, the freeze is between janv. 10 07:54:23 and
janv. 10 07:54:48

** Attachment added: "journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+attachment/5034104/+files/output.txt

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1741928] Re: Automatic time zone not working

[shankao]

That solved the problem, but... shouldn't the automatic timezone option
be grayed out or warn about it not working when Location Services is
turned off?

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

Title:
  Automatic time zone not working

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

I don't know how the KbdBackLight interface is meant to work. It seems
to be defined in package 'upower'. And that error seems to be from code
in unity-settings-daemon where it fails to change the keyboard backlight
brightness, because something isn't implementing "SetBrightness". And
even then, the error only seems to occur when unity-settings-daemon
changes to GSD_POWER_IDLE_MODE_BLANK. So I wouldn't expect that to be
related to logging in, probably.

Do you have a keyboard backlight at all? Or an external keyboard plugged
in?

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

Actually, no it's not related. You say your problem is with gnome-shell
logins and the above is about Unity7 only...

Please try:
 1. sudo apt install openssh-server
 2. Log in from a second machine via ssh, and run: journalctl -f
 3. On the original machine log in locally and reproduce the freeze.
 4. What does your journalctl output say after that? Can you paste it here?

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

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

Hi Daniel,

Thanks for the analysis, can I do something by myself to prevent that
delay?

Regards

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

HI Da

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

[Daniel van Vugt]

Judging by all the duplicate bugs and the global error reports
(https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7),
this particular bug stopped happening with the introduction of gnome-
shell version 3.26.1.

So if you continue to experience any problems, please open new bugs.

** Changed in: mutter (Ubuntu)
 Assignee: Sam Spilsbury (smspillaz) => (unassigned)

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

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

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Derek L]

Is an SRU fixing this likely to get pushed to artful?  It bites me
several times a week (it's filling my syslog with errors as I write
this).

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

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

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

[Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

[Po-Hsu Lin]

Tested with Bionic Daily build image, gnome-shell 3.26.2
this issue still exist.

** Tags added: artful bionic

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

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

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

[Bug 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

[Daniel van Vugt]

I'm really not sure we're linking to the right upstream bugs still, or
that we've captured all the right error reports from errors.ubuntu.com.

Possibly this is related and is in progress:
https://bugzilla.gnome.org/show_bug.cgi?id=72

As for Ubuntu crash reports, the only link we have suggests this
particular crash in meta_window_is_on_primary_monitor universally
stopped happening after artful gnome-shell version 3.26.0-0ubuntu2, and
never happened in bionic:

https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

So _if_ this is the right bug for us to be commenting on then we
probably need to find a different but similar error report. Otherwise
we're all commenting on the wrong bug right now.

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

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

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

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

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

[Bug 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

[Rocko]

So is there any progress on this? I can't use gnome-shell because of it,
even with Ubuntu 18.04.

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

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

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

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

[Bug 1741843] Re: caribou (gnome-shell osk): special characters not working

[Bug Watch Updater]

** Changed in: caribou
   Status: Unknown => In Progress

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

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

Title:
  caribou (gnome-shell osk): special characters not working

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

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

[Bug 1709135] Re: add bond primary parameter

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Bug 1712921] Re: enabling networkd appears to eat up entropy

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Bug 1717471] Re: networkd does not accept / set advertised mtu

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.04.1

---
nplan (0.32~17.04.1) zesty; urgency=medium

  * Backport 0.32 to 17.04. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not
configured; this follows the same logic as setting IPv6AcceptRA=no in
networkd, with the exception that NM does not currently disable RAs. When
it does, an unconfigured device for IPv6 will truly be left with no config.

nplan (0.24) artful; urgency=medium

  * debian/control: set Priority to important to make sure we can get into
minimal.

 -- Mathieu Trudel-Lapierre   Thu, 16 Nov 2017
10:43:28 -0500

** Changed in: nplan (Ubuntu Zesty)
   Status: Fix 

[Bug 1717471] Re: networkd does not accept / set advertised mtu

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Bug 1741843] Re: caribou (gnome-shell osk): special characters not working

[Daniel van Vugt]

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

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

** Changed in: caribou
 Remote watch: GNOME Bug Tracker #777468 => GNOME Bug Tracker #604585

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

Title:
  caribou (gnome-shell osk): special characters not working

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

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

[Bug 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct_label_box()

[Daniel van Vugt]

This issue is also being tracked in:
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc

** Description changed:

+ https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc
+ 
+ ---
+ 
  gnome-shell-portal-helper crashed with SIGABRT
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 17:19:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  InstallationDate: Installed on 2017-06-08 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  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/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  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/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

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

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

[Bug 1742339] Re: gnome-shell crashed with signal 5

[Daniel van Vugt]

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

** This bug is no longer a duplicate of private bug 1742278
** 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"]

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

Title:
  gnome-shell crashed with signal 5

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

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

[Bug 1742344] [NEW] /usr/lib/gnome-shell/gnome-shell-portal-helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic

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

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-
  
helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Daniel van Vugt]

Yes, sorry about that. I experience the same on my development machine.
I have no idea why that's happening.

Suggestion: Remove the two empty files *.upload and *.uploaded and then
in a terminal re-upload the existing crash file:

  ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

That will take a minute or two to complete but then you will be directed
either to an existing bug report, or asked to make a new one. Either
way, please let us know here what web page you end up with.

When I say "directed" I mean that ubuntu-bug will print a link for you
to copy and paste.

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1742344] Re: /usr/lib/gnome-shell/gnome-shell-portal-helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1726156
   gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from 
construct_label_box()

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

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-
  
helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

[Daniel van Vugt]

Great. But just a warning; 17.04 reaches end of life this month:
https://wiki.ubuntu.com/Releases

So you will need to upgrade again soon. If you're using gnome-shell then
we recommend 17.10 right now. And before May 2018 we will have 18.04
ready too.

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

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1742339] Re: gnome-shell crashed with signal 5

[Apport retracing service]

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

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 #1742278, 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/1742339/+attachment/5033979/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1742278

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

Title:
  gnome-shell crashed with signal 5

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

Your log shows an 11 second delay each time this happens:

Nov 06 13:57:46 hostname gnome-session-binary[3428]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
Nov 06 13:57:57 hostname unity-settings-[3399]: failed to turn the kbd 
backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface 'org.freedesktop.UPower.KbdBacklight' on object at path 
/org/freedesktop/UPower/KbdBacklight

and

Nov 06 15:38:07 hostname gnome-session-binary[3428]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
Nov 06 15:38:18 hostname unity-settings-[3399]: failed to turn the kbd 
backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface 'org.freedesktop.UPower.KbdBacklight' on object at path 
/org/freedesktop/UPower/KbdBacklight

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

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

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

[Bug 1739625] Re: Mouse events pass through pure Wayland windows (that use wl_shell)

[Daniel van Vugt]

The fix has landed upstream. It's due for release in mutter 3.26.3 ...
https://git.gnome.org/browse/mutter/commit/?h=gnome-3-26=294cceaeb8ecfd468132eff8af1f75c9d60ff21d

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

Title:
  Mouse events pass through pure Wayland windows (that use wl_shell)

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

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

[Bug 1742310] [NEW] No network in recovery mode (systemd-resolved does not start)

[Lastique]

Public bug reported:

When booting into recovery mode and enabling networking, networking does
not get enabled. DNS lookup doesn't work because systemd-resolved does
not start and /etc/resolv.conf is a broken symlink.

Steps to reproduce:

1. Reboot.
2. In the grub menu, select "Advanced options for Ubuntu" and then select boot 
in recovery mode.
3. When the menu appears, select "networking". In the console you may notice a 
few errors that /etc/resolv.conf file not found.
4. Select "drop to root" console.
5. Try pinging some hosts, like "ping ubuntu.com". You will see that name 
resolution doesn't work.
6. You can check that the network interface is up, "ip addr" displays valid 
info and the interface has an assigned local IP.
7. You can check that /etc/resolv.conf is in fact a dangling link to 
../run/resolvconf/resolv.conf.
8. You can see that systemd-resolved is not running: "systemctl status 
systemd-resolved" shows the service is dead.
9. Invoking "systemctl start systemd-resolved" hangs indefinitely, the service 
not starting.

The workaround to get DNS working is to replace /etc/resolv.conf with a
valid link or a file with a DNS server.

The DNS lookup and networking in general works fine if the system is
booted normally.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jan 10 02:18:14 2018
InstallationDate: Installed on 2015-05-01 (984 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
SourcePackage: systemd
SystemdDelta:
 [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

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

Title:
  No network in recovery mode (systemd-resolved does not start)

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

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

[Bug 1732012] Re: After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen

[Jonathan Avraham]

Thanks for your input, Daniel, but I just easily reproduced it (just
flip the input source bach and forth, no need to even turn the TV off)
and no crash file was created. /var/crash only has 4 crash files, none
of which are from today.

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

Title:
  After turning display (LCD TV) off and then back on, session ends and
  Ubuntu goes back to the logon screen

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

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

[Bug 1742288] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_array()

[Apport retracing service]

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

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 #1710770, 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/1742288/+attachment/5033796/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1710770

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

Title:
  gvfsd-smb-browse crashed with SIGABRT in _talloc_array()

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

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

[Bug 1742287] Re: gvfsd-mtp crashed with SIGSEGV

[Apport retracing service]

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

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 #1706097, 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/1742287/+attachment/5033782/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

[fermulator]

since upgrading to Ubuntu 17.04, I'm unable to reproduce the crash any
longer FYI.

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1741588] Re: Categories in Ubuntu Software don't work

[Robert Ancell]

Thanks for the clarification!

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

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

Title:
  Categories in Ubuntu Software don't work

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

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

[Bug 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct_label_box()

[Apport retracing service]

** Tags added: bionic

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

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

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

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

[Bug 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct_label_box()

[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/1726156

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

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

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

[Bug 1742268] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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 #1726156, 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/1742268/+attachment/5033674/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1726156
   gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from 
construct_label_box()

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

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message()

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

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

[Bug 1741588] Re: Categories in Ubuntu Software don't work

[dmiller309]

Polarr is a Snap, but the bug I intended to report here is that on
16.04, none of the items in the category list display or are clickable.
The screenshot attached to the original bug report illustrates the
problem. I couldn't say for sure whether Polarr is in the list or not
because each of the apps display as a box with an ellipsis inside: no
icon or text. One weird thing I when switching between categories is
that none of the items in the list for each category render or are
clickable, but there are different amounts of items in each category. I
know I had an internet connection because I was on a video call.

During a demo of the new Polarr Snap I was asked whether the Polarr Snap
is in the Software Store and if it showed up under the Graphics
category. I could bring up Polarr by searching for it directly. It was
kind of embarrassing though when none of the categories in the store
worked. We link our existing users to our snapcraft.io/polarr page, but
we're not featured, the categories were broken on 16.04, and we don't
show up under categories on 17.10, so there is currently no way for new
users to find Polarr in the Software Store.

Thanks for your patience, I know that y'all have a lot of work to do
with all the new Snaps coming out. I've seen categories in the Software
Store work before and maybe this is just a temporary regression; I just
wanted to share this in case you weren't aware of the problem.

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

Title:
  Categories in Ubuntu Software don't work

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

Hi Sebastien,

I think https://bugzilla.gnome.org/show_bug.cgi?id=706688 could be used
as the upstream bug.

Regards

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

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1742250] [NEW] Adding and deleting a veth leaks a systemd unit

[Shaun Crampton]

Public bug reported:

When I add a veth device:

sudo ip link add name test1 type veth

I see these systemd units appear:

systemctl list-units --all | grep test

 sys-devices-virtual-net-test1.device
 loadedactive   plugged   /sys/devices/virtual/net/test1

 sys-subsystem-net-devices-test1.device
 loadedactive   plugged   /sys/subsystem/net/devices/test1

However, if I then delete the veth:

sudo ip link del dev test1

Then only one of the units is removed:

systemctl list-units --all | grep test

  sys-devices-virtual-net-test1.device
 loadedactive   plugged   /sys/devices/virtual/net/test1

This is a big problem when running, for example, a Kubernetes cluster
since each pod creation/deletion leaks a systemd unit.  When enough have
been leaked, systemd becomes unresponsive and the system is broken until
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
Date: Tue Jan  9 18:57:34 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y 
console=ttyS0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google

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


** Tags: amd64 apport-bug artful uec-images

** Description changed:

  When I add a veth device:
  
- sudo ip link add name test1 type veth
+ sudo ip link add name test1 type veth
  
  I see these systemd units appear:
  
- systemctl list-units --all | grep test
- smc-kubeadm-node-0: Tue Jan  9 19:02:41 2018
+ systemctl list-units --all | grep test
  
-  sys-devices-virtual-net-test1.device
-  loadedactive   plugged   /sys/devices/virtual/net/test1
+  sys-devices-virtual-net-test1.device
+  loadedactive   plugged   /sys/devices/virtual/net/test1
  
-  sys-subsystem-net-devices-test1.device
-  loadedactive   plugged   /sys/subsystem/net/devices/test1
+  sys-subsystem-net-devices-test1.device
+  loadedactive   plugged   /sys/subsystem/net/devices/test1
  
  However, if I then delete the veth:
  
- sudo ip link del dev test1
+ sudo ip link del dev test1
  
  Then only one of the units is removed:
  
- systemctl list-units --all | grep test
- smc-kubeadm-node-0: Tue Jan  9 19:03:53 2018
+ systemctl list-units --all | grep test
  
-   sys-devices-virtual-net-test1.device
-  loadedactive   plugged   /sys/devices/virtual/net/test1
+   sys-devices-virtual-net-test1.device
+  loadedactive   plugged   /sys/devices/virtual/net/test1
  
  This is a big problem when running, for example, a Kubernetes cluster
  since each pod creation/deletion leaks a systemd unit.  When enough have
  been leaked, systemd becomes unresponsive and the system is broken until
  reboot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Tue Jan  9 18:57:34 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

Title:
  Adding and deleting a veth leaks a systemd unit

To manage 

[Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Norbert]

Problem with `nemo` "Open as Root" is confirmed on 18.04.

** Tags added: bionic

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

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

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

[Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Norbert]

synaptic confirmed on 18.04.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

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

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

[Bug 1739762] Re: Search list starts from beginning after going back to it

[Bug Watch Updater]

** Changed in: gnome-software
   Status: Unknown => Confirmed

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

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

Title:
  Search list starts from beginning after going back to it

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

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

[Bug 1739762] Re: Search list starts from beginning after going back to it

[Amr Ibrahim]

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

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

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

Title:
  Search list starts from beginning after going back to it

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

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

[Bug 1742143] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

Public bug reported:

it happened during an upgrade from 17.10 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Tue Jan  9 13:39:24 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2014-07-23 (1265 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 3138
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha5
SourcePackage: systemd
Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
dmi.bios.date: 08/30/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0FC0K2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 3138
dmi.sys.vendor: Dell Inc.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package bionic rls-bb-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/1742143

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

@Daniel

The above commands do bring me to a web-page, but there are no uploaded
relevant error reports, although I see them in /var/crash

** Attachment added: "/var/crash screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+attachment/5033441/+files/20180108_ls_var_crash.png

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1739849] Re: Logging into snap installer fails with GDBus / Polkit error

[Salvolupo-g]

A workaround is to install snap by command line as it doesn't require logging. 
sudo snap install snap-name

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

Title:
  Logging into snap installer fails with GDBus / Polkit error

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

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

[Bug 1742127] Re: gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()

[Apport retracing service]

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

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 #1735858, 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/1742127/+attachment/5033395/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1735858

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

Title:
  gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()

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

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

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Maraschin]

more info: my current setup has 4 monitors running with 2560x1440

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

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

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Maraschin]

Hi, I'm running ubuntu 17.10 with gnome 3.26.2

I noticed today that every time I press the "windows" key it consumes
about 5 MB extra and just keeps growing ...

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

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

[Bug 1739849] Re: Logging into snap installer fails with GDBus / Polkit error

[Launchpad Bug Tracker]

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

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

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

Title:
  Logging into snap installer fails with GDBus / Polkit error

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

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

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   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/1716432

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

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

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

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

[Didier Roche]

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

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

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

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

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

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

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-shell/ubuntu

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

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

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

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

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

[Didier Roche]

** Changed in: gnome-shell (Ubuntu)
   Status: Opinion => Fix Committed

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

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

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

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

[Bug 1732012] Re: After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen

[Daniel van Vugt]

Next time this problem occurs, please look in /var/crash for .crash
files. If any are found then please upload them using this command only:

  ubuntu-bug /var/crash/YOURFILE.crash

And then add a comment in this bug telling us the newly-created bug ID.

** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  After turning display (LCD TV) off and then back on, session ends and
  Ubuntu goes back to the logon screen

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

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

[Bug 1732012] [NEW] After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

TV is an old Toshiba LCD connected via HDMI. Problem first appeared
after upgrade to Artful.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,imgpng,obs,gnomecompat,vpswitch,regex,resize,move,place,mousepoll,animation,grid,workarounds,session,wobbly,fade,cube,rotate,expo,scale,unitymtgrabhandles,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 21:56:50 2017
DistUpgraded: 2017-10-21 11:42:55,395 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-38-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] 
[1002:964a] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6530D] 
[1458:d000]
InstallationDate: Installed on 2012-05-29 (1994 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-D2H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=ce7c3cb8-c699-4b71-8e50-d1a46484f917 ro quiet splash
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-10-21 (23 days ago)
dmi.bios.date: 11/03/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-A75M-D2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-D2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 18 21:11:02 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful ubuntu wayland-session
-- 
After turning display (LCD TV) off and then back on, session ends and Ubuntu 
goes back to the logon screen
https://bugs.launchpad.net/bugs/1732012
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1740146] Re: System slow on wayland, lagging mouse and programs on 17.10 & 18.04

[Daniel van Vugt]

** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)

** Tags added: performance

** Also affects: mutter (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/1740146

Title:
  System slow on wayland, lagging mouse and programs on 17.10 & 18.04

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

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

[Bug 1725180] Re: xwayland animations are not smooth

[Daniel van Vugt]

It sounds like you're referring to gnome-shell and not Xwayland.

** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- xwayland animations are not smooth
+ Shell animations are not smooth

** Tags added: performance

** Also affects: mutter (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/1725180

Title:
  Shell animations are not smooth

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

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

[Bug 1740146] [NEW] System slow on wayland, lagging mouse and programs on 17.10 & 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 18.04 development branch @ 26/12/2017

Overall system is lagging when opening programs and mouse, not smooth to work 
with
on gnome and the default wayland session, the xorg session is fast without 
lags. Tested the same machine on 17.10 and have same issues.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 26 17:15:16 2017
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6290] [1025:0598]
InstallationDate: Installed on 2017-12-18 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
Lsusb:
 Bus 002 Device 002: ID 0402:7675 ALi Corp.
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer AO722
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE10-BZ
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
dmi.product.family: Type1Family
dmi.product.name: AO722
dmi.product.version: V1.08
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.89-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu wayland-session
-- 
System slow on wayland, lagging mouse and programs on 17.10 & 18.04
https://bugs.launchpad.net/bugs/1740146
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1725180] [NEW] xwayland animations are not smooth

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

+++UBUNTU RELEASE+++

Description:Ubuntu 17.10
Release:17.10

+++PACKAGE VERSION+++

xwayland:
  Installed: 2:1.19.5-0ubuntu2
  Candidate: 2:1.19.5-0ubuntu2
  Version table:
 *** 2:1.19.5-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently
using Intel HD Graphics 630 as Nvidia seems to have no support for
xwayland.

The window/dock/launcher animations are lagging/shaky (not smooth).


__

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 19:09:27 2017
DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed
 v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed
 v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2017-05-24 (149 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug artful possible-manual-nvidia-install ubuntu 
wayland-session
-- 
xwayland animations are not smooth
https://bugs.launchpad.net/bugs/1725180
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1723815] Re: Unable to show files on MTP connection

[Alexxz]

Any news here? I'm experiencing the same issue. Opening directory with
150 files takes half a minute. Opening directory with 3000 files is
something endless. Ubuntu 17.10 and 2 Android devices Galaxy S7.

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

Title:
  Unable to show files on MTP connection

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

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

[Bug 1741632] Re: FW update error: could not find thunderbolt device

[Matthieu JOOSSEN]

Same issue, here

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

Title:
  FW update error: could not find thunderbolt device

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

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