[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

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

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

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

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

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Incomplete
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Incomplete
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully 

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

Hopefully a maintainer there will be able to give a better opinion as to
what's going on here

** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

** Also affects: dbus via
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It 

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

Thanks! Here's where I think the problem starts:

Ok, let's authenticate to dbus:

Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state HELLO → RUNNING

Right, systemd thinks it's done it at least. You can see a whole bunch
of messages being returned, the connection is working.

After a while (note this first timestamp jump; is that significant?
looks to be waiting for udev to settle I think so maybe not; could be
snapd related) we decide to do something with a Type=dbus unit:

Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner 
cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a

And another timestamp jump, waiting for this timeout:

Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: 
[system] Connection has not authenticated soon enough, closing it 
(auth_timeout=3ms, elapsed: 45129ms)
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a 
interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a 
error-message=n/a

The dbus-daemon didn't think that the connection was authenticated.

The last message AFAICS received on the bus connection was:

Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_call sender=n/a destination=org.freedesktop.systemd1 
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager 
member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading.

No smoking gun yet, at least not to me. But interesting that the last
thing which happened successfully was reloading. Can we have another go
please, with these changes vs. an upstream clean image?

  - LogLevel=debug in /etc/systemd/system.conf
  - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. 
This dbus is just the one from impish backported to hirsute with verbose 
debugging turned on.
  
And then attach the full `journalctl -b ` which will 
probably be quite large. :-)

Maybe we'll get some information out of the dbus side to say what it
thinks goes wrong with the connection.

** Please note ** The "connection has not authenticated" string does not
appear in the earlier logs from Christian or Steve. It could be that
there are two bugs here, with similar symptoms that systemd loses its
connection to the system bus.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?

It's going to be next to impossible for me to look into this in detail
without being able to reproduce it or getting a bit more debug
information.

Maybe you could crank up the system log level and try to reproduce this?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel 

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)

My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops responding to systemd, and so when it calls
GetNameOwner() to be able to watch type=dbus units, it gets no reply and
then decides to kill all type=dbus units, which is a lot of things. If
that's right, it's most likely to be a dbus bug that it can get into
this state. But I'm personally at a bit of a loss as to how to approach
it without being able to reproduce.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: 

[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Iain Lane]

Right. It's in the library. Programs will remain using the versions of
the libraries that were on the system when they started, so that means
that you need to upgrade, reboot, and *then* try the restart. I should
update the QA steps to make that more clear, will do.

** Description changed:

  [ Description ]
  
  When accountsservice's daemon is restarted - particularly when there is
  a user configured for auto login - it can cause code using its library
  to crash. This is bad because gnome-shell is one of those users which
  crashes.
  
  [ QA ]
  
  Configure a user for automatic login in gnome-shell.
+ 
+ Update to this SRU, and then *restart your system*. The crash is in the
+ library part, and so you will still see it if programs loaded the buggy
+ version. Restarting is the easiest way to make sure you're not on it.
  
  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.
  
  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.
  
  ---
  
  Test that fast user switching still works properly.
  
  ---
  
  Take a look at the error reports listed below and hopefully see them not
  occurring (barring the usual noise) with the SRU.
  
  [ Regression potential ]
  
  We think this is safe - it tells clients that the daemon is away when it
  quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when they
  weren't before now, so that could cause problems. Watch out for errors
  creeping up with this SRU.
  
  We wondered upstream whether some more protections might be needed. I'm
  thinking that those should be *additional* safety rails around this fix,
  but it could actually be that more is needed and this fix isn't
  complete.
  
  [ Original report ]
  
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think 

[Dx-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Iain Lane]

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

It's not a regression. It is in fact the same bug happening one last
time. I just explained it in the other bug, hope that's clear.

(If I'm not understanding right, please un-dupe and re-open this bug.)

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1878611

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

Status in accountsservice package in Ubuntu:
  New

Bug description:
  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
  point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

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

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

[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Iain Lane]

Okay, I've uploaded a fix to groovy and the review queue for 20.04.

** Description changed:

+ [ Description ]
+ 
+ When accountsservice's daemon is restarted - particularly when there is
+ a user configured for auto login - it can cause code using its library
+ to crash. This is bad because gnome-shell is one of those users which
+ crashes.
+ 
+ [ QA ]
+ 
+ Configure a user for automatic login in gnome-shell.
+ 
+ Restart accounts-daemon.service (sudo systemctl restart accounts-
+ daemon.service) a few times, leaving several seconds between each
+ attempt.
+ 
+ See that it crashes if you don't have this SRU, and doesn't if you do
+ have it.
+ 
+ ---
+ 
+ Test that fast user switching still works properly.
+ 
+ ---
+ 
+ Take a look at the error reports listed below and hopefully see them not
+ occurring (barring the usual noise) with the SRU.
+ 
+ [ Regression potential ]
+ 
+ We think this is safe - it tells clients that the daemon is away when it
+ quits, and is back when it comes back. They should get appropriate
+ signals to indicate this. Nevertheless, these signals are sent when they
+ weren't before now, so that could cause problems. Watch out for errors
+ creeping up with this SRU.
+ 
+ We wondered upstream whether some more protections might be needed. I'm
+ thinking that those should be *additional* safety rails around this fix,
+ but it could actually be that more is needed and this fix isn't
+ complete.
+ 
+ [ Original report ]
+ 
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  

[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Iain Lane]

** Also affects: accountsservice (Ubuntu Focal)
   Importance: High
 Assignee: Iain Lane (laney)
   Status: Triaged

** Changed in: accountsservice (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Dx-packages] [Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators

[Iain Lane]

** Description changed:

+ [ Description ]
+ 
+ When gnome-shell-extension-appindicator is installed and in use, and
+ indicator-application is also in use, there is a race condition that
+ means that Ubuntu sessions might not show any appindicators. They each
+ try to claim a bus name, and only one thing may own the same bus name at
+ a time.
+ 
+ [ QA ]
+ 
+ 1. Install indicator-application.
+ 2. Enter an Ubuntu GNOME Shell session
+ 3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
+ 4. Make sure it displays
+ 5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.
+ 
+ [ Fix ]
+ 
+ Don't run indicator-application on ubuntu sessions.
+ 
+ [ Regression potential ]
+ 
+ If someone has a different session called 'ubuntu' then this will stop
+ indicator-application running for them.
+ 
+ [ Original description ]
+ 
  On an Ubuntu 18.10 system, the dropbox icon would not show in the system
  tray panel. After searching the internet and trying various fixes (which
  did not work as expected) I came across a link which said indicator-
  application should be removed. I removed it along with the indicator-
  applet app and things are working fine!.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-application in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1819103

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  In Progress
Status in indicator-application source package in Bionic:
  In Progress
Status in indicator-application source package in Cosmic:
  In Progress

Bug description:
  [ Description ]

  When gnome-shell-extension-appindicator is installed and in use, and
  indicator-application is also in use, there is a race condition that
  means that Ubuntu sessions might not show any appindicators. They each
  try to claim a bus name, and only one thing may own the same bus name
  at a time.

  [ QA ]

  1. Install indicator-application.
  2. Enter an Ubuntu GNOME Shell session
  3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
  4. Make sure it displays
  5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.

  [ Fix ]

  Don't run indicator-application on ubuntu sessions.

  [ Regression potential ]

  If someone has a different session called 'ubuntu' then this will stop
  indicator-application running for them.

  [ Original description ]

  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators

[Iain Lane]

Thanks. I think I understand the fix. I'll upload for
disco/cosmic/bionic now and hopefully the new packages will resolve the
issue.

** Also affects: indicator-application (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: indicator-application (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: indicator-application (Ubuntu)
   Status: New => In Progress

** Changed in: indicator-application (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: indicator-application (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: indicator-application (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: indicator-application (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: indicator-application (Ubuntu Cosmic)
 Assignee: (unassigned) => Iain Lane (laney)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-application in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1819103

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  In Progress
Status in indicator-application source package in Bionic:
  In Progress
Status in indicator-application source package in Cosmic:
  In Progress

Bug description:
  [ Description ]

  When gnome-shell-extension-appindicator is installed and in use, and
  indicator-application is also in use, there is a race condition that
  means that Ubuntu sessions might not show any appindicators. They each
  try to claim a bus name, and only one thing may own the same bus name
  at a time.

  [ QA ]

  1. Install indicator-application.
  2. Enter an Ubuntu GNOME Shell session
  3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
  4. Make sure it displays
  5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.

  [ Fix ]

  Don't run indicator-application on ubuntu sessions.

  [ Regression potential ]

  If someone has a different session called 'ubuntu' then this will stop
  indicator-application running for them.

  [ Original description ]

  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators

[Iain Lane]

** Branch linked: lp:~laney/indicator-application/no-autostart-
ubuntu-18.04

** Branch linked: lp:~laney/indicator-application/no-autostart-ubuntu

** Branch linked: lp:~laney/indicator-application/no-autostart-
ubuntu-18.10

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-application in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1819103

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  New

Bug description:
  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

They're all uploaded now. To the SRU team - these are quite delicate
SRUs. I think they're right, but more eyes would be appreciated.

The essence is that when nux-tools is removed-not-purged at a buggy
version, the leftover conffile is harmful. So we picked a core package,
x11-common, and made it stash the conffile away. Then nux-tools will
pick it up if it's reinstalled and upgrade it to the fixed version in
the normal way.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  In Progress
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

> Well, I just wanted to make sure this happened as early as possible,
since this is not related to what the package installs, I thought it was
better to handle this in preinst, so that this can be also just removed
at later times.

The thing about the preinst is that it runs super early, you can't even
rely on the package's dependencies being installed. In this case we
don't use any non-Essential tools, so it's OK, but often this is a
problem. We don't *need* to use the preinst, since either the pkg is
removed or not removed before we even start installing x11-common - at
postinst time it's going to still be removed or it's going to get
upgraded to the fixed version.

There's a bug in x11-common. If the preinst check triggers twice (like
on a xenial dist-upgrade and then again when you upgrade to bionic), the
upgrade fails:

Preparing to unpack .../x11-common_1%3a7.7+19ubuntu7.1_all.deb ...
Moving obsolete conffile /etc/X11/Xsession.d/50_check_unity_support to 
/etc/X11/Xsession.d/50_check_unity_support.x11-back...
mv: cannot stat '/etc/X11/Xsession.d/50_check_unity_support': No such file or 
directory
dpkg: error processing archive 
/var/cache/apt/archives/x11-common_1%3a7.7+19ubuntu7.1_all.deb (--unpack):
 new x11-common package pre-installation script subprocess returned error exit 
status 1
Errors were encountered while processing:
 /var/cache/apt/archives/x11-common_1%3a7.7+19ubuntu7.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Fixed that by adding a [ -f ] check, and then I made the same fixes as
on the MP, expanded the changelog a bit, and uploaded to the silo (3299)
for all releases. Please check my diffs - particularly the versions.

Could you add some testcases for this please? Like

 - remove nux-tools from bionic-release (pre-sru), upgrade, reinstall nux-tools 
(no prompt)
 - remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall 
nux-tools (no prompt)
 - modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
 - install nux-tools, upgrade, no prompt

You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
its new contents or you are asked what to do if you've changed it
before. Never the old content.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

Cheers!

My nux-tools review comments apply to x11-common too. The following are
for x11-common:

What's the reason for doing this in preinst rather than postinst
configure? It's fine in this case but usually we do things in postinst
where possible.

What about adding a "Breaks: nux-tools (<<
4.0.8+18.04.20180613.5-0ubuntu1)" to x11-common, and making the script
not do the fix up if we're upgrading from the new version ("if dpkg
--compare-versions "${2}" lt 1:7.7+19ubuntu8; then do stuff; fi")?

I think it's a good idea generally to make fix up actions in maintainer
scripts strictly limited to certain package versions and this will mean
if you still have nux-tools installed you have to upgrade it to the
fixed version, so the removal can only have happened earlier than
x11-common 1:7.7+19ubuntu8.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

Marco, I don't think there is a solution that satisfies all the
requirements and doesn't involve nux cooperating in some way. I've given
you mostly-working debdiffs now - can we please move forward with them?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

This is the solution that I proposed to you in private. It is a fix to
mesa (a "common" package) and a followup to nux-tools.

It needs some testing. In particular I don't think I picked the right
mesa package to use, and we also need to check with the mesa maintainer.
There are various version numbers in there that need to be correct for
the target release.

A basic test worked OK though (libegl1-mesa is because I had it in an
even more wrong package at the time). Remove nux-tools, broken conffile
is left around, upgrade mesa, it's fixed, install new nux-tools and it's
installed with the right content and no prompt:

root@nux-tools-test:~# apt remove nux-tools
...
root@nux-tools-test:~# ls /etc/X11/Xsession.d/50_check_unity_support 
/etc/X11/Xsession.d/50_check_unity_support
root@nux-tools-test:~# sudo apt full-upgrade
...
Broken /etc/X11/Xsession.d/50_check_unity_support and removed nux-tools found, 
moving aside...
root@nux-tools-test:~# sudo apt install nux-tools
Found saved /etc/X11/Xsession.d/50_check_unity_support.mesa-save file, moving 
it back in place...
Unpacking nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ...
Setting up nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ...
Installing new version of config file 
/etc/X11/Xsession.d/50_check_unity_support ...
root@nux-tools-test:~# cat /etc/X11/Xsession.d/50_check_unity_support
# This file is sourced by Xsession(5), not executed.
# If the hardware does not pass unity_support_test, fall back to LLVMpipe
# which does.

if [ "x$DESKTOP_SESSION" = "xubuntu" ] && [ -x 
"/usr/lib/nux/unity_support_test" ]; then
(
IFS=':'
for d in $XDG_CURRENT_DESKTOP; do
if [ "x$d" = "xUnity" ] || [ "x$d" = "xUnity7" ]; then
return 0
fi
done
return 1
)

if [ $? = 0 ]; then
/usr/lib/nux/unity_support_test || export LIBGL_ALWAYS_SOFTWARE=1
fi
fi

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

** Patch added: "mesa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152448/+files/mesa.debdiff

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

** Patch added: "nux.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152447/+files/nux.debdiff

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

I'm adding a mesa task, as this bug also needs to be fixed for people
who *already* removed the package without purging it. I suggest mesa,
because that's the package that LIBGL_ALWAYS_SOFTWARE=1 acts on
(mostly?) - so fixing it there will fix for everybody whereas ubuntu-
desktop or whatever might miss some people. But it's a matter for Marco
and the mesa maintainers really.

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

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mesa (Ubuntu Artful)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mesa (Ubuntu Xenial)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  In Progress
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  In Progress
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  In Progress

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

(you can reassign that task from mesa to something else if it's going to
be fixed elsewhere)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  In Progress
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  In Progress
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  In Progress

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Iain Lane]

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

** Also affects: nux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nux (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: nux (Ubuntu Xenial)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux (Ubuntu Artful)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: nux (Ubuntu Artful)
 Assignee: Iain Lane (laney) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: nux (Ubuntu)
Milestone: ubuntu-18.04.1 => None

** Changed in: nux (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  In Progress
Status in nux source package in Artful:
  In Progress
Status in nux source package in Bionic:
  In Progress

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Iain Lane]

** Also affects: gnome-session (Ubuntu Bionic)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: Triaged

** Also affects: dconf (Ubuntu Bionic)
   Importance: High
   Status: Triaged

** Also affects: d-conf (Ubuntu Bionic)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: Triaged

** Also affects: session-migration (Ubuntu Bionic)
   Importance: High
 Assignee: Didier Roche (didrocks)
   Status: Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to d-conf in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1735929

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Triaged
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Triaged
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

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

[Dx-packages] [Bug 1718254] Re: please drop url-dispatcher dependencies

[Iain Lane]

Not sure desktop is going to have time to work on this for 17.10.

** Tags added: rls-aa-notfixinf

** Tags removed: rls-aa-notfixinf
** Tags added: rls-aa-notfixing

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1718254

Title:
  please drop url-dispatcher dependencies

Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in unity-greeter-session-broadcast package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  New
Status in indicator-datetime source package in Artful:
  New
Status in indicator-network source package in Artful:
  New
Status in indicator-power source package in Artful:
  New
Status in indicator-sound source package in Artful:
  New
Status in unity-greeter-session-broadcast source package in Artful:
  New
Status in unity-scopes-api source package in Artful:
  New

Bug description:
  please drop url-dispatcher dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1718254/+subscriptions

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

[Dx-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

** Changed in: libunity-webapps (Ubuntu)
   Status: Expired => Triaged

** Changed in: oxide-qt (Ubuntu)
   Status: Expired => Triaged

** Changed in: webbrowser-app (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: libunity-webapps (Ubuntu)
   Importance: Undecided => Medium

** Changed in: oxide-qt (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Triaged
Status in oxide-qt package in Ubuntu:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions

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

[Dx-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

Moving from bug #1649310

On Thu, May 04, 2017 at 08:02:57PM -, Steve Langasek wrote:
> On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> > Notable things not listed:
> >  * oxide/webbrowser app, still in use for amazon "app"
>·
> What pulls in the amazon app?  I have heard that oxide is definitively not
> on the supported list for 17.10+.

It's /usr/share/applications/ubuntu-amazon-default.desktop, so...

  application://ubuntu-amazon-default.desktop is in Unity's favourites 
  by default

and the chain is

 unity-webapps-service -> webapp-container -> webbrowser-app

I heard that we need to keep this, so if it is confirmed that Oxide, the
web browser and the Unity webapps are to be removed, then we will need
to provide this in another way. The desktop team will do that. (An
initial implementation might just be opening a new tab in Firefox.)

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libunity-webapps (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

** Changed in: libunity-webapps (Ubuntu)
   Status: New => Incomplete

** Changed in: oxide-qt (Ubuntu)
   Status: New => Incomplete

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions

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

[Dx-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

Initially assigning xnox, but feel free to move that.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions

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

[Dx-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Iain Lane]

We think this is an undisclosed ABI break and we'll rebuild for it (in a
silo) to see if that works.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Triaged

** Changed in: indicator-datetime (Ubuntu)
   Importance: Medium => High

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1681870

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870/+subscriptions

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

[Dx-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name

[Iain Lane]

Huh, it seems like the new icon is actually shipped by Nautilus itself.
So symlinks in adwaita-icon-theme doesn't make sense. The rest of my
point still stands.

I think a-i-t and h-i-t are good now, so I will upload them.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1669655

Title:
  Adapt to new Nautilus icon name

Status in humanity-icon-theme package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system-
  file-manager for better flatpak compatibility.

  I have updated ubuntu-themes and humanity-icon-theme for this change
  (adding a new symlink pointing to system-file-manager).

  ubuntu-themes is handled via bileto so I'll ask the appropriate people
  to sponsor that separately. DONE

  I pushed my change to the humanity bzr branch but I don't have upload rights 
for it so I'll need sponsorship for this:
  https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/

  I let other Ubuntu flavors know about this change at bug 1669663.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+subscriptions

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

[Dx-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name

[Iain Lane]

I am trying to tell you to be less aggressive in the changes you're
pushing into Ubuntu, especially after feature freeze.

I don't think that making it easier to maintain a PPA is a good reason
to risk bugs in the release proper and to take up a fair amount of
reviewer time. We do not, and will not, have Nautilus 3.24 in Zesty and
so we shouldn't be having discussions about making other packages work
with it.

With symlinks in adwaita-icon-theme I was suggesting a way you could
update that to 3.24 but keep Nautilus at 3.20, thinking that might have
been your goal (not making Humanity work with Nautilus 3.24 that's being
offered from a PPA). I appreciate that Humanity, and other icon themes,
will have to be updated to work with 3.24.

We're far enough down the path with this change, so we might as well
finish it, but let's be more conservative from now on please.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1669655

Title:
  Adapt to new Nautilus icon name

Status in humanity-icon-theme package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system-
  file-manager for better flatpak compatibility.

  I have updated ubuntu-themes and humanity-icon-theme for this change
  (adding a new symlink pointing to system-file-manager).

  ubuntu-themes is handled via bileto so I'll ask the appropriate people
  to sponsor that separately. DONE

  I pushed my change to the humanity bzr branch but I don't have upload rights 
for it so I'll need sponsorship for this:
  https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/

  I let other Ubuntu flavors know about this change at bug 1669663.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+subscriptions

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

[Dx-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name

[Iain Lane]

The new ubuntu-mono packages symlink org.gnome.Nautilus.svg to system-
file-manager-panel.svg. This makes you get that icon as the icon for
Nautilus, which is wrong.

I think that change should be reverted. I also think that implies that
the -panel change in humanity is also wrong.

I'd really prefer it if we could just forget about introducing
destabilising changes for very little benefit into Zesty at this point.
I don't see what the reason for backporting this change is. If you want
to update adwaita-icon-theme to 3.24, add symlinks there so that the old
icon continues to work.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1669655

Title:
  Adapt to new Nautilus icon name

Status in humanity-icon-theme package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system-
  file-manager for better flatpak compatibility.

  I have updated ubuntu-themes and humanity-icon-theme for this change
  (adding a new symlink pointing to system-file-manager).

  ubuntu-themes is handled via bileto so I'll ask the appropriate people
  to sponsor that separately. DONE

  I pushed my change to the humanity bzr branch but I don't have upload rights 
for it so I'll need sponsorship for this:
  https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/

  I let other Ubuntu flavors know about this change at bug 1669663.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+subscriptions

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

[Dx-packages] [Bug 1669655] Re: Adapt to new Nautilus icon name

[Iain Lane]

laney@zesty> bzr diff -r tag:0.6.12
=== added symlink 'Humanity-Dark/status/16/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity-Dark/status/22/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity-Dark/status/24/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/apps/128/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/apps/16/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/apps/24/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/apps/32/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/apps/48/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/status/16/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/status/22/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity/status/24/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'

The apps/ ones are broken symlinks. I didn't actually check this but I
should think that's a problem and they should point to system-file-
manager.svg instead.

Are the status/ symlinks necessary? I thought that these were used for
the panel - who requests those icons and how do they do it?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1669655

Title:
  Adapt to new Nautilus icon name

Status in humanity-icon-theme package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Nautilus 3.24's app icon name is org.gnome.Nautilus instead of system-
  file-manager for better flatpak compatibility.

  I have updated ubuntu-themes and humanity-icon-theme for this change
  (adding a new symlink pointing to system-file-manager).

  ubuntu-themes is handled via bileto so I'll ask the appropriate people
  to sponsor that separately. DONE

  I pushed my change to the humanity bzr branch but I don't have upload rights 
for it so I'll need sponsorship for this:
  https://code.launchpad.net/~ubuntu-art-pkg/humanity/release/

  I let other Ubuntu flavors know about this change at bug 1669663.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1669655/+subscriptions

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

[Dx-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

[Iain Lane]

uploaded, please test tomorrow once it hits an image

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1666495

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in unity-lens-applications:
  Invalid
Status in zeitgeist package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+subscriptions

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

[Dx-packages] [Bug 1666833] Re: Nautilus GTK overlay scrollbars never appear at small window sizes

[Iain Lane]

Typoed the bug number in the upload, but I think the new nautilus
(3.20.4) fixes this.

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

** Changed in: overlay-scrollbar (Ubuntu)
   Status: Confirmed => Invalid

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1666833

Title:
  Nautilus GTK overlay scrollbars never appear at small window sizes

Status in Canonical System Image:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Fix Released
Status in overlay-scrollbar package in Ubuntu:
  Invalid

Bug description:
  GTK overlay scrollbars never appear at small window sizes in zesty
  (but works in xenial).

  Test case:
    1. Launch "Files" (nautilus binary)
    2. Navigate to a folder with lots of files/icons.
    3. Resize the window as small as it will go.
    4. Slowly move the mouse so the cursor enters from the right side of the 
window.

  Expected: Overlay scrollbars appear
  Observed: Overlay scrollbars never appear (unless the window is bigger)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+subscriptions

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

[Dx-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

[Iain Lane]

Trevinho disagrees with me, but I want to put on the record that I think
comment #6's patch is wrong and that instead the VACUUM mode should
explicitly check if the database exists and "return 0" in that case.

Rationale:

It's reasonable to say that it's okay to run without having run the main
program first. The counter argument says that this is *not* reasonable
and you would expect an error in this case. I think that there is no one
true way here, and you should write programs with their intended usage
in mind. In this case I think the intented use is that you could imagine
a user writing a shell script such as:

  #!/bin/sh

  set -e

  zeitgeist-vacuum # or zeitgeist --vacuum
  zeitgeist

(of course this is a simplified version of the existing user unit's
control flow)

and it's just silly to have to detect the DB not existing explicitly
there. It's also a bit shady to ignore VACUUM failures that could point
to a more severe problem.

For the record, I think the code to implement my change would look like
this (untested).

var file = File.new_for_path (db_path);
if (!file.query_exists ())
{
debug ("Database '%s' doesn't exist, but that's okay".printf (db_path));
return 0;
}

With this change the unit file can remain unmodified.

Since there's disagreement, I won't unilaterally upload my suggestion.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1666495

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in unity-lens-applications:
  Invalid
Status in zeitgeist package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+subscriptions

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

[Dx-packages] [Bug 1622686] Re: double header in 16.10

[Iain Lane]

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Fix Committed

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

** Also affects: humanity-icon-theme (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: humanity-icon-theme (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1622686

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  New
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  New
Status in ubiquity source package in Yakkety:
  New

Bug description:
  STEPS:
  1. grab the latest iso
  2. Note the header during install

  EXPECTED:
  Icon on one header

  ACTUAL:
  I believe the a11y icon is double sized and forces a double header.  see photo

  /!\ Seem to be a hidpi only issue I see it on xps13 but not on other
  installs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Dx-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens

[Iain Lane]

** Changed in: humanity-icon-theme (Ubuntu)
   Status: Confirmed => Fix Committed

** Also affects: humanity-icon-theme (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: humanity-icon-theme (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1657863

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Committed
Status in humanity-icon-theme source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  New

Bug description:
  Because Humanity doesn't have support for @2x icons, some icons are
  displayed too big.  This is a general issue, but is easily noticed in
  a few examples below.

  In Nautilus, the icons are much too big on hidpi screends in 16.04,
  while in 16.10 the icons are the same size but use different icons
  with much thinner strokes.  The difference is also visible in icons on
  the Desktop.

  In Transmission, the "Open" button in the toolbar uses an icon with a
  different metaphor on hidpi screens (an up arrow emerging from a
  folder) than on lowdpi screens (a sheet of paper emerging from a
  folder).

  After adding symbolic links for @2x icons and updating the index.theme
  files accordingly fixes these issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Dx-packages] [Bug 1622686] Re: double header in 16.10

[Iain Lane]

** Also affects: humanity-icon-theme (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1622686

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. grab the latest iso
  2. Note the header during install

  EXPECTED:
  Icon on one header

  ACTUAL:
  I believe the a11y icon is double sized and forces a double header.  see photo

  /!\ Seem to be a hidpi only issue I see it on xps13 but not on other
  installs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

Re: [Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Iain Lane]

On Tue, Jan 10, 2017 at 12:39:40PM -, Jean-Baptiste Lallement wrote:
> I've tested dbus 1.10.6-1ubuntu3.2 on frieza xenial/arm64 and it renders
> the device completely unusable (cf bug 1654241)
> 
> Marking as verification-failed.

That's fair, but note that this is *not* a bug with this SRU. Something
is starting a dbus-daemon and setting its address in the environment. It
then is terminated and not available in the session. This SRU makes dbus
not start a new bus if the environment is saying there already is one.

Yes, it should be held out of -updates until that is fixed. But the fix
is elsewhere.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Committed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Iain Lane]

I don't see how this can be v-done given the QA steps in the
description, since unity-gtk-module isn't accepted yet. Were those steps
followed? If so, maybe I was too hasty in linking u-g-m into the bug. If
not, please could u-g-m be reviewed and ideally accepted into x-proposed
so this can be re-verified?

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Committed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Iain Lane]

** Description changed:

  [ Description ]
  
  In Xenial, when dbus-user-session is installed, dbus' upstart job still
  starts a new bus. Things get confused about which bus to talk to.
  
  [ Fix ]
  
  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation environment.
  
+ /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
+ before unity-gtk-module.conf is started - so dbus activated services
+ miss the GTK_MODULES environment variable. Update unity-gtk-module.conf
+ to set it in the dbus activation environment.
+ 
  [ QA ]
  
  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.
  
  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.
+ 
+ Test that gnome-terminal has global menus in both situations.
  
  [ Regression potential ]
  
  This change alters the way that the session bus is launched, even if you
  aren't using dbus-user-session. Even though this same change is deployed
  in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-
  session by default, so the case where you don't have it isn't as well
  tested. I would suggest focusing some testing on the non dbus-user-
  session case.
  
  [ Original report ]
  
  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as launching
  chromium and ctrl-alt-t for a new terminal session.
  
  Removing both the deb and the snap followed by a reboot does not fix the
  symptoms.
  
  Xenial amd64 laptop

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Iain Lane]

Both uploaded.

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Iain Lane]

unity-gtk-module needs to update the systemd environment now too

** Description changed:

+ [ Description ]
+ 
+ In Xenial, when dbus-user-session is installed, dbus' upstart job still
+ starts a new bus. Things get confused about which bus to talk to.
+ 
+ [ Fix ]
+ 
+ Already fixed in Yakkety. Cherry-pick the upstart job. On top of
+ Yakkety's version, call `dbus-update-activation-environment --verbose
+ --systemd GTK_MODULES', because Xenial does not have the change in
+ upstart to automatically publish to the systemd activation environment.
+ 
+ [ QA ]
+ 
+ Install dbus-user-session, press print screen. It should be delayed if
+ you are experiencing this bug, and not delayed otherwise.
+ 
+ Remove dbus-user-session, make sure the session still works properly -
+ the global menu works, everything launches properly, etc.
+ 
+ [ Regression potential ]
+ 
+ This change alters the way that the session bus is launched, even if you
+ aren't using dbus-user-session. Even though this same change is deployed
+ in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-
+ session by default, so the case where you don't have it isn't as well
+ tested. I would suggest focusing some testing on the non dbus-user-
+ session case.
+ 
+ [ Original report ]
+ 
  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as launching
  chromium and ctrl-alt-t for a new terminal session.
  
  Removing both the deb and the snap followed by a reboot does not fix the
  symptoms.
  
  Xenial amd64 laptop

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

** Changed in: unity-gtk-module (Ubuntu)
   Status: New => Fix Released

** Changed in: unity-gtk-module (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in unity-gtk-module source package in Xenial:
  In Progress

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1632413] [NEW] Starts on a unity 7 session where it isn't needed

[Iain Lane]

Public bug reported:

indicator-transfer is starting on unity 7, but it's not needed there

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: indicator-transfer 0.2+16.10.20160808.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 11 18:12:54 2016
InstallationDate: Installed on 2012-10-07 (1464 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
SourcePackage: indicator-transfer
UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1253 days ago)

** Affects: indicator-transfer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-transfer in Ubuntu.
https://bugs.launchpad.net/bugs/1632413

Title:
  Starts on a unity 7 session where it isn't needed

Status in indicator-transfer package in Ubuntu:
  New

Bug description:
  indicator-transfer is starting on unity 7, but it's not needed there

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-transfer 0.2+16.10.20160808.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 11 18:12:54 2016
  InstallationDate: Installed on 2012-10-07 (1464 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-transfer
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1253 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-transfer/+bug/1632413/+subscriptions

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

Re: [Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

[Iain Lane]

On Sun, Oct 02, 2016 at 10:27:43AM -, Martin Pitt wrote:
> Iain Lane [2016-10-01 19:26 -]:
> > Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> > something else - like unity7? You can't log in again with an active
> > unity7, so in theory (if stop is propagated down to graphical-session
> > and graphical-session-pre) there wouldn't be a need to stop/restart in
> > the script since everything would be stopped by definition if you're
> > trying to start unity7 again.
> 
> I like that idea in principle -- picking a session leader which
> automatically dies when X goes away would be a lot simpler indeed (and
> gnome-session does not do that). I picked gnome-session as the session
> leader because it traditionally has had that role, and it still has
> the API for logging out.
> 
> Another point is that we want to make unity/compiz robust against
> crashes and provide auto-restart -- if it becomes the session leader,
> then the whole session will go down on any crash. So picking
> unity7.service in particular is a bad choice.

It would be good if it were possible to say that the BindsTo shouldn't
trigger the target to stop until after systemd gives up restarting the
unit.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

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

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

Re: [Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

[Iain Lane]

On Sun, Oct 02, 2016 at 08:39:01AM -, Martin Pitt wrote:
> > If you ever end up stopping gnome-keyring from within a new session
> then its ExecStopPost kills the upstart session of this new one that we
> are starting up, *not* the previous one that it was started up under.
> 
> I assume you meant to say "gnome-session.service" here, not keyring (as
> its ExecStopPost is harmless). gnome-session is the session leader, so
> stopping it by definition means to end the current session.

Yes I did. But the problem is that it is *not* always stopped when the
session dies, so it is a bad choice of leader while that is true.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

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

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

Re: [Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

[Iain Lane]

On Sat, Oct 01, 2016 at 01:53:56PM -, Martin Pitt wrote:
> > To fix that, something like comment #3 is needed. Such as looping over
> all 'active' units that are PartOf graphical-session.target and stopping
> them all.
> 
> I think we would only need to "systemctl stop graphical-session.target"
> for this, otherwise a unit forgets the PartOf= and that loop would not
> work anyway.

I tried this, but I think that it might have only been before I worked
out the below ExecStopPost issue - so it's worth testing again.

> 
> > gnome-session needs a fix to its ExecStopPost to not kill the one we
> just started.
> 
> This is similar to waiting for "deactivating" units after
> *-session.target goes down. On the systemd sprint we just figured out a
> better scheme for this which solves that waiting, does not require this
> session ID tracking, and also gets rid of the manual starting of
> graphical-session-pre.target: Eventually we just want to declare in
> *-session.target that it comes After=graphical-session-pre.target and
> have this propagate to the dependencies
> (https://github.com/systemd/systemd/issues/3750). Until then we can just
> have a mini-generator do this for us. After we have the Requires/After
> =graphical-session-pre.target, then "systemctl stop graphical-session-
> pre.target" properly blocks until all "later" units are completely
> stopped.

I remember this problem.

It would only solve this specific issue if it lets us get rid of the
stop or restart in the session-runner script. If you ever end up
stopping gnome-keyring from within a new session then its ExecStopPost
kills the upstart session of this new one that we are starting up, *not*
the previous one that it was started up under. That's a mismatch vs.
session and user specific semantics of upstart and systemd --user.

Hmm. Maybe this is saying that we should bind ubuntu-session.target to
something else - like unity7? You can't log in again with an active
unity7, so in theory (if stop is propagated down to graphical-session
and graphical-session-pre) there wouldn't be a need to stop/restart in
the script since everything would be stopped by definition if you're
trying to start unity7 again.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

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

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

[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

[Iain Lane]

This isn't quite enough in this situation.

- Log in over SSH or in a vt (so there is a logind session alive for your user)
- Log into the same user in Unity
- Simulate an Xorg crash (pkill -f -SEGV Xorg)
- Log back in

You don't have GTK_MODULES set properly. The previous gnome-session is
lingering.

To fix that, something like comment #3 is needed. Such as looping over
all 'active' units that are PartOf graphical-session.target and stopping
them all.

gnome-session needs a fix to its ExecStopPost to not kill the one we
just started.

I'll upload this and it can be reviewed in the queue.

** Changed in: gnome-session (Ubuntu)
   Status: Fix Released => Triaged

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

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

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

** Changed in: gnome-session (Ubuntu)
   Importance: High => Medium

** Changed in: gnome-session (Ubuntu)
 Assignee: Martin Pitt (pitti) => Iain Lane (laney)

** Changed in: upstart (Ubuntu)
 Assignee: Martin Pitt (pitti) => Iain Lane (laney)

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Triaged
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

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

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

[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

[Iain Lane]

To restart everything when the session starts, add

  systemctl --user stop graphical-session.target

to the systemd-graphical-session.conf and run-systemd-session, after the
block where all failed units are reset.

For the unity-in-upstart case, we might want to not override unity-gtk-
module? Maybe it then becomes racy with setting environment variables
though.

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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

[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

[Iain Lane]

s/restart everything/stop everything from a previous graphical session/

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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

[Dx-packages] [Bug 1597598] Re: a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI display.

[Iain Lane]

Please resubmit this as a merge proposal against lp:libindicator.

I think you should (as well as doing this) fix the earlier calls to
gtk_icon_theme_lookup_by_gicon to use
gtk_icon_theme_lookup_by_gicon_for_scale.

What does gtk_widget_get_scale_factor on the GtkImage give you? If
that's right, use that instead.

Please fix the indentation to match the surrounding code.

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

Title:
  a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI
  display.

Status in libindicator package in Ubuntu:
  New

Bug description:
  When using a laptop with HiDPI display, the a11y-profile-manager-
  indicator scaled too large in Ubiquity.

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

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

Re: [Dx-packages] [Bug 1551986] Re: [FFe][UIFe] HUD hotkey assignment is suboptimal

[Iain Lane]

On Wed, Apr 13, 2016 at 09:01:54PM -, Will Cooke wrote:
> It's worth noting that the current alt-space functionality (move,
> minimize, maximize etc) will be exposed via the HUD.  So that
> functionality will remain.

It'll break the existing mnemonics behaviour, unless alt-space, x with
the HUD activates maximise immediately - which would be bad behaviour
for the HUD itself.

I think this is way too close to the release. Can we just fix the hud's
bad default binding to something else or, failing that, back this change
out and work out an acceptable solution for 16.04.1?

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [FFe][UIFe] HUD hotkey assignment is suboptimal

Status in bamf package in Ubuntu:
  In Progress
Status in compiz package in Ubuntu:
  In Progress
Status in hud package in Ubuntu:
  In Progress
Status in libwnck3 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress
Status in bamf source package in Xenial:
  In Progress
Status in compiz source package in Xenial:
  In Progress
Status in hud source package in Xenial:
  In Progress
Status in libwnck3 source package in Xenial:
  In Progress
Status in unity source package in Xenial:
  In Progress

Bug description:
  = Proposed Change =
  The suggestion (subject to Design approval) is to remap HUD to alt-space and 
also expose window controls in to the HUD such that people used to using 
"alt-space n"to minimize a window still can.

  = Motivation =
  Having HUD trigger on alt tap is not working so this is a request to change 
it. It conflicts with several other applications such as full screen games, etc.

  = Potential Regressions =
  * Hud fails to open on alt+space
  * Hud fails to show normal menu entries for gtk applications
  * Hud fails to show normal menu entries for qt applications

  == Links to mailing lists ==
  * https://lists.ubuntu.com/archives/ubuntu-translators/2016-April/007138.html
  * https://lists.ubuntu.com/archives/ubuntu-doc/2016-April/019870.html

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

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

[Dx-packages] [Bug 1551986] Re: [FFe][UIFe] HUD hotkey assignment is suboptimal

[Iain Lane]

I've blocked this change in xenial-proposed. They only got there because
the CI train bypasses the unapproved queue.

The FFe wasn't approved so they shouldn't really have been uploaded.

I think it's contentious to make HUD take over what was a bit of window
manager functionality, especially so close to release.

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

Title:
  [FFe][UIFe] HUD hotkey assignment is suboptimal

Status in bamf package in Ubuntu:
  In Progress
Status in compiz package in Ubuntu:
  In Progress
Status in hud package in Ubuntu:
  In Progress
Status in libwnck3 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress
Status in bamf source package in Xenial:
  In Progress
Status in compiz source package in Xenial:
  In Progress
Status in hud source package in Xenial:
  In Progress
Status in libwnck3 source package in Xenial:
  In Progress
Status in unity source package in Xenial:
  In Progress

Bug description:
  = Proposed Change =
  The suggestion (subject to Design approval) is to remap HUD to alt-space and 
also expose window controls in to the HUD such that people used to using 
"alt-space n"to minimize a window still can.

  = Motivation =
  Having HUD trigger on alt tap is not working so this is a request to change 
it. It conflicts with several other applications such as full screen games, etc.

  = Potential Regressions =
  * Hud fails to open on alt+space
  * Hud fails to show normal menu entries for gtk applications
  * Hud fails to show normal menu entries for qt applications

  == Links to mailing lists ==
  * https://lists.ubuntu.com/archives/ubuntu-translators/2016-April/007138.html
  * https://lists.ubuntu.com/archives/ubuntu-doc/2016-April/019870.html

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

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

[Dx-packages] [Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Iain Lane]

Thanks for the investigation. I uploaded the new pygobject to fix this.

(@pitti, sorry for doing this without consulting you - I was pinged a
few times about this bug and checked the changes which seemed to be
bugfix)

** Changed in: pygobject (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: pygobject (Ubuntu)
 Assignee: Ubuntu Desktop (ubuntu-desktop) => Iain Lane (laney)

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1538471

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

Status in Ubuntu Kylin:
  New
Status in libunity package in Ubuntu:
  Invalid
Status in pygobject package in Ubuntu:
  Fix Committed

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size 
(fast): 0x01ca17b0 ***
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Jan 27 10:41:54 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-04-30 (271 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
info/calculator.scope
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid 
next size (fast)", action=1) at malloc.c:4965
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3834
   __GI___libc_free (mem=) at malloc.c:2950
   ?? () from 
/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': 
free(): invalid next size (fast): 0x01ca17b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1513110] Re: global menus are broken and cannot be clicked

[Iain Lane]

reverted, will make sure the .symbols are fixed before re-uploading the
original fixes

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1513110

Title:
  global menus are broken and cannot be clicked

Status in Unity:
  Invalid
Status in indicator-appmenu package in Ubuntu:
  Confirmed

Bug description:
  Global menus are broken in latest xenial and cannot be clicked.

  Clicking on the menu in the unity panel will make the panel turn
  completely to the background color and flicker, but one still can't
  get the menu.

  Furthermore, for windowed applications clicking the global menu will
  change the size of the windowed application, reducing it by a few
  pixels. (Easily reproducible using gnome-terminal).

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

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

[Dx-packages] [Bug 1513110] Re: global menus are broken and cannot be clicked

[Iain Lane]

indicator-appmenu migrated before bamf, from which it uses new symbols,
due to bamf not having a correct .symbols file

** Package changed: unity (Ubuntu) => indicator-appmenu (Ubuntu)

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1513110

Title:
  global menus are broken and cannot be clicked

Status in Unity:
  Invalid
Status in indicator-appmenu package in Ubuntu:
  Confirmed

Bug description:
  Global menus are broken in latest xenial and cannot be clicked.

  Clicking on the menu in the unity panel will make the panel turn
  completely to the background color and flicker, but one still can't
  get the menu.

  Furthermore, for windowed applications clicking the global menu will
  change the size of the windowed application, reducing it by a few
  pixels. (Easily reproducible using gnome-terminal).

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

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

[Dx-packages] [Bug 1460626] Re: Unity Lockscreen still shows unlocked desktop while shutting down

[Iain Lane]

** Also affects: indicator-session (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460626

Title:
  Unity Lockscreen still shows unlocked desktop while shutting down

Status in Unity:
  Fix Committed
Status in indicator-session package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in indicator-session source package in Trusty:
  New
Status in unity source package in Trusty:
  New

Bug description:
  This was reported and supposedly fixed in
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the
  bug is still present in the current Unity version in Trusty.  I've
  reported it in that bug already, but got ignored, so I'm opening a new
  bug about it.

  [Impact and Test Case]

  Steps to reproduce:
  1 - Log into Unity
  2 - Open a terminal.
  3 - Lock the screen
  4 - From the lockscreen, tell the computer to shut down / restart

  Expected behavior:
  * Session programs are closed while the screen is still locked
  * During shutdown, no user interaction is possible

  Observed behavior:
  * The lockscreen is gone immediately, with the rest of compiz (e.g. window 
decorations are not present)
  * But it's possible to interact with programs that are still running in the 
session for about 3 seconds

  Observed on an updated Trusty machine, running unity version
  7.2.5+14.04.20150521.1-0ubuntu1

  This bug is a security vulnerability because during those 3 seconds it
  could be possible to access and interact with sensitive information.
  Yes, it's short, but you could take a picture or even rm -rf / if
  there happened to be a root console available.

  =

  [Impact]
  A lockscreen should hide the screen content no matter what. A the moment 
there is no easy way to provide a good shutdown experience if the screen is 
locked so it's better to disable it. Please note that you can still shut down 
the system if the screen is locked just switching to unity-greeter using 
"Swtich Account..." (it's safe in this case)

  Needs to be backported to 14.04 LTS because can affect security.

  [Test Case]
  1 - Lock the screen
  2 - Push the hw shutdown button.
  3 - Make sure that there is no shutdown option in the end of session dialog.

  1 - Lock the screen
  2 - Open the session indicator
  3 - Make sure there is no shutdown option in the drop down menu

  [Regression Potential]
  None.

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

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

[Dx-packages] [Bug 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()

[Iain Lane]

** Also affects: ido (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350821

Title:
  unity-panel-service crashed with SIGSEGV in
  ido_calendar_menu_item_key_press()

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  New

Bug description:
  
  [Impact]
  Unity panel service crashes when opening the Calendar menu

  [Test Case]
  There's not a way to reproduce this systemically. Just open frequently the 
calendar menu, but this crash can happen or not.

  [Regression Potential]
  None, the code change consists only on protecting against a null pointer 
(recorded in the stacktraces here), so it's just pretty safe.

  
  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 31 13:53:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-12-22 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx
   PC (0x7ffbbaf3b766) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jul 30 18:55:05 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu8

To manage notifications about this bug go 

[Dx-packages] [Bug 1308037] Re: No results from application scope

[Iain Lane]

I'm unduping this - bug #1295908 says that there are two ways to fix
(try again or check 'applications' in the filters list). This bug is
about being in a state where neither of these cases work - apps are
never returned until unity is restarted.

I got it once again a couple of weeks ago but I forgot to try that apps
lens (comment #6), sorry - will try to remember next time.

** This bug is no longer a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

** Summary changed:

- No results from application scope
+ No results from application scope until Unity is restarted

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308037

Title:
  No results from application scope until Unity is restarted

Status in libunity:
  Invalid
Status in Unity:
  Confirmed
Status in unity-lens-applications:
  Invalid
Status in libunity package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity is in a state where I don't get any results from the
  applications lens. This sometimes happens for one search but either
  re-entering the search or toggling the lens has always fixed it in the
  past for me. This time neither of these steps work.

  I'm attaching a bustle log of the problem in case that's helpful. I
  searched for "spotify", which I've got installed, and got 0 results.

  The only way to fix the issue is to log out and back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 13:29:40 2014
  InstallationDate: Installed on 2012-10-07 (554 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago)

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

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

[Dx-packages] [Bug 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

[Iain Lane]

** Branch linked: lp:~laney/upstart/lp1433013

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

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  via Super Key -> the environment is correct

  via Alt-F2 -> it is not

  
  I believe Alt+F2 code path should call into upstart dbus api to "list-env" 
and import that environment before executing the search result.

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

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

Re: [Dx-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Iain Lane]

On Mon, Oct 05, 2015 at 08:30:29PM -, Bryan Quigley wrote:
> I haven't had this issue since upgrading to glib2.0 (2.46.0-2).  Can
> this and related issues be closed as Fixed?

If they are fixed, then mark them as so.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

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

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

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

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

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

[Dx-packages] [Bug 1501476] Re: datetime indicator spins out of control when clicking neighbor-month day

[Iain Lane]

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

** This bug has been marked a duplicate of bug 1480387
   Clicking a date to go back or forward a month causes repeated jumps between 
two dates

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1501476

Title:
  datetime indicator spins out of control when clicking neighbor-month
  day

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Click the date indicator to get a calendar and list of schedule
  entries for the highlighted, default day.

  Notice the month grid of days. Assuming it doesn't fall evenly on week
  boundaries, you'll see days from previous or following month in the
  list.

  Click on a day from another month.

  Watch the selected month change, then rapidly switch to and fro in
  months, pulling calendar items from evolution data store, re-
  rendering, and burning CPU in three separate processes.

  You can also walk ahead one month step, and then click backwards to a
  margin day in contemporary month, but choosing the present day does
  not trigger the bug, but any other day does.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150909-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 30 15:17:55 2015
  InstallationDate: Installed on 2014-05-07 (510 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1501476/+subscriptions

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

[Dx-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone

[Iain Lane]

I think this is fixed

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1485659

Title:
  Date/time indicator doesn't update after changing time zone

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  After changing the timezone the time displayed in the date/time
  indicator is still in my old time zone. I sent a signal to the
  indicator-datetime-service process, and after it restarted the correct
  time was displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 17 08:51:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (178 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions

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

[Dx-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Iain Lane]

** Changed in: unity-gtk-module (Ubuntu)
   Status: Triaged => Invalid

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

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

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

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

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

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

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

[Dx-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Iain Lane]

I uploaded it to unstable and will sync when Launchpad picks it up,
thanks for the testing

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

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

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

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

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

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

[Dx-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Iain Lane]

It's *probably* a bug in unity-gtk-module - Will has been looking into
this.

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

** Changed in: unity-gtk-module (Ubuntu)
   Status: New => Triaged

** Changed in: unity-gtk-module (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: unity-gtk-module (Ubuntu)
 Assignee: (unassigned) => William Hua (attente)

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

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

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

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

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

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

[Dx-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()

[Iain Lane]

Oh and you can reproduce it by turning the External Tools plugin on

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

Title:
  gedit crashed with SIGABRT in g_assertion_message()

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

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

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

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

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

[Dx-packages] [Bug 1499286] [NEW] In scale factors > 1, some icons in the dash (e, g. d-feet) may be clipped instead of scaled

[Iain Lane]

Public bug reported:

This happens on my laptop with 2× but not my desktop with 1×

1. Install d-feet
2. Search for d-feet in the dash
3. Look at the icon - you see the top-left corner of it and not the whole thing

Screenshot is attached.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity 7.3.2+15.10.20150921-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Sep 24 11:18:07 2015
InstallationDate: Installed on 2015-06-05 (110 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Attachment added: "icon.png"
   https://bugs.launchpad.net/bugs/1499286/+attachment/4473181/+files/icon.png

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

Title:
  In scale factors > 1, some icons in the dash (e,g. d-feet) may be
  clipped instead of scaled

Status in unity package in Ubuntu:
  New

Bug description:
  This happens on my laptop with 2× but not my desktop with 1×

  1. Install d-feet
  2. Search for d-feet in the dash
  3. Look at the icon - you see the top-left corner of it and not the whole 
thing

  Screenshot is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20150921-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Sep 24 11:18:07 2015
  InstallationDate: Installed on 2015-06-05 (110 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

[Iain Lane]

I think it makes sense. DBus in wily (>= 1.9) does similar for
Xsession.d managed sessions:

# unset login-session-specifics
unset XDG_SEAT
unset XDG_SESSION_ID
unset XDG_VTNR

# tell dbus-daemon --session (and systemd --user, if running)
# to put the Xsession's environment in activated services'
# environments
dbus-update-activation-environment --verbose --systemd --all

You probably want to blacklist those same variables.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-lens-applications in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1433013

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix
Status in unity-lens-applications package in Ubuntu:
  Won't Fix
Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  via Super Key -> the environment is correct

  via Alt-F2 -> it is not

  
  I believe Alt+F2 code path should call into upstart dbus api to "list-env" 
and import that environment before executing the search result.

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

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

[Dx-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone

[Iain Lane]

** Branch linked: lp:~laney/indicator-datetime/timedated-timezone-
property

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1485659

Title:
  Date/time indicator doesn't update after changing time zone

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  After changing the timezone the time displayed in the date/time
  indicator is still in my old time zone. I sent a signal to the
  indicator-datetime-service process, and after it restarted the correct
  time was displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 17 08:51:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (178 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions

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

[Dx-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone

[Iain Lane]

We should instead watch timedated's Timezone property

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) = Iain Lane (laney)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1485659

Title:
  Date/time indicator doesn't update after changing time zone

Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  After changing the timezone the time displayed in the date/time
  indicator is still in my old time zone. I sent a signal to the
  indicator-datetime-service process, and after it restarted the correct
  time was displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 17 08:51:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (178 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150110)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions

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

[Dx-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone

[Iain Lane]

I think it's a glib GFileMonitor problem - it works again if I build
2.44 and run with that. The code here is watching /etc/timezone to know
when it changes.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1485659

Title:
  Date/time indicator doesn't update after changing time zone

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After changing the timezone the time displayed in the date/time
  indicator is still in my old time zone. I sent a signal to the
  indicator-datetime-service process, and after it restarted the correct
  time was displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 17 08:51:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (178 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150110)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions

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

[Dx-packages] [Bug 1295908] Re: Sometimes applications stop showing up in the Dash

[Iain Lane]

Forgive me that I'm re-explaining the bug, but I just want it to be
clear. When I see this (I agree it is certainly not #1308037 - when that
happens [haven't seen it for a long time though], *no* searches ever
give a result until Unity is restarted - this is about some searches not
working  retrying being okay), it's like this.

  - Open dash, search for something.
  - Usually it works but sometimes I get Sorry, there is nothing that matches 
your search. wrongly.
  - When that happens, I can open Filter results and select Applications to 
see the results.
  - It's easy to reproduce - just hit ctrl-backspace and type the same search 
term a few times. Soon it'll not work.

I can only get this to happen on one of my two machines. Perhaps the
interesting difference is that the one which reproduces it has been
installed for a long time and the other one is quite new.

** Tags added: rls-w-incoming

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

Title:
  Sometimes applications stop showing up in the Dash

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

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

  What happens: Application scope stops giving results

  What should happen: Application scope should still give results

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

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

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

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

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

[Dx-packages] [Bug 1480387] [NEW] Clicking a date to go back or forward a month causes repeated jumps between two dates

[Iain Lane]

Public bug reported:

I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
or trusty. It happened for me in the most recent wily iso.

Open the indicator, click one of the greyed dates at the start or end of
the month (sometimes requires more than one go). The active date starts
to repeatedly jump between this date and another one. I ran with
G_MESSAGES_DEBUG=all and when it's happening this is spammed (I clicked
a date in 2015-05).

(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
(process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
(process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
(process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
Uname: Linux 4.1.0-2-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 31 17:09:43 2015
InstallationDate: Installed on 2012-10-07 (1026 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages wily

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1480387

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  

[Dx-packages] [Bug 1460271] Re: Update evolution-data-server to 3.16

[Iain Lane]

** Changed in: evolution-data-server (Ubuntu)
   Status: In Progress = Fix Released

** Changed in: indicator-datetime (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271

Title:
  Update evolution-data-server to 3.16

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Update to 3.16. Debian currently has this in experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+subscriptions

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

Re: [Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

On Sun, Jul 19, 2015 at 10:57:28PM -, gfysty! wrote:
 Come on ffs...
 I had no problem whatsoever on 15.04 with the previously installed version, 
 now the Context-Menu in Fullscreen completely disappeared in  Totem and i 
 have to minimize it it an use the Unity Taksbar to scale or 
 deactivate/activate Subtitles, something that worked before this ... update 
 no problem with subtitles whatsoever.

Please keep your language calm.

It wasn't technically possible for us to provide for both use cases I'm
afraid. We were stuck between having no way to change languages or
subtitles (which lots of people were unhappy about) or having no menu in
fullscreen and we chose what we consider to be the lesser of two evils.

Ubuntu's team for managing updates to stable releases had the chance to
review this update and passed it too. It has gone through our correct
process.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  Fix Released
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items Language and Subtitles do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical  already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1460271] Re: Update evolution-data-server to 3.16

[Iain Lane]

See
https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1469208

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271

Title:
  Update evolution-data-server to 3.16

Status in evolution-data-server package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Update to 3.16. Debian currently has this in experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+subscriptions

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

[Dx-packages] [Bug 1460271] Re: Update evolution-data-server to 3.16

[Iain Lane]

Uploading to ppa:laney/experimental prior to putting into wily

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271

Title:
  Update evolution-data-server to 3.16

Status in evolution-data-server package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Update to 3.16. Debian currently has this in experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+subscriptions

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

[Dx-packages] [Bug 1460271] Re: Update evolution-data-server to 3.16

[Iain Lane]

** Changed in: evolution-data-server (Ubuntu)
   Status: Triaged = In Progress

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) = Iain Lane (laney)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271

Title:
  Update evolution-data-server to 3.16

Status in evolution-data-server package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Update to 3.16. Debian currently has this in experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

Uploaded with a note about the behaviour changes. We think that on
balance being able to select languages outweighs these, but it is up to
you dear SRU team to decide.

** Description changed:

- After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to select
- different audio tracks or subtitles when playing videos with multiple
- tracks. This is a regression from Ubuntu 14.10 where playback of such
- files was working as expected. I tried this on multiple machines running
- 15.04 and with various media, mostly MKV videos but also AVI videos or
- simply DVDs.
+ [ Description ]
  
- On Totem the expected functionality in the application menu is missing
- or the menu item is just empty.
+ Under Unity, the menu items Language and Subtitles do not show
+ available languages and subtitles that can be selected.
  
- On VLC the menu items are present but always disabled.
+ [ Fix ]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: totem 3.14.2-0ubuntu1
- ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
- Uname: Linux 3.19.0-14-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 2.17.2-0ubuntu1
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Wed Apr 22 16:53:57 2015
- InstallationDate: Installed on 2014-07-15 (280 days ago)
- InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
- SourcePackage: totem
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Port to GMenu, which can correctly show the menu items.
+ 
+ NOTE that this removes the menu from full screen under Unity.
+ 
+ [ QA ]
+ 
+ Test under both Unity and GNOME shell (and optionally other DEs) that
+ you can load a video (e.g.
+ 
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
+ [large - 819M]) with subtitles and languages and select between them.
+ 
+ [ Development fix ]
+ 
+ Identical  already uploaded.
+ 
+ [ Regression potential ]
+ 
+ Due to the nature of this change, you won't get the app menu when full
+ screened under Unity any more - langs and subtitles can only be selected
+ from the regular menu which is visible when not in full screen.
+ 
+ No other regressions are expected, so if you find any please report in
+ this bug.

** Changed in: totem (Ubuntu Vivid)
   Status: Confirmed = In Progress

** Changed in: totem (Ubuntu Vivid)
 Assignee: (unassigned) = Iain Lane (laney)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  In Progress
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items Language and Subtitles do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical  already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

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

** Changed in: indicator-appmenu (Ubuntu Vivid)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items Language and Subtitles do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical  already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1430059] Re: LyX menu is not updated by indicator-appmenu in mode unity-all-menus

[Iain Lane]

** Changed in: lyx (Ubuntu Vivid)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1430059

Title:
  LyX menu is not updated by indicator-appmenu in mode unity-all-menus

Status in indicator-appmenu package in Ubuntu:
  In Progress
Status in lyx package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in lyx source package in Vivid:
  Invalid

Bug description:
  Options greyed out:
  - File menu: Close through Version control, plus Export and Print
  - Edit menu: all options
  - View menu: all but Messages pane, Toolbars and Fullscreen
  - Insert menu: all options
  - Navigate menu: all options
  - Document menu: all options
  - Tools menu:  Spellchecker and Statistics

  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  lyx:
Installed: 2.1.3-1
Candidate: 2.1.3-1
Version table:
   *** 2.1.3-1 0
  500 http://br.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lyx 2.1.3-1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  9 19:45:01 2015
  ExecutablePath: /usr/bin/lyx
  InstallationDate: Installed on 2015-02-03 (33 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: lyx
  UpgradeStatus: Upgraded to vivid on 2015-03-05 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1430059/+subscriptions

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

Re: [Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

On Thu, Jun 11, 2015 at 01:13:14PM +0100, Iain Lane wrote:
 On Thu, Jun 11, 2015 at 11:57:31AM -, Rich Daley wrote:
  +1 to pwuertz's comment. This is a wider issue than totem so marking it
  as resolved when there's a workaround only for totem doesn't help those
  of us with issues in VLC.
 
 Please be slightly patient.
 
 They are two different bugs. I was checking on another report.
 
 The vlc issue is bug #1340059.

oops, bug #1430059. :)

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  In Progress
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items Language and Subtitles do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical  already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

Re: [Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

On Thu, Jun 11, 2015 at 11:57:31AM -, Rich Daley wrote:
 +1 to pwuertz's comment. This is a wider issue than totem so marking it
 as resolved when there's a workaround only for totem doesn't help those
 of us with issues in VLC.

Please be slightly patient.

They are two different bugs. I was checking on another report.

The vlc issue is bug #1340059.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  In Progress
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items Language and Subtitles do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical  already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1430059] Re: LyX menu is not updated by indicator-appmenu in mode unity-all-menus

[Iain Lane]

This affects vlc too (originally reported in bug #1447224) - could you
upload this soon  SRU it?

** Also affects: lyx (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: indicator-appmenu (Ubuntu Vivid)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1430059

Title:
  LyX menu is not updated by indicator-appmenu in mode unity-all-menus

Status in indicator-appmenu package in Ubuntu:
  In Progress
Status in lyx package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  New
Status in lyx source package in Vivid:
  New

Bug description:
  Options greyed out:
  - File menu: Close through Version control, plus Export and Print
  - Edit menu: all options
  - View menu: all but Messages pane, Toolbars and Fullscreen
  - Insert menu: all options
  - Navigate menu: all options
  - Document menu: all options
  - Tools menu:  Spellchecker and Statistics

  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  lyx:
Installed: 2.1.3-1
Candidate: 2.1.3-1
Version table:
   *** 2.1.3-1 0
  500 http://br.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lyx 2.1.3-1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  9 19:45:01 2015
  ExecutablePath: /usr/bin/lyx
  InstallationDate: Installed on 2015-02-03 (33 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: lyx
  UpgradeStatus: Upgraded to vivid on 2015-03-05 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1430059/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

That patch uses gtk_popover_set_transitions_enabled, which is ≥ 3.16 :(

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

Recording what we said on IRC

   - No way to change languages/subtitles in fullscreen
   - There's an empty menu when the file doesn't have selectable audio 
languages. Can submenus be made insensitive? Or maybe add a No languages item.
  - Doesn't backport cleanly to 3.14 for SRU to vivid  my version didn't work 
properly. :)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1460271] Re: Update evolution-data-server to 3.16

[Iain Lane]

They're about to do this in Debian so we can get patches for free-ish
(or help out there) if we wait.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271

Title:
  Update evolution-data-server to 3.16

Status in evolution-data-server package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Update to 3.16. Debian currently has this in experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+subscriptions

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

Re: [Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

[Iain Lane]

On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
 ** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released

I'm not sure what that means but if it means that it's supposed to be
fixed then it's not yet. I only uploaded one piece to wily. I think
seb128 is handling the rest (+ vivid/overlay).

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1390120

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time  
Date settings and select Manually under Set the time and date:
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the Date Time Indicator at top-right
  3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time  Date settings agree with Old_Time and Automatically has been 
selected under Set the time and date:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions

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

Re: [Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

[Iain Lane]

On Fri, May 22, 2015 at 04:18:50PM +0100, Iain Lane wrote:
 On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
  ** Changed in: canonical-devices-system-image
 Status: Confirmed = Fix Released
 
 I'm not sure what that means but if it means that it's supposed to be
 fixed then it's not yet. I only uploaded one piece to wily. I think
 seb128 is handling the rest (+ vivid/overlay).

Thought this was a different bug. Disregard. :)


-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1390120

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in the base for Ubuntu mobile products:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in systemd-shim package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time  
Date settings and select Manually under Set the time and date:
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the Date Time Indicator at top-right
  3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time  Date settings agree with Old_Time and Automatically has been 
selected under Set the time and date:

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions

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

[Dx-packages] [Bug 1433013] Re: Super - exec vs Alt-F2 - exec have different environment

[Iain Lane]

Can you please test this with the gnome-session in vivid-proposed /
wily? We think it might be the same issue.

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

Title:
  Super - exec vs Alt-F2 - exec have different environment

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity-lens-applications source package in Trusty:
  New
Status in upstart source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity-lens-applications source package in Utopic:
  New
Status in upstart source package in Utopic:
  New
Status in unity source package in Vivid:
  New
Status in unity-lens-applications source package in Vivid:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started proccesses lack them.

  to test

  Super Key - xterm - Enter - env | grep SSH

  vs

  Alt+F2 - xterm - Enter - env | grep SSH

  via Super Key - the environment is correct

  via Alt-F2 - it is not

  
  I believe Alt+F2 code path should call into upstart dbus api to list-env 
and import that environment before executing the search result.

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

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

Lars said he would take a look at this soon - looks to me (but I don't
know the most about this stuff) like totem's code is failing to populate
the traditional menubar but does for the gear menu - so there's a bug in
totem too in addition to any indicator-appmenu bug.

** Changed in: totem (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

** Also affects: totem (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: vlc (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: indicator-appmenu (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: vlc (Ubuntu Vivid)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  New
Status in totem source package in Vivid:
  New
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

rhythmbox has a function rb_application_link_shared_menus that might be
similar to what we want here

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  New
Status in totem source package in Vivid:
  New
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Iain Lane]

rhythmbox has a function rb_application_link_shared_menus that might be
similar to what we want here

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  New
Status in totem source package in Vivid:
  New
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Dx-packages] [Bug 1412709] Re: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme'

[Iain Lane]

** Changed in: notify-osd (Ubuntu)
   Status: In Progress = Fix Released

** Changed in: telephony-service (Ubuntu)
 Assignee: Iain Lane (laney) = (unassigned)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1412709

Title:
  Error: loading icon 'notification-notification-audio-volume-medium'
  caused error: 'Icon 'notification-notification-audio-volume-medium'
  not present in theme'

Status in notify-osd package in Ubuntu:
  Fix Released
Status in notify-osd-icons package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  In Progress

Bug description:
  I am seeing the following warning with notify-osd when changing the
  volume:

 loading icon 'notification-notification-audio-volume-medium' caused
  error: 'Icon 'notification-notification-audio-volume-medium' not
  present in theme'

  This happens also when running it manually (as in src/send-test-
  notification.sh):

  notify-send Volume -i notification-audio-volume-medium -h
  int:value:75 -h string:x-canonical-private-synchronous:

  When leaving out the notification- prefix there's no error:

  notify-send Volume -i audio-volume-medium -h int:value:75 -h
  string:x-canonical-private-synchronous:

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 20 10:41:03 2015
  DesktopSession: 'ubuntu'
  GtkTheme: 'Numix'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2012-05-28 (966 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 42992PG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.3-0ubuntu0.2
   libdrm2  2.4.56-1~ubuntu1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3.1
  SourcePackage: notify-osd
  UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42992PG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42992PG
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1412709/+subscriptions

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

[Dx-packages] [Bug 1425578] Re: Window title sometimes gets rendered underneath controls

[Iain Lane]

** Attachment added: controls.png
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1425578/+attachment/4327267/+files/controls.png

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

Title:
  Window title sometimes gets rendered underneath controls

Status in unity package in Ubuntu:
  New

Bug description:
  If it's relevant I have all LIM settings at default (enabled, show on
  mouse over).

  When changing workspaces, the controls of a maximised unfocused window
  sometimes get rendered behind the controls of that window.

  1. Maximise a window (I use firefox)
  2. Focus another window on the same workspace.
  3. Switch workspaces, wait for the title to change, switch back.
  4. The window title is behind the controls

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb 25 16:20:55 2015
  InstallationDate: Installed on 2012-10-07 (870 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago)

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

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

[Dx-packages] [Bug 1425578] [NEW] Window title sometimes gets rendered underneath controls

[Iain Lane]

Public bug reported:

If it's relevant I have all LIM settings at default (enabled, show on
mouse over).

When changing workspaces, the controls of a maximised unfocused window
sometimes get rendered behind the controls of that window.

1. Maximise a window (I use firefox)
2. Focus another window on the same workspace.
3. Switch workspaces, wait for the title to change, switch back.
4. The window title is behind the controls

See attached screenshot

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Feb 25 16:20:55 2015
InstallationDate: Installed on 2012-10-07 (870 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
SourcePackage: unity
UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago)

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  Window title sometimes gets rendered underneath controls

Status in unity package in Ubuntu:
  New

Bug description:
  If it's relevant I have all LIM settings at default (enabled, show on
  mouse over).

  When changing workspaces, the controls of a maximised unfocused window
  sometimes get rendered behind the controls of that window.

  1. Maximise a window (I use firefox)
  2. Focus another window on the same workspace.
  3. Switch workspaces, wait for the title to change, switch back.
  4. The window title is behind the controls

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb 25 16:20:55 2015
  InstallationDate: Installed on 2012-10-07 (870 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago)

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

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

[Dx-packages] [Bug 1412709] Re: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme'

[Iain Lane]

Funnily enough I had fixed these the other day, just needs uploading.

** Branch linked: lp:~laney/notify-osd-icons/humanity-not-gnome

** Branch linked: lp:~laney/telephony-service/humanity-not-gnome

** Also affects: telephony-service (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: notify-osd (Ubuntu)
   Status: New = In Progress

** Changed in: telephony-service (Ubuntu)
   Status: New = In Progress

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) = Iain Lane (laney)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1412709

Title:
  Error: loading icon 'notification-notification-audio-volume-medium'
  caused error: 'Icon 'notification-notification-audio-volume-medium'
  not present in theme'

Status in notify-osd package in Ubuntu:
  In Progress
Status in telephony-service package in Ubuntu:
  In Progress

Bug description:
  I am seeing the following warning with notify-osd when changing the
  volume:

 loading icon 'notification-notification-audio-volume-medium' caused
  error: 'Icon 'notification-notification-audio-volume-medium' not
  present in theme'

  This happens also when running it manually (as in src/send-test-
  notification.sh):

  notify-send Volume -i notification-audio-volume-medium -h
  int:value:75 -h string:x-canonical-private-synchronous:

  When leaving out the notification- prefix there's no error:

  notify-send Volume -i audio-volume-medium -h int:value:75 -h
  string:x-canonical-private-synchronous:

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 20 10:41:03 2015
  DesktopSession: 'ubuntu'
  GtkTheme: 'Numix'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2012-05-28 (966 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 42992PG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.3-0ubuntu0.2
   libdrm2  2.4.56-1~ubuntu1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3.1
  SourcePackage: notify-osd
  UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42992PG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42992PG
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1412709/+subscriptions

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

[Dx-packages] [Bug 1414613] Re: Replace gnome-icon-theme with adwaita-icon-theme

[Iain Lane]

** Changed in: gnome-themes-standard (Ubuntu)
   Status: New = Fix Released

** Changed in: ubuntu-themes (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-asset-pool in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1414613

Title:
  Replace gnome-icon-theme with adwaita-icon-theme

Status in adwaita-icon-theme package in Ubuntu:
  Fix Released
Status in apturl package in Ubuntu:
  Fix Released
Status in brasero package in Ubuntu:
  Fix Released
Status in cheese package in Ubuntu:
  Fix Released
Status in empathy package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Fix Released
Status in gnome-themes-standard package in Ubuntu:
  Fix Released
Status in gtkhtml4.0 package in Ubuntu:
  Fix Released
Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in metacity package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity-asset-pool package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  We want to replace the old gnome-icon-theme with the new adwaita-icon-
  theme in Ubuntu.

  But we do not want both on the CD at once, so let's block them in
  proposed until the transition is complete.

  laney@vivid reverse-depends -c main gnome-icon-theme
  Reverse-Recommends
  ==
  * cheese
  * file-roller
  * gnome-calculator
  * libbrasero-media3-1

  Reverse-Depends
  ===
  * apturl
  * brasero
  * empathy
  * evolution
  * gnome-icon-theme-full
  * gnome-icon-theme-symbolic
  * gnome-screensaver
  * gnome-themes-standard-data
  * humanity-icon-theme
  * ibus
  * libgtkhtml-4.0-common
  * metacity
  * network-manager-gnome
  * rhythmbox
  * system-config-printer-gnome
  * totem
  * ubuntu-mono
  * unity-asset-pool
  * unity-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1414613/+subscriptions

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