date:20190417

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1825197/+attachment/5256637/+files/ProcCpuinfoMinimal.txt

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC.

[Desktop-packages] [Bug 1825197] Re: system unresponse for several seconds a couple of times per hour [Attempting to call back into JSAPI during the sweeping phase of GC...]

apport information

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

** Description changed:

  My system is up-to-date on:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1
  
  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.
  
  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).
  
  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The off

[Desktop-packages] [Bug 1825197] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1825197/+attachment/5256636/+files/GsettingsChanges.txt

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. Thi

[Desktop-packages] [Bug 1825197] ProcEnviron.txt

apport information

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

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most

[Desktop-packages] [Bug 1825197] Re: system unresponse for several seconds a couple of times per hour [Attempting to call back into JSAPI during the sweeping phase of GC...]

Thanks for the feedback!
I just send in the report collected by apport-collect, hope it helps.

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or

[Desktop-packages] [Bug 1815354] Re: BCM 43142 driver not installed - no WiFi

2019-04-17 Thread Walter Lapchynski

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

** This bug has been marked a duplicate of bug 1825286
   Calamares installer lacks a way to install proprietary drivers

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

Title:
  BCM 43142 driver not installed - no WiFi

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019

  BCM 43142 drivers not installed resulting in no WiFi during and after
  installation.

  I was able to attach ethernet cable and use the command line "ubuntu-
  drivers" command to install the drivers and all worked well after
  that.

  Of course if running a machine with no ethernet then this is a huge
  problem for the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1815354/+subscriptions

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

[Desktop-packages] [Bug 1824910] Re: ubuntu-drivers fail to install Nvidia divers without Internet connection in Lubuntu Disco Dingo

2019-04-17 Thread Walter Lapchynski

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

** This bug has been marked a duplicate of bug 1825286
   Calamares installer lacks a way to install proprietary drivers

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

Title:
  ubuntu-drivers fail to install Nvidia divers without Internet
  connection in Lubuntu Disco Dingo

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Expected results:
  1. Perform a fresh Lubuntu Disco Dingo installation with no network.
  2. Reboot the system. 
  3. On first boot, while the system is still disconnected, issue 
`ubuntu-drivers autoinstall` to install Nvidia display drivers.
  4. Nvidia display drivers are installed.

  Actual results:
  1. ubuntu-drivers attempts to connect to the Internet (system is 
disconnected) and drivers fail to install.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-drivers-common 1:0.6.3
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Mon Apr 15 21:15:32 2019
  InstallationDate: Installed on 2019-04-16 (0 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1824910/+subscriptions

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

[Desktop-packages] [Bug 603402]

2019-04-17 Thread Philippe Cloutier

I have had 2 Thunderbird 45 instances for the same Gmail account open in
the last weeks, viewing the All Mail folder while I was deleting mails
from that folder. On several occasions, I noticed after deleting and/or
tagging mails from one instance that the other instance wasn't updated.
The deleted mails would still show, and would keep showing even after
"Get Messages". There was no activity shown, and even Activity Manager
showed nothing going on. If I remember correctly, this fixed between 1
and 5 minutes after going back to the outdated instance (Thunderbird
would take the initiative to update, even though it had been asked
before).

It seems like after a while Thunderbird goes in some kind of sleep mode,
and has trouble waking up from that, but it hasn't happened often enough
for me to explain the precise conditions needed for this to happen.

I do not fully understand Summary and am unable to parse several
comments, and as it would take an eternity to go through all other
comments, I will assume that the symptoms I experienced are results of
the bug reported here and add a vote.

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

Title:
  Thunderbird incorrectly shows some Gmail archived messages as unread
  via IMAP

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Steps to reproduce:
  1) Wait for a few messages to arrive in Inbox, thus being marked as unread.
  2) Mark all of them as read, then archive them.
  3) Click on All Mail folder.

  Actual Results:
  Only one of recently archived messages is marked as read (usually the newest 
one), the rest must be marked as read again.

  Expected Results:
  All of recently marked as read in Inbox and archived mails should be marked 
as read in All Mail folder, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jul  9 02:22:30 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 603402]

2019-04-17 Thread Aaron-hastings11

Still seems to be an issue for me with Gmail. At least I assume this is
the same issue. In my case, I filter all emails into folders (or
"labels" as Gmail calls them) on the server. So all emails sent directly
to *my* email address go to a folder/label called "Me".

== Steps to reproduce ==
1. Open Thunderbird.
2. Open arbitrary email app on phone/other computer. Send email to Gmail 
account.

== Expected results ==
Within seconds, Thunderbird displays the new mail in the "Me" folder, complete 
with a notification.

== Actual results ==


== Completely manual "workaround" ==
Click the "Me" folder. Thunderbird instantly displays the new message.

I note that even clicking "Get Messages" doesn't pull down the new
message. What the heck? Clicking the folder gets a new message from the
server but clicking "Get Messages" doesn't?

I have tried what I think is everything from this thread: disabled IDLE
and changed max_cached_connections to 1. My CONDSTORE was actually
"false" by default (Thunderbird 38.2.0 on OS X) so I left that as-is. I
did a complete Exit of Thunderbird and restarted. No difference
whatsoever.

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

Title:
  Thunderbird incorrectly shows some Gmail archived messages as unread
  via IMAP

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Steps to reproduce:
  1) Wait for a few messages to arrive in Inbox, thus being marked as unread.
  2) Mark all of them as read, then archive them.
  3) Click on All Mail folder.

  Actual Results:
  Only one of recently archived messages is marked as read (usually the newest 
one), the rest must be marked as read again.

  Expected Results:
  All of recently marked as read in Inbox and archived mails should be marked 
as read in All Mail folder, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jul  9 02:22:30 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 603402]

2019-04-17 Thread Vseerror

*** Bug 1030044 has been marked as a duplicate of this bug. ***

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

Title:
  Thunderbird incorrectly shows some Gmail archived messages as unread
  via IMAP

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Steps to reproduce:
  1) Wait for a few messages to arrive in Inbox, thus being marked as unread.
  2) Mark all of them as read, then archive them.
  3) Click on All Mail folder.

  Actual Results:
  Only one of recently archived messages is marked as read (usually the newest 
one), the rest must be marked as read again.

  Expected Results:
  All of recently marked as read in Inbox and archived mails should be marked 
as read in All Mail folder, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jul  9 02:22:30 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 603402]

2019-04-17 Thread Vseerror

*** Bug 987626 has been marked as a duplicate of this bug. ***

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

Title:
  Thunderbird incorrectly shows some Gmail archived messages as unread
  via IMAP

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Steps to reproduce:
  1) Wait for a few messages to arrive in Inbox, thus being marked as unread.
  2) Mark all of them as read, then archive them.
  3) Click on All Mail folder.

  Actual Results:
  Only one of recently archived messages is marked as read (usually the newest 
one), the rest must be marked as read again.

  Expected Results:
  All of recently marked as read in Inbox and archived mails should be marked 
as read in All Mail folder, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jul  9 02:22:30 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 603402]

2019-04-17 Thread Vseerror

*** Bug 945493 has been marked as a duplicate of this bug. ***

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

Title:
  Thunderbird incorrectly shows some Gmail archived messages as unread
  via IMAP

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Steps to reproduce:
  1) Wait for a few messages to arrive in Inbox, thus being marked as unread.
  2) Mark all of them as read, then archive them.
  3) Click on All Mail folder.

  Actual Results:
  Only one of recently archived messages is marked as read (usually the newest 
one), the rest must be marked as read again.

  Expected Results:
  All of recently marked as read in Inbox and archived mails should be marked 
as read in All Mail folder, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jul  9 02:22:30 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Sebastien Bacher

Thanks for testing, it confirms it's a kernel issue (and see the status
is still wrong, worth reporting upstream probably)

** Package changed: gnome-power-manager (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Battery level stuck at 100% and Estimating...

Status in linux package in Ubuntu:
  New

Bug description:
  Battery applet does not display battery charge. Always shows 100%.

  ASUS 1215T-RED008S.
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Установлен: 1:3.28.2-0ubuntu0.18.04.2
Кандидат:   1:3.28.2-0ubuntu0.18.04.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 00:48:18 2019
  InstallationDate: Installed on 2019-04-10 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref

** Changed in: gedit
   Status: New => Fix Released

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

Title:
  
/usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref

Status in gedit:
  Fix Released
Status in gedit package in Ubuntu:
  In Progress
Status in gedit source package in Disco:
  In Progress

Bug description:
  [Impact]
  Gedit crashes when it is closed while a file is being loaded or just after 
the file has been loaded.

  The bug is a regression in Disco: in Cosmic Gedit is built using
  autotools while in Disco we use meson. During the port to meson
  upstream forgot to port a build option (in particular 'enable-gvfs-
  metadata', enabled by default). Without this option a broken - and
  untested - code path is activated.

  To fix this bug we should reintroduce the 'enable-gvfs-metadata'
  option.

  [Test case]
  1. Create a big text file
  2. Open gedit
  3. Close the window while the file is still being loaded

  Also check there are no more reports in e.u.c.

  [Regression Potential]
  The change affects the way gedit stores the file metadata. Try for example
  1. open a file
  2. focus a random line
  3. close the file
  4. re-open the file
  5. make sure the random line that you focused in point 2. is focused

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

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

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

[Desktop-packages] [Bug 1756979] Re: RM: gcc-5: no longer used

Removing packages:
gcc-5 5.5.0-12ubuntu8 in disco
cpp-5 5.5.0-12ubuntu8 in disco amd64
cpp-5 5.5.0-12ubuntu8 in disco arm64
cpp-5 5.5.0-12ubuntu8 in disco armhf
cpp-5 5.5.0-12ubuntu8 in disco i386
cpp-5 5.5.0-12ubuntu8 in disco ppc64el
cpp-5 5.5.0-12ubuntu8 in disco s390x
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco amd64
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco arm64
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco armhf
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco i386
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco ppc64el
cpp-5-dbgsym 5.5.0-12ubuntu8 in disco s390x
cpp-5-doc 5.5.0-12ubuntu8 in disco amd64
cpp-5-doc 5.5.0-12ubuntu8 in disco arm64
cpp-5-doc 5.5.0-12ubuntu8 in disco armhf
cpp-5-doc 5.5.0-12ubuntu8 in disco i386
cpp-5-doc 5.5.0-12ubuntu8 in disco ppc64el
cpp-5-doc 5.5.0-12ubuntu8 in disco s390x
g++-5 5.5.0-12ubuntu8 in disco amd64
g++-5 5.5.0-12ubuntu8 in disco arm64
g++-5 5.5.0-12ubuntu8 in disco armhf
g++-5 5.5.0-12ubuntu8 in disco i386
g++-5 5.5.0-12ubuntu8 in disco ppc64el
g++-5 5.5.0-12ubuntu8 in disco s390x
g++-5-dbgsym 5.5.0-12ubuntu8 in disco amd64
g++-5-dbgsym 5.5.0-12ubuntu8 in disco arm64
g++-5-dbgsym 5.5.0-12ubuntu8 in disco armhf
g++-5-dbgsym 5.5.0-12ubuntu8 in disco i386
g++-5-dbgsym 5.5.0-12ubuntu8 in disco ppc64el
g++-5-dbgsym 5.5.0-12ubuntu8 in disco s390x
g++-5-multilib 5.5.0-12ubuntu8 in disco amd64
g++-5-multilib 5.5.0-12ubuntu8 in disco armhf
g++-5-multilib 5.5.0-12ubuntu8 in disco i386
g++-5-multilib 5.5.0-12ubuntu8 in disco s390x
gcc-5 5.5.0-12ubuntu8 in disco amd64
gcc-5 5.5.0-12ubuntu8 in disco arm64
gcc-5 5.5.0-12ubuntu8 in disco armhf
gcc-5 5.5.0-12ubuntu8 in disco i386
gcc-5 5.5.0-12ubuntu8 in disco ppc64el
gcc-5 5.5.0-12ubuntu8 in disco s390x
gcc-5-base 5.5.0-12ubuntu8 in disco amd64
gcc-5-base 5.5.0-12ubuntu8 in disco arm64
gcc-5-base 5.5.0-12ubuntu8 in disco armhf
gcc-5-base 5.5.0-12ubuntu8 in disco i386
gcc-5-base 5.5.0-12ubuntu8 in disco ppc64el
gcc-5-base 5.5.0-12ubuntu8 in disco s390x
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco amd64
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco arm64
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco armhf
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco i386
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco ppc64el
gcc-5-dbgsym 5.5.0-12ubuntu8 in disco s390x
gcc-5-doc 5.5.0-12ubuntu8 in disco amd64
gcc-5-doc 5.5.0-12ubuntu8 in disco arm64
gcc-5-doc 5.5.0-12ubuntu8 in disco armhf
gcc-5-doc 5.5.0-12ubuntu8 in disco i386
gcc-5-doc 5.5.0-12ubuntu8 in disco ppc64el
gcc-5-doc 5.5.0-12ubuntu8 in disco s390x
gcc-5-hppa64-linux-gnu 5.5.0-12ubuntu8 in disco amd64
gcc-5-hppa64-linux-gnu 5.5.0-12ubuntu8 in disco i386
gcc-5-hppa64-linux-gnu-dbgsym 5.5.0-12ubuntu8 in disco amd64
gcc-5-hppa64-linux-gnu-dbgsym 5.5.0-12ubuntu8 in disco i386
gcc-5-locales 5.5.0-12ubuntu8 in disco amd64
gcc-5-locales 5.5.0-12ubuntu8 in disco arm64
gcc-5-locales 5.5.0-12ubuntu8 in disco armhf
gcc-5-locales 5.5.0-12ubuntu8 in disco i386
gcc-5-locales 5.5.0-12ubuntu8 in disco ppc64el
gcc-5-locales 5.5.0-12ubuntu8 in disco s390x
gcc-5-multilib 5.5.0-12ubuntu8 in disco amd64
gcc-5-multilib 5.5.0-12ubuntu8 in disco armhf
gcc-5-multilib 5.5.0-12ubuntu8 in disco i386
gcc-5-multilib 5.5.0-12ubuntu8 in disco s390x
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco amd64
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco arm64
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco armhf
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco i386
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco ppc64el
gcc-5-plugin-dev 5.5.0-12ubuntu8 in disco s390x
gcc-5-plugin-dev-dbgsym 5.5.0-12ubuntu8 in disco amd64
gcc-5-plugin-dev-dbgsym 5.5.0-12ubuntu8 in disco arm64
gcc-5-plugin-dev-dbgsym 5.5.0-12ubuntu8 in disco armhf
gcc-5-plugin-dev-dbgsym 5.5.0-12ubuntu8 in disco i386
gcc-5-plugin-dev-dbgsym 5.5.0

[Desktop-packages] [Bug 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty

2019-04-17 Thread Robert Ancell

Closing the gnome-software tasks as we downgraded.

** No longer affects: gnome-software (Ubuntu)

** No longer affects: gnome-software (Ubuntu Disco)

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

Title:
  [disco-proposed] The list of applications in Ubuntu Software is empty

Status in libxmlb package in Ubuntu:
  Fix Released
Status in libxmlb source package in Disco:
  Fix Released

Bug description:
  Hi

  The COMPLETE LIST of applications in Ubuntu Software is not showing up

  See attached image

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.31.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 19:11:23 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.31.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/d

This problem is probably related to:

"Following Mutter's 3.32.1 release, meanwhile, the developers have now
hard-enforced a requirement that graphics drivers on the system either
support OpenGL 2.1 or OpenGL ES 2.0 as a minimum."

[https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Shell-
Mutter-3.32.1]

Although Mesa offers software rendering which supports newer OpenGL.
Therefore gdm3 and mutter *should* be detecting that the GPU is too old
and falling back. It's a semi-regular problem though, that gdm3 and
mutter fail to fall back reliably and the login screen never appears.



** Summary changed:

- With AutomaticLogin enabled, logging out lands me on a black screen that's 
unresponsive to any keyboard input
+ With AutomaticLogin enabled, logging out lands me on a black screen that's 
unresponsive to any keyboard input [gnome-shell: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs]

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

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

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

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input [gnome-shell: Failed to
  initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL
  configs]

Status in gdm3 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Just testing Disco and wanted to see what login options are available
  after adding 'gnome-shell-extensions' and found that logging out lands
  me on a black screen that's unresponsive to any keyboard input. I'll
  test on some slightly different hardware soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 16:18:56 2019
  InstallationDate: Installed on 2019-04-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523

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

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

[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically

2019-04-17 Thread Mathew Hodson

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

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

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

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

Title:
  USB stick isn't mounted automatically

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Xenial:
  New

Bug description:
  [Impact]

  USB stick isn't mounted automatically. Auto-mount function fails.

  [Test Case]

  1) Plug USB stick and check if USB stick is mounted automatically.

  2) Umount USB stick

  3) Unplug USB stick

  4) Go to 1)

  ---

  If the error message below appears, auto-mount function will fail.
  systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file 
or directory

  Error Message:

  1. when auto-mount fails:
  kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6
  systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file 
or directory
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0
  kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using 
xhci_hcd
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470

  2. when auto-mount works:
  kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 
drive_disconnected
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330
  kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using 
xhci_hcd
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 
drive_connected
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0
  org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount
  udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

Now clarified statuses properly :)

** Also affects: mutter (Ubuntu Disco)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

** Also affects: mutter (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: gnome-shell (Ubuntu Disco)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: mutter (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: mutter (Ubuntu Disco)
   Status: Fix Released => Invalid

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

** No longer affects: gnome-shell (Ubuntu Cosmic)

** No longer affects: mutter (Ubuntu Cosmic)

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in th

When you see X11 code in the gnome-shell process of a Wayland session
that's nothing unusual. It just means some X11 app is running, talking
to Xwayland and gnome-shell (which is both the Wayland display server
AND the X11 window manager in this case).

Since this bug is about a particular "BadWindow (invalid Window
parameter)", maybe it is specific to Evolution?...

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

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

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

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Mathew Hodson

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

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

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in th

2019-04-17 Thread Joe Barnett

Not sure if related, but I do run under wayland (weird that it looks
like an X11 error then, especially as evolution runs wayland native?),
with fractional zooming on my laptop panel @ 175% and usually have an
external, lower resolution screen at 100% scaling.  Evolution is usually
the first app i open and stays open throughout my session, so has
usually been running for days before being closed (and killing the
session) -- but sometimes closing it is fine.  Haven't seen any other
app trigger it.

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY

Also assigned to xorg-server, because Xorg should be intercepting
Alt+KEY. If Xorg fails to do so and somehow the key events get sent to
the VT then we get the unwanted VT's interpretation of Alt+KEY.

** Description changed:

+ WORKAROUND:
+ 
+ sudo kbd_mode -s
+ 
+ ORIGINAL DESCRIPTION:
+ 
  I'm running Ubuntu Lucid development branch.
  
  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.
  
  I'm pretty sure that my keyboard is not malfunctioning as I can use all
  my applications normally. (Pressing O and Ctrl-O do not have the same
  effect.)
  
  I'm not sure which package I should file this bug against. I'll happily
  do an apport-collect once I know.

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

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

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

** Summary changed:

- Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
+ Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from 
Alt+Left/Right

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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

[Desktop-packages] [Bug 1825197] Re: system unresponse for several seconds a couple of times per hour

Thanks for the bug report. I have encountered the same problems myself
this week when stress testing parts of gnome-shell. But those parts and
the cause might be different to yours. So please run:

  apport-collect 1825197

to send us more information about the system.


** Tags added: cosmic

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

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

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: =

[Desktop-packages] [Bug 1825197] Re: system unresponse for several seconds a couple of times per hour

As far as I can tell, the common error (from gjs):

Attempting to call back into JSAPI during the sweeping phase of GC. This
is most likely caused by not destroying a Clutter actor or Gtk+ widget
with ::destroy signals connected, but can also be caused by using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked and the JS callback not invoked.

is caused by a type of mistake that has been made in JavaScript
locations. And that mistake is common, in multiple locations in gnome-
shell and its extensions. Although I don't yet understand what that
mistake looks like in code :(

** Summary changed:

- system unresponse for several seconds a couple of times per hour 
+ system unresponse for several seconds a couple of times per hour [Attempting 
to call back into JSAPI during the sweeping phase of GC...]

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My system is up-to-date on:

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1

  To provide you with an idea of the motivation for the origin in gnome-
  shell; I've included the lines in syslog that are displayed for many
  more occasions than presented below.

  At the times that these messages are displayed in my logs I can still
  move my mouse, but mouse clicks are unresponsive and typing is frozen
  (but text does appear after freeze).

  
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
  Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was 
g-signal on GDBusProxy 0x55f9f7e68eb0.
  Apr 17 09:30:25 TUE001295 gnom

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

OK, I give in... Since this bug is so popular and I can't find any
explicit code fix we can reopen this one. Unfortunately I still cannot
reproduce this bug myself.

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

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

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

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

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

** Tags removed: artful
** Tags added: bionic

** Tags added: cosmic

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

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

** This bug is no longer a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot
** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I have two displays, one on display port, and one on VGA. The display
  port display is a Seiki Pro 40" display in landscape at 3840x2160. The
  VGA is an HP 24" display in portrait at 1920x1200.

  If I boot with either display by itself, everything works fine. If I
  plug in the other display and configure it to run multidisplay,
  everything is fine.

  When I reboot, the display settings are changed from "Join Displays"
  to "Mirror", the 40" is set to 1920x1200 landscape (which it cannot
  actually do), and the 24" is set to 1920x1200 landscape. The 24" is
  also set to primary (whereas I selected the 40" as primary before
  rebooting.)

  The 40" display is messed up with overdraw, etc. In addition, I can no
  longer select 3840x2160 for the 40". If I turn of the 40" and turn it
  on again, eventually the settings box will let me select 3840x2160.
  Once I select it, the screen flashes but does not come back to
  3840x2160. (ie., it is still corrupted with overdraw and presumably
  running at 1920x1200.). If I toggle the display power several times,
  it will eventually come back running at the correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 10:58:08 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

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

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

[Desktop-packages] [Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

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

Actually, let's use bug 1292398 since that's the one most users are
finding.

** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After connecting my laptop to the external monitor I set up different
  resolutions for the external and internal screens and their layout.
  After I log out or reboot and then connect it doesn't remember those
  settings and I have to do it all over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 09:17:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=376bf665-7419-4f99-b83c-c6f9ad13c0b6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET45W(1.30):bd02/22/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

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

** This bug is no longer a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot
** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  monitors.xml is not parsed or applied correctly during login after
  reboot or shutdown

Status in gdm:
  New
Status in Mutter:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  WORKAROUND

  Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver
  + numlockx(optionally)

  
  TL;DR

  Correct positioning and working of multiple displays until reboot or
  shutdown and then subsequent login from gdm3. HDMI monitor(projector)
  goes blank and the VGA monitor only shows 'Secondary' monitor screen
  without any user visible controls or windows as they are all being
  painted to the now blanked 'Primary' HDMI connected display.

  REPRODUCTION

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a FHD projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session.

  However, after a reboot or power cycle of the computer and a
  successful login from GDM(gdm3), the HDMI goes dark(blank?) and the
  VGA monitor shows as 'Secondary' monitor even though I set it as
  'Primary' in the "Displays" dialog.

  The monitors.xml file, attached, shows the correct layout and survives
  the reboot without alteration.

  I am unable to see anything on the 'Primary' display, which has
  incorrectly been given to the HDMI projector. Unseating the HDMI cable
  does not restore the VGA to 'Primary' display automatically and I must
  reboot the computer while leaving the HDMI unplugged in order to
  restore my ability to see the 'Primary' display on the VGA connection.

  Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is
  repeatedly provable through multiple reboots or changes to the logical
  layout of the screens in the 'Displays' settings of gnome-control-
  center.

  ERRORS(syslog)

  "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  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: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

Everyone please ensure you are actually logging in again too :)

If you're only concerned about the login screen then that is bug
1760849.

** Tags added: multimonitor

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After connecting my laptop to the external monitor I set up different
  resolutions for the external and internal screens and their layout.
  After I log out or reboot and then connect it doesn't remember those
  settings and I have to do it all over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 09:17:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=376bf665-7419-4f99-b83c-c6f9ad13c0b6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET45W(1.30):bd02/22/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1580451] Re: mutter does not remember position of extra displays

Tim,

Do you see the same bug in 18.04 or later?

** Description changed:

+ https://bugzilla.gnome.org/show_bug.cgi?id=747529
+ 
  If you have a laptop where you irregularly use the external monitor,
  mutter will forget the position when you turn off/on the monitor.

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

Title:
  mutter does not remember position of extra displays

Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=747529

  If you have a laptop where you irregularly use the external monitor,
  mutter will forget the position when you turn off/on the monitor.

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

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

[Desktop-packages] [Bug 509661] Re: Screen layout not remembered

Thank you for reporting this bug to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Screen layout not remembered

Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gnome-control-center

  The gnome-display-properties panel does not remember the layout of the
  screen, and is also affected by a bug similar to #351900 where
  changing the layout will garble the X display and force me to
  disconnect.

  In my case, I have a laptop with a dock and an external monitor
  plugged to the dock. Every time I put the laptop back in the dock, I
  have to start the display properties, re-adjust the screen layout
  (external monitor to the left, laptop to the right) and click "apply"
  -- these settings should be remembered.

  Also after hitting "apply", the X display is garbled (parts of the
  laptop screen are displayed on the external monitor), which forces me
  to disconnect and reconnect for everything to work fine.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Jan 19 09:32:55 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-display-properties
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: gnome-control-center 1:2.28.1-0ubuntu1
  ProcEnviron:
   LANG=fr_CA.UTF-8
   SHELL=/usr/bin/tcsh
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: gnome-control-center
  Uname: Linux 2.6.31-17-generic i686

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in th

Unless you can think of anything that's special or unusual about your
system that triggers this bug?

It took a while, but we now are getting other reports of this same crash via:
https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

** Description changed:

+ https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978
+ 
  Had this happen a few times now, where closing the main evolution window
  (last visible window on desktop) results in a gnome-shell crash (see bug
  1821262)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After connecting my laptop to the external monitor I set up different
  resolutions for the external and internal screens and their layout.
  After I log out or reboot and then connect it doesn't remember those
  settings and I have to do it all over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 09:17:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=376bf665-7419-4f99-b83c-c6f9ad13c0b6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET45W(1.30):bd02/22/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

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

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


** This bug has been marked a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot

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

Title:
  monitors.xml is not parsed or applied correctly during login after
  reboot or shutdown

Status in gdm:
  New
Status in Mutter:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  WORKAROUND

  Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver
  + numlockx(optionally)

  
  TL;DR

  Correct positioning and working of multiple displays until reboot or
  shutdown and then subsequent login from gdm3. HDMI monitor(projector)
  goes blank and the VGA monitor only shows 'Secondary' monitor screen
  without any user visible controls or windows as they are all being
  painted to the now blanked 'Primary' HDMI connected display.

  REPRODUCTION

  After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED
  monitor to the VGA port of a DELL Optiplex 390 desktop tower,
  connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with
  a FHD projector and then configuring the logical monitor layout in the
  "Displays" settings dialog, I can successfully create and use a multi
  monitor setup in my current session.

  However, after a reboot or power cycle of the computer and a
  successful login from GDM(gdm3), the HDMI goes dark(blank?) and the
  VGA monitor shows as 'Secondary' monitor even though I set it as
  'Primary' in the "Displays" dialog.

  The monitors.xml file, attached, shows the correct layout and survives
  the reboot without alteration.

  I am unable to see anything on the 'Primary' display, which has
  incorrectly been given to the HDMI projector. Unseating the HDMI cable
  does not restore the VGA to 'Primary' display automatically and I must
  reboot the computer while leaving the HDMI unplugged in order to
  restore my ability to see the 'Primary' display on the VGA connection.

  Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is
  repeatedly provable through multiple reboots or changes to the logical
  layout of the screens in the 'Displays' settings of gnome-control-
  center.

  ERRORS(syslog)

  "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  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: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After connecting my laptop to the external monitor I set up different
  resolutions for the external and internal screens and their layout.
  After I log out or reboot and then connect it doesn't remember those
  settings and I have to do it all over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 09:17:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=376bf665-7419-4f99-b83c-c6f9ad13c0b6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET45W(1.30):bd02/22/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After connecting my laptop to the external monitor I set up different
  resolutions for the external and internal screens and their layout.
  After I log out or reboot and then connect it doesn't remember those
  settings and I have to do it all over again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 09:17:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=376bf665-7419-4f99-b83c-c6f9ad13c0b6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET45W(1.30):bd02/22/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

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

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


** This bug has been marked a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I have two displays, one on display port, and one on VGA. The display
  port display is a Seiki Pro 40" display in landscape at 3840x2160. The
  VGA is an HP 24" display in portrait at 1920x1200.

  If I boot with either display by itself, everything works fine. If I
  plug in the other display and configure it to run multidisplay,
  everything is fine.

  When I reboot, the display settings are changed from "Join Displays"
  to "Mirror", the 40" is set to 1920x1200 landscape (which it cannot
  actually do), and the 24" is set to 1920x1200 landscape. The 24" is
  also set to primary (whereas I selected the 40" as primary before
  rebooting.)

  The 40" display is messed up with overdraw, etc. In addition, I can no
  longer select 3840x2160 for the 40". If I turn of the 40" and turn it
  on again, eventually the settings box will let me select 3840x2160.
  Once I select it, the screen flashes but does not come back to
  3840x2160. (ie., it is still corrupted with overdraw and presumably
  running at 1920x1200.). If I toggle the display power several times,
  it will eventually come back running at the correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 10:58:08 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

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

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

[Desktop-packages] [Bug 1825270] Re: /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

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

** This bug has been marked a duplicate of bug 1821427
   gnome-shell crashed with signal 5 when closing evolution, logging "The 
program 'gnome-shell' received an X Window System error.\nThis probably 
reflects a bug in the program.\nThe error was 'BadWindow (invalid Window 
parameter)'.\n  (Details: serial 333851 error_code 3 r"

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in th

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in th

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

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

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1825270] [NEW] /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

2019-04-17 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: disco

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

No, not directly, but kind of :)

The option to start a Wayland session is enabled by adding:

  nvidia-drm.modeset=1

to your kernel command line.

Secondly, mutter's Wayland backend needs to be found to WORK with it. If
it doesn't work (this bug), then mutter will hide the Wayland option
before you ever see the login screen.

So you should:

  1. Add nvidia-drm.modeset=1 to your kernel command line; and
  2. Either wait for this bug to be fixed in 18.04 or just use a later Ubuntu 
release which doesn't have this bug.

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [ Fix ]

  See below for the changes from upstream that fix this, which we're
  uploading to disco-proposed now.

  [ QA ]

  Under the GNOME Micro Release Exception, you can believe this is
  fixed.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It might be a good idea to test an nvidia machine, but it doesn't need
  explicit verification.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1824103] Re: aplay record file failed always.

2019-04-17 Thread Gabriel Zhi Chen

Retest the issue on Yoda2-2, image : Disco-Daily-20190416, it can not
reproduce anymore.

The test.wav file can record and play normally.

When executing commands arecord and aplay, there is no error info
feedback also.

** Tags added: cqa-verified

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

Title:
  aplay record file failed always.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord abc.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay abc.wav" in terminal

  Expected result:
  The voice played smoothly.

  Actual result:
  Step 3, 
  u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav
  Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
  ^CAborted by signal Interrupt...
  arecord: pcm_read:2145: read error: Interrupted system call

  Step 6,
  u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav 
  ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
  aplay: main:828: audio open error: Device or resource busy

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

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

[Desktop-packages] [Bug 1766192] Re: [snap] cannot save file under $HOME

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

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

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

Title:
  [snap] cannot save file under $HOME

Status in snapd:
  Triaged
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  (this was initially reported on the forum:
  https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032)

  When trying to save a file under $HOME (not a subdirectory), the user
  is presented with an error dialog:

  --- Error ---
  Error saving the document Untitled 1:
  Object not accessible.
  The object cannot be accessed
  due to insufficient user rights.
  [OK]

  This is because libreoffice tries to create a lock file of the form:
  "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow
  writing hidden files (those with a filename that starts with a dot)
  under $HOME.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  DESKTOP_SESSION=ubuntu
  GTK_MODULES=gail:atk-bridge
  HOME=/home/osomon/snap/libreoffice/59
  LANG=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa
  
PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  SNAP=/snap/libreoffice/59
  SNAP_ARCH=amd64
  SNAP_COMMON=/var/snap/libreoffice/common
  SNAP_DATA=/var/snap/libreoffice/59
  
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
  SNAP_NAME=libreoffice
  SNAP_REEXEC=
  SNAP_REVISION=59
  SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
  SNAP_USER_DATA=/home/osomon/snap/libreoffice/59
  SNAP_VERSION=6.0.3.2
  TEMPDIR=/tmp
  TMPDIR=/run/user/1000/snap.libreoffice
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=x11

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

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

[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2019-04-17 Thread Martin Wimpress

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Opinion

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

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

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

[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

** Changed in: gstreamer
   Status: Unknown => Fix Released

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

Status in GStreamer:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91

  ---

  Backtrace goes through:

  totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
  gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
  libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)

  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.

  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---

  I.e. bug is in what is given to Mesa, not what Mesa does.

  -> NOTOURBUG

  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  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/gstreamer/+bug/1758287/+subscriptions

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

[Desktop-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin

I booted from the LiveCD 19.04. Although charging status is indicated
the other way round, percentages are correct and decrease with battery
discharge.

How tired I am of this...
Ubuntu does not work normally on any of the last ten computers...

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

Title:
  Battery level stuck at 100% and Estimating...

Status in gnome-power-manager package in Ubuntu:
  Incomplete

Bug description:
  Battery applet does not display battery charge. Always shows 100%.

  ASUS 1215T-RED008S.
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Установлен: 1:3.28.2-0ubuntu0.18.04.2
Кандидат:   1:3.28.2-0ubuntu0.18.04.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 00:48:18 2019
  InstallationDate: Installed on 2019-04-10 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1825060] Re: libreoffice

2019-04-17 Thread Miguel Ángel Rodríguez Uría

Hi, I have tested the beta of Ubuntu 19.04 and it seems that it is
already fixed. I will wait to update. Thank you and sorry for the
inconvenience.


El mié, 17-04-2019 a las 09:19 +, Sebastien Bacher escribió:
> Thank you for taking the time to report this bug and helping to
> makeUbuntu better. Unfortunately, we cannot work on this bug because
> yourdescription didn't include enough information. You may find it
> helpfulto read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be
> gratefulif you would then provide a more complete description of the
> problem.
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures.
> At a minimum, we need:1. The specific steps or actions you took that
> caused you to encounter the problem.2. The behavior you expected.3.
> The behavior you actually encountered (in as much detail as
> possible).Thanks! 
> ** Changed in: libreoffice (Ubuntu)   Importance: Undecided => Low
> ** Changed in: libreoffice (Ubuntu)   Status: New => Incomplete
>

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

Title:
  libreoffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  In Libreoffice you can not put mosaic window from version 6.0

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

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

[Desktop-packages] [Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-04-17 Thread FN

1) Uninstalled hplip-3.17.1
2) Did a fresh install of hplip-3.19.3
3) Installed the plugin

Still getting

-- Reboot --
Apr 17 20:28:21 xps13 systemd[1]: Started CUPS Scheduler.
Apr 17 20:33:22 xps13 systemd[1]: Stopping CUPS Scheduler...
Apr 17 20:33:22 xps13 systemd[1]: Stopped CUPS Scheduler.
Apr 17 20:33:22 xps13 systemd[1]: Started CUPS Scheduler.
Apr 17 22:48:38 xps13 hpcups[24442]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG:
imageProcessorStartPage failed result = 2
Apr 17 22:49:23 xps13 hpcups[24471]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG:
imageProcessorStartPage failed result = 2
Apr 17 22:51:08 xps13 hpcups[24526]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG:
imageProcessorStartPage failed result = 2

When I print a test page

** Attachment added: "hp-check.log"

https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1812582/+attachment/5256606/+files/hp-check.log

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

Title:
Unable to install hplip 3.18.12 on linux mint 19.1

Status in HPLIP:
In Progress
Status in hplip package in Ubuntu:
Confirmed

Bug description:
RESTART OR RE-PLUG IS REQUIRED
--
If you are installing a USB connected printer, and the printer was plugged in
when you started this installer, you
will need to either restart your PC or unplug and re-plug in your printer
(USB cable only). If you choose to restart,
run this command after restarting: hp-setup (Note: If you are using a
parallel connection, you will have to restart
your PC. If you are using network/wireless, you can ignore and continue).

Restart or re-plug in your printer (r=restart, p=re-plug in*,
i=ignore/continue, q=quit) : i

PRINTER SETUP
-
Please make sure your printer is connected and powered on at this time.
Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) :
u

HP Linux Imaging and Printing System (ver. 3.18.12)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp)
Segmentation fault
error: The device you are trying to setup requires a binary plug-in. Some
functionalities may not work as expected without plug-ins. Please run
'hp-plugin' as normal user to install plug-ins. Visit
http://hplipopensource.com for more infomation.

Segmentation fault
error: The device you are trying to setup requires a binary plug-in. Some
functionalities may not work as expected without plug-ins. Please run
'hp-plugin' as normal user to install plug-ins. Visit
http://hplipopensource.com for more infomation.

Done.

RE-STARTING HP_SYSTRAY
--

HP Linux Imaging and Printing System (ver. 3.18.12)
System Tray Status Service ver. 2.0

/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning:
PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)

:~/Downloads$ hp-plugin

HP Linux Imaging and Printing System (ver. 3.18.12)
Plugin Download and Install Utility ver. 2.1

Checking for network connection...
Downloading plug-in from:
Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg
--no-permission-warning --keyserver pgp.mit.edu --recv-keys
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
Creating directory plugin_tmp
Verifying archive integrity... All good.
Uncompressing HPLIP 3.18.12 Plugin Self Extracting
Archive.

HP Linux Imaging and Printing System (ver. 3.18.12)
Plugin Installer ver. 3.0

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

2019-04-17 Thread John W Maynard

Do you need any other input to get a fix in for this? I've tried a
number of different 'model' settings for the ALC256 to try to get this
to work to no avail.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-04-17 Thread Timo Aaltonen

Yes, the plan was to get rid of these in Debian first, maybe after
Buster..

** Changed in: xf86-input-mtrack (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  Incomplete
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  New
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1825249] [NEW] fonts garbled in firefox browser -- only on certain pages

2019-04-17 Thread C. Jeffery Small

Public bug reported:

Xubuntu 18.10 and earlier releases
Firefox browser 66.0.3 and every earlier version of the Quantum releases

There has been a font display problem on Firefox add-on pages (and a
very few other random sites) ever since the Quantum browser was
released.  I reported this to the Firefox team well over a year ago
here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1437338

with periodic follow-up here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1446688

You can see a recent example of the problem here:

http://smallthoughts.com/photos/misc/firefox_66_01.png

Now, while I'm convinced that this is likely a Firefox problem, I cannot
get anyone there to reproduce the problem.  So on the chance that it's
related to some font glitch on the Ubuntu system, I'm reporting it here
to see if anyone can reproduce the problem.  If you could load a recent
version of Firefox and visit this (or any add-on) page:

https://addons.mozilla.org/en-US/firefox/addon/autofill-
quantum/?src=search

and see if you observe what I'm observing, it would be great in helping
track down the source of this extremely annoying glitch.  BTW, this ONLY
happen in Firefox, not in the Chromium or Opera browsers, and it does
not happen in Firefox running under Windows 10 in a VM on the same
machine.

Thanks for any insights as to what might be causing this.

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

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

Title:
  fonts garbled in firefox browser -- only on certain pages

Status in firefox package in Ubuntu:
  New

Bug description:
  Xubuntu 18.10 and earlier releases
  Firefox browser 66.0.3 and every earlier version of the Quantum releases

  There has been a font display problem on Firefox add-on pages (and a
  very few other random sites) ever since the Quantum browser was
  released.  I reported this to the Firefox team well over a year ago
  here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1437338

  with periodic follow-up here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1446688

  You can see a recent example of the problem here:

  http://smallthoughts.com/photos/misc/firefox_66_01.png

  Now, while I'm convinced that this is likely a Firefox problem, I
  cannot get anyone there to reproduce the problem.  So on the chance
  that it's related to some font glitch on the Ubuntu system, I'm
  reporting it here to see if anyone can reproduce the problem.  If you
  could load a recent version of Firefox and visit this (or any add-on)
  page:

  https://addons.mozilla.org/en-US/firefox/addon/autofill-
  quantum/?src=search

  and see if you observe what I'm observing, it would be great in
  helping track down the source of this extremely annoying glitch.  BTW,
  this ONLY happen in Firefox, not in the Chromium or Opera browsers,
  and it does not happen in Firefox running under Windows 10 in a VM on
  the same machine.

  Thanks for any insights as to what might be causing this.

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

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

[Desktop-packages] [Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it

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

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

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

Title:
  System beep broken in Karmic despite heroic efforts to fix it

Status in Metacity:
  New
Status in libcanberra package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in metacity package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Between Jaunty and Karmic, a number of changes were made to keep the
  PC speaker from beeping.  As part of this, system bell events are now
  captured by metacity, which uses libcanberra to play a sound.  For
  users without speakers, this fails to be useful.  The current setup
  makes restoring the old behavior extremely difficult.

  The absolute show stopper is that metacity traps audible system bell
  events.  This behavior is, as best we can tell, not configurable.  The
  attached patch keeps metacity from capturing system bell events.  It
  also removes the sound playback capability.  As Lucid will be using
  pulse audio's module-x11-bell to play sounds for system bell events,
  it is not necessary for this capability to be in metacity.
  Additionally, this removes the discrepancy between metacity's and
  compiz's handling of system bell events.

  There are several other difficulties in enabling the system bell:
  1) Even if it is taken out of the blacklist, the pcspkr module may not load 
properly.  Another modprobe may be necessary to get it loaded.  See bug #398161.
  2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset 
b on` must be run on every login.  (Note that bug #280767 keeps you from 
setting the bell volume with xset.)
  3) A number of settings in gnome-terminal and gconf may keep the shell from 
sounding system bell events.

  Comments #28, #34, and #50 give more detailed summaries of the various
  problems.

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

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

[Desktop-packages] [Bug 1756979] Re: RM: gcc-5: no longer used

I tried merging the new upstream version from unstable, but mono (still?
again?) FTBFS on s390x, with or without the Ubuntu delta to build with
-O0. https://launchpad.net/ubuntu/+source/mono/5.18.0.240+dfsg-
2ubuntu1/+build/16646009

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

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

Title:
  RM: gcc-5: no longer used

Status in gcc-5 package in Ubuntu:
  New
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-5-cross-ports package in Ubuntu:
  Fix Released
Status in mono package in Ubuntu:
  New

Bug description:
  $ 
liblist='lib(x32|32|64|sf)?(gomp1|quadmath0|atomic1|itm1|objc4|stdc\+\+6|gfortran3|tsan0|gccjit0|ubsan0|cilkrts5|lsan0|cc1-0)'
  $ rmadison -s bionic -S gcc-5 | grep -E "\b$liblist[[:space:]]"
  $ reverse-depends src:gcc-5 | grep -vE "\b$liblist\)|-linux-gnu"
  Reverse-Recommends
  ==

  Reverse-Depends
  ===
  * gcc-5-doc (for gcc-5-base)
  * minica [s390x](for libgo7)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for gcc-5)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for g++-5)
  * pluginhook [arm64 ppc64el s390x]  (for libgo7)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  $

  gcc-5-doc is a misidentification. nvidia-cuda-toolkit are
  alternatives.  minica and pluginhook needed no-change rebuilds to use
  golang instead of gccgo; I have uploaded these now.  So once they
  migrate, gcc-5 will have no reverse-dependencies in the archive except
  for gcc-5-cross; so we should drop both of these packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1756979/+subscriptions

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread fossfreedom

confirmed that the new mutter also tries to uplift the budgie-desktop
version.

Tested the new mutter with the 4 budgie SRU's and all is ok.

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

See Bryan's question.  These are syncs from Debian, if they are
obsolete, why have they not been removed there first?

** Changed in: xf86-input-mtrack (Ubuntu)
   Status: New => Incomplete

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  Incomplete
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  New
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1525454] Re: bootstrapping mono compiler fails at mdoc

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

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

Title:
  bootstrapping mono compiler fails at mdoc

Status in mono package in Ubuntu:
  Fix Released

Bug description:
  mdoc fails when bootstrapping mono

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

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-04-17 Thread blszyn

Does it mean that gdm will show an option to start Gnome on Wayland when
using Nvidia binary drivers?

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [ Fix ]

  See below for the changes from upstream that fix this, which we're
  uploading to disco-proposed now.

  [ QA ]

  Under the GNOME Micro Release Exception, you can believe this is
  fixed.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It might be a good idea to test an nvidia machine, but it doesn't need
  explicit verification.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1756979] Re: RM: gcc-5: no longer used

mono needs a merge of a new upstream version from Debian to drop the
s390x-specific build-dependency on gcc-5.

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

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

Title:
  RM: gcc-5: no longer used

Status in gcc-5 package in Ubuntu:
  New
Status in gcc-5-cross package in Ubuntu:
  Fix Released
Status in gcc-5-cross-ports package in Ubuntu:
  Fix Released
Status in mono package in Ubuntu:
  New

Bug description:
  $ 
liblist='lib(x32|32|64|sf)?(gomp1|quadmath0|atomic1|itm1|objc4|stdc\+\+6|gfortran3|tsan0|gccjit0|ubsan0|cilkrts5|lsan0|cc1-0)'
  $ rmadison -s bionic -S gcc-5 | grep -E "\b$liblist[[:space:]]"
  $ reverse-depends src:gcc-5 | grep -vE "\b$liblist\)|-linux-gnu"
  Reverse-Recommends
  ==

  Reverse-Depends
  ===
  * gcc-5-doc (for gcc-5-base)
  * minica [s390x](for libgo7)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for gcc-5)
  * nvidia-cuda-toolkit [amd64 ppc64el]  (for g++-5)
  * pluginhook [arm64 ppc64el s390x]  (for libgo7)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  $

  gcc-5-doc is a misidentification. nvidia-cuda-toolkit are
  alternatives.  minica and pluginhook needed no-change rebuilds to use
  golang instead of gccgo; I have uploaded these now.  So once they
  migrate, gcc-5 will have no reverse-dependencies in the archive except
  for gcc-5-cross; so we should drop both of these packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1756979/+subscriptions

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

[Desktop-packages] [Bug 1825230] [NEW] She should work at Canonical

Public bug reported:

http://sylviaritter.tumblr.com/

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

** Attachment added: "tumblr_potxnhV9JD1qe0vzqo1_1280.png"
   
https://bugs.launchpad.net/bugs/1825230/+attachment/5256588/+files/tumblr_potxnhV9JD1qe0vzqo1_1280.png

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

Title:
  She should work at Canonical

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  http://sylviaritter.tumblr.com/

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

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

[Desktop-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

Removing packages from disco:
android-audiosystem 1.8+13.10.20130807-0ubuntu1 in disco
libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in 
disco armhf
libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in 
disco i386
libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco armhf
libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco i386
libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco armhf
libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco i386
Comment: Ubuntu-specific, no uploads since 2013, unmaintained; LP: #1734568
1 package successfully removed.


** Changed in: android-audiosystem (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove obsolete Android packages from Ubuntu

Status in android-audiosystem package in Ubuntu:
  Fix Released
Status in android-headers package in Ubuntu:
  New
Status in android-src-vendor package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  Ubuntu has a few Android-related packages that were never in Debian
  and are no longer maintained by anyone. Please remove them from Ubuntu
  disco.

  $ reverse-depends src:android-src-vendor 
  No reverse dependencies found
  $ reverse-depends -b src:android-src-vendor 
  No reverse dependencies found

  $ reverse-depends src:android-audiosystem
  No reverse dependencies found
  $ reverse-depends -b src:android-audiosystem
  No reverse dependencies found

  $ reverse-depends src:android-headers
  No reverse dependencies found
  $ reverse-depends -b src:android-headers
  Reverse-Build-Depends
  =
  * wpa   (for android-headers)

  WPA source package would need to first drop:
  - debian/patches/android_hal_fw_path_change.patch: add a DBus method
for requesting a firmware change when working with the Android HAL;
this is used to set a device in P2P or AP mode; conditional to
CONFIG_ANDROID_HAL being enabled.
  - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
  - debian/control: Build-Depends on android-headers to get the required
wifi headers for the HAL support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

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

[Desktop-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

Removing packages from disco:
android-src-vendor 7-0ubuntu1 in disco
android-src-vendor 7-0ubuntu1 in disco amd64
android-src-vendor 7-0ubuntu1 in disco arm64
android-src-vendor 7-0ubuntu1 in disco armhf
android-src-vendor 7-0ubuntu1 in disco i386
android-src-vendor 7-0ubuntu1 in disco ppc64el
android-src-vendor 7-0ubuntu1 in disco s390x
Comment: Ubuntu-specific, no uploads since 2014, unmaintained; LP: #1734568
1 package successfully removed.


** Changed in: android-src-vendor (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove obsolete Android packages from Ubuntu

Status in android-audiosystem package in Ubuntu:
  Fix Released
Status in android-headers package in Ubuntu:
  New
Status in android-src-vendor package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  Ubuntu has a few Android-related packages that were never in Debian
  and are no longer maintained by anyone. Please remove them from Ubuntu
  disco.

  $ reverse-depends src:android-src-vendor 
  No reverse dependencies found
  $ reverse-depends -b src:android-src-vendor 
  No reverse dependencies found

  $ reverse-depends src:android-audiosystem
  No reverse dependencies found
  $ reverse-depends -b src:android-audiosystem
  No reverse dependencies found

  $ reverse-depends src:android-headers
  No reverse dependencies found
  $ reverse-depends -b src:android-headers
  Reverse-Build-Depends
  =
  * wpa   (for android-headers)

  WPA source package would need to first drop:
  - debian/patches/android_hal_fw_path_change.patch: add a DBus method
for requesting a firmware change when working with the Android HAL;
this is used to set a device in P2P or AP mode; conditional to
CONFIG_ANDROID_HAL being enabled.
  - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
  - debian/control: Build-Depends on android-headers to get the required
wifi headers for the HAL support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

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

[Desktop-packages] [Bug 1754914] Re: Please remove gnome-themes-standard source, superseded by gnome-themes-extra

Removed 2018-10-09 via Debian:

(From Debian) RoQA; source package renamed to gnome-themes-extra; Debian
bug #892100


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

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

Title:
  Please remove gnome-themes-standard source, superseded by gnome-
  themes-extra

Status in gnome-themes-standard package in Ubuntu:
  Fix Released

Bug description:
  gnome-themes-standard has been renamed to gnome-themes-extra.

  Please remove the obsolete source package and the gnome-themes-
  standard-data binary.

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

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

[Desktop-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

wpa still has a build-dependency on android-headers.

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

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

Title:
  Please remove obsolete Android packages from Ubuntu

Status in android-audiosystem package in Ubuntu:
  Fix Released
Status in android-headers package in Ubuntu:
  New
Status in android-src-vendor package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  Ubuntu has a few Android-related packages that were never in Debian
  and are no longer maintained by anyone. Please remove them from Ubuntu
  disco.

  $ reverse-depends src:android-src-vendor 
  No reverse dependencies found
  $ reverse-depends -b src:android-src-vendor 
  No reverse dependencies found

  $ reverse-depends src:android-audiosystem
  No reverse dependencies found
  $ reverse-depends -b src:android-audiosystem
  No reverse dependencies found

  $ reverse-depends src:android-headers
  No reverse dependencies found
  $ reverse-depends -b src:android-headers
  Reverse-Build-Depends
  =
  * wpa   (for android-headers)

  WPA source package would need to first drop:
  - debian/patches/android_hal_fw_path_change.patch: add a DBus method
for requesting a firmware change when working with the Android HAL;
this is used to set a device in P2P or AP mode; conditional to
CONFIG_ANDROID_HAL being enabled.
  - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
  - debian/control: Build-Depends on android-headers to get the required
wifi headers for the HAL support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

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

[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

In the time it took to try to port from aptdaemon to packagekit,
packagekit has gone dead upstream, and we have been recommended not to
port further work to it.

Julian is now looking at providing an aptd as part of apt upstream that
is fit for purpose.

I am unsubscribing ubuntu-archive from this bug.

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

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

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

[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

** Project changed: totem => gstreamer

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

Status in GStreamer:
  Unknown
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91

  ---

  Backtrace goes through:

  totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
  gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
  libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)

  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.

  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---

  I.e. bug is in what is given to Mesa, not what Mesa does.

  -> NOTOURBUG

  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  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/gstreamer/+bug/1758287/+subscriptions

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Treviño

Both budgie and gnome-shell are in proposed now and this is verified for
mutter and both shell.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1825224] Re: gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer

** Description changed:

  Upon attempting to add a calendar from outlook.com, I was greeted with a
  username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have two-
  factor authentication. The dialog box would go away, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug which I will link
- here as soon as I get it filed.
+ Unfortunately, at that point, I discovered another bug (#185227).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Upon attempting to add a calendar from outlook.com, I was greeted with a
  username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have two-
  factor authentication. The dialog box would go away, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug (#185227).
+ Unfortunately, at that point, I discovered bug #185227.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-calendar cannot add credentialed web ics calendars

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Upon attempting to add a calendar from outlook.com, I was greeted with
  a username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have
  two-factor authentication. The dialog box would go away, but the
  calendar would not be added.

  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
  Unfortunately, at that point, I discovered bug #185227.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825227] [NEW] gnome-calendar overcompensates time zone difference in web ics calendar

2019-04-17 Thread Erich Eickmeyer

Public bug reported:

Upon adding a web ics calendar (via Evolution due to Bug #1825224), the
events from this calendar were not properly time-compensated for my time
zone. While Evolution and Gnome Shell displayed the time of my events
properly, gnome-calendar displayed the events 7 hours in the past,
likely attempting to compensate for my time zone (GMT -7).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 11:47:17 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Upon adding a web ics calendar (via Evolution due to Bug #1825224),
  the events from this calendar were not properly time-compensated for
  my time zone. While Evolution and Gnome Shell displayed the time of my
  events properly, gnome-calendar displayed the events 7 hours in the
  past, likely attempting to compensate for my time zone (GMT -7).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:47:17 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825224] [NEW] gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer

Public bug reported:

Upon attempting to add a calendar from outlook.com, I was greeted with a
username/password dialog box. So, I entered my username (an email
address in this case) and an app password I generated since I have two-
factor authentication. The dialog box would go away, but the calendar
would not be added.

The only workaround was to add the calendar using Evolution, which
properly accepted the username/app-password and added the calendar.
Unfortunately, at that point, I discovered bug #185227.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 11:39:29 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  gnome-calendar cannot add credentialed web ics calendars

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Upon attempting to add a calendar from outlook.com, I was greeted with
  a username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have
  two-factor authentication. The dialog box would go away, but the
  calendar would not be added.

  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
  Unfortunately, at that point, I discovered bug #185227.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-04-17 Thread Pavarin Bhandtivej

Verified on bionic that the proposed update (mutter version
3.28.3+git20190124-0ubuntu18.04.2) fixes the issue.

Thank you everyone who has worked on the issue. Your hard work is much
appreciated.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-04-17 Thread Treviño

This has been fixed by

mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)  Wed, 03 Apr 2019 19:19:59 -0400


I expect this is fixed by 
https://gitlab.gnome.org/GNOME/mutter/merge_requests/336 (issue 
https://gitlab.gnome.org/GNOME/mutter/issues/407)

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #407
   https://gitlab.gnome.org/GNOME/mutter/issues/407

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

Title:
  scaling changes when closing/re-opening the lid

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1825209] Re: Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga

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

** This bug has been marked a duplicate of bug 1825208
   Automatic suspend delay is at least 15 mins

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

Title:
  Automatic suspend delay is at least 15 mins

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

Bug description:
  Settings -> Power -> Automatic suspend -> On battery power -> Delay
  has a minimum value of 15 mins. This might made sense to the developer
  who thought that you never want a lower value because you have a
  laptop with multiple hours of battery life, but the same setting is
  used for desktop computers than run on UPSs. In case of a power
  outage, desktop users might reasonably want a lower delay before
  suspending the computer (1 or 5 minutes, etc.) so I believe that this
  is a UX design issue.

  If you agree with this I might be able to patch it.

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

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

[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** No longer affects: gstreamer

** Also affects: totem via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already

[Desktop-packages] [Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta

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

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

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

Title:
  Can't drag and drop files to Desktop on Disco 19.04 beta

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  Summary: Can't drag and drop files to Desktop on Disco 19.04 beta

  Steps to reproduce:
  1. Click "Files" on luncher
  2. Select some files
  3. Drag and drop the files to desktop (Disco Dingo wallpaper)

  Expected result:
  Drag and drop the files to desktop successfully

  Actual result:
  Can't drap and drop files to desktop

  Addtional information:
  Drag and drog the files in "Files" to "Desktop" folder were succesful and the 
files show on desktop (Disco Dingo wallpapaer)

  Failure rate: 100%

  -

  CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x)
  system-product-name: Precision 5530
  bios-version: 1.6.0
  system-manufacturer: Dell Inc.
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b

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

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

[Desktop-packages] [Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

2019-04-17 Thread Christopher Nelson

Yes, they are very similar.

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I have two displays, one on display port, and one on VGA. The display
  port display is a Seiki Pro 40" display in landscape at 3840x2160. The
  VGA is an HP 24" display in portrait at 1920x1200.

  If I boot with either display by itself, everything works fine. If I
  plug in the other display and configure it to run multidisplay,
  everything is fine.

  When I reboot, the display settings are changed from "Join Displays"
  to "Mirror", the 40" is set to 1920x1200 landscape (which it cannot
  actually do), and the 24" is set to 1920x1200 landscape. The 24" is
  also set to primary (whereas I selected the 40" as primary before
  rebooting.)

  The 40" display is messed up with overdraw, etc. In addition, I can no
  longer select 3840x2160 for the 40". If I turn of the 40" and turn it
  on again, eventually the settings box will let me select 3840x2160.
  Once I select it, the screen flashes but does not come back to
  3840x2160. (ie., it is still corrupted with overdraw and presumably
  running at 1920x1200.). If I toggle the display power several times,
  it will eventually come back running at the correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 10:58:08 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

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

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

[Desktop-packages] [Bug 1812903] Re: Please remove libproxy1-plugin-mozjs/s390x on disco

This is done.

 libproxy1-plugin-mozjs  | 0.4.15-5 | disco/universe | amd64,
arm64, armhf, i386, ppc64el


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

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

Title:
  Please remove libproxy1-plugin-mozjs/s390x on disco

Status in libproxy package in Ubuntu:
  Fix Released

Bug description:
  Please remove the NBS libproxy1-plugiin-mozjs from s390x.

  It does not show up on
  https://people.canonical.com/~ubuntu-archive/nbs.html

  But it does show at
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

  The binary package is intentionally not built on s390x because mozjs60
  is not available on s390x currently.

  $ rmadison libproxy1-plugin-mozjs
   libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
   libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

  $ rmadison libproxy
   libproxy | 0.4.15-2 | cosmic   | source
   libproxy | 0.4.15-5 | disco| source

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

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

[Desktop-packages] [Bug 1825208] [NEW] Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga

Public bug reported:

Settings -> Power -> Automatic suspend -> On battery power -> Delay has
a minimum value of 15 mins. This might made sense to the developer who
thought that you never want a lower value because you have a laptop with
multiple hours of battery life, but the same setting is used for desktop
computers than run on UPSs. In case of a power outage, desktop users
might reasonably want a lower delay before suspending the computer (1 or
5 minutes, etc.) so I believe that this is a UX design issue.

If you agree with this I might be able to patch it.

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

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

Title:
  Automatic suspend delay is at least 15 mins

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

Bug description:
  Settings -> Power -> Automatic suspend -> On battery power -> Delay
  has a minimum value of 15 mins. This might made sense to the developer
  who thought that you never want a lower value because you have a
  laptop with multiple hours of battery life, but the same setting is
  used for desktop computers than run on UPSs. In case of a power
  outage, desktop users might reasonably want a lower delay before
  suspending the computer (1 or 5 minutes, etc.) so I believe that this
  is a UX design issue.

  If you agree with this I might be able to patch it.

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

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

[Desktop-packages] [Bug 1825209] [NEW] Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga

Public bug reported:

Settings -> Power -> Automatic suspend -> On battery power -> Delay has
a minimum value of 15 mins. This might made sense to the developer who
thought that you never want a lower value because you have a laptop with
multiple hours of battery life, but the same setting is used for desktop
computers than run on UPSs. In case of a power outage, desktop users
might reasonably want a lower delay before suspending the computer (1 or
5 minutes, etc.) so I believe that this is a UX design issue.

If you agree with this I might be able to patch it.

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

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

Title:
  Automatic suspend delay is at least 15 mins

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

Bug description:
  Settings -> Power -> Automatic suspend -> On battery power -> Delay
  has a minimum value of 15 mins. This might made sense to the developer
  who thought that you never want a lower value because you have a
  laptop with multiple hours of battery life, but the same setting is
  used for desktop computers than run on UPSs. In case of a power
  outage, desktop users might reasonably want a lower delay before
  suspending the computer (1 or 5 minutes, etc.) so I believe that this
  is a UX design issue.

  If you agree with this I might be able to patch it.

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

Hello Pavarin, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt

Hello Gert, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  Gnome shell crashes on double free

  Problem is occurring if dual monitor is used. Second monitor is
  repeatingly blank and activated again. At the bottom it probably
  contains the upper part of the first monitor. I had the same problem
  at 18.04 when using gdm3 without wayland during logon.

  [ Test case ]

  - Run gnome-shell with multimonitor
  - No flashing should happen on gdm initialization

  Also we should monitor crashes in e.u.c

  [ Regression potential ]

  Low, the proposed fix is part of the current stable branch upstream
  and not changed in further revisions.

  --

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic i686
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: i386
  AssertionMessage: double free or corruption (fasttop)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 21:02:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_signal_restore_set (set=0xbfcd5e9c) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
   __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
   __GI_abort () at abort.c:79
   __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption 
(fasttop)") at malloc.c:5350
  Title: gnome-shell assert failure: double free or corruption (fasttop)
  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/mutter/+bug/1790525/+subscriptions

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

Hello Yogish, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [ Fix ]

  See below for the changes from upstream that fix this, which we're
  uploading to disco-proposed now.

  [ QA ]

  Under the GNOME Micro Release Exception, you can believe this is
  fixed.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It might be a good idea to test an nvidia machine, but it doesn't need
  explicit verification.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

  https://bugzilla.gnome.org/show_bug.cgi?id=790316

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom

Hello Daniel, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  Shell text and some icons have sharp edges during zoom

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  Shell text and some icons have sharp edges during zoom. Screenshot attached.
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/387

  [Test Case]

  1. Settings > Universal Access > Zoom = ON
  2. Click on the time/calendar and look closely at the font edges.
  Expect: the edges should be smooth when zoomed.

  [Regression Potential]

  Low potential effect on other parts of Gnome Shell. The code being
  changed is only used in shell popup menus at the moment.

  [Other Info]

  This is not an important bug at all. Its fix is just a happy
  consequence of fixing the more important bug 1767648, so that's why it
  is getting SRU'd - for bug 1767648.

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

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

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

Hello Marco, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

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

Title:
  SRU 3.28 latest git to bionic

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text

Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  gnome-shell crashed with SIGSEGV in
  cogl_texture_get_height(texture=0x0) from
  clutter_offscreen_effect_real_paint_target() from
  clutter_offscreen_effect_paint_texture() from
  clutter_offscreen_effect_paint() from clutter_actor_continue_paint()

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  Gnome shell crashes on cogl_texture_get_height

  [ Test case ]

  No clear reproducer is know for such issue, crashes should be
  monitored in e.u.c checking that this is not happening anymore for the
  version in proposed.

  [ Regression potential ]

  Low, the proposed fix is part of the current stable branch upstream
  and not changed in further revisions.

  --

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

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

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

[Desktop-packages] [Bug 919156] Re: Kubuntu 11.10 does not automatically download HPLIP plugin

2019-04-17 Thread Ammar Sayed Abdel Aziz

I am reporting the same issue here

I have followed the instruction on the below video and it just worked
very fine

https://www.youtube.com/watch?v=G0r1awenSug&t=167s

similar solution was provided in the below forum as well

https://www.kubuntuforums.net/showthread.php/56776-SOLVED-HP-
Laserjet-P1005-not-printing

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

Title:
  Kubuntu 11.10 does not automatically download HPLIP plugin

Status in hplip package in Ubuntu:
  Expired

Bug description:
  The user has to run hp-plugin manually.

  Originally reported here:

  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/comments/39

  And answered here:

  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/comments/43

  and here:

  https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/913730/comments/6

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

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

[Desktop-packages] [Bug 1825197] [NEW] system unresponse for several seconds a couple of times per hour

Public bug reported:

My system is up-to-date on:

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.30.2-0ubuntu1.18.10.1
  Candidate: 3.30.2-0ubuntu1.18.10.1

To provide you with an idea of the motivation for the origin in gnome-
shell; I've included the lines in syslog that are displayed for many
more occasions than presented below.

At the times that these messages are displayed in my logs I can still
move my mouse, but mouse clicks are unresponsive and typing is frozen
(but text does appear after freeze).


Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the swee

[Desktop-packages] [Bug 1824998] Re: Zanata is messing up the translations

2019-04-17 Thread Rodrigo Lledó

Yes, the string is upstream.
Yes, upstream was importing errors from Red Hat translators. I think is related 
with the Copy Trans feaure of Zanata.
I reported this issue upstream a few minutes after reporting in Launchpad and 
here is his reply:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/160

I also contacted one of the developers of Zanata: Sachin Pathare.

https://github.com/orgs/zanata/people

Summary:

"NetworkManager upstream does not use Zanata.
We had a project at zanata.org [1], but that had severe issues, so we are back 
to po-files and git."

"Red Hat uses Zanata internally, but afterwards they get manualy import the 
plain "po" file in git. Whatever Red Hat translators do, what matters is only 
what we import.
The only upstream location for translations is git (and that's also the place 
to contribute translations)."

** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues 
#160
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/160

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

Title:
  Zanata is messing up the translations

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi

  Today is actually impossible to keep NM translations in good shape
  since Zanata (a tool used in Fedora and Red Hat) is messing up the
  translations.

  Example:

  https://translations.launchpad.net/ubuntu/disco/+source/network-
  manager/+pots/networkmanager/es/870/+translate

  Which literally means:
  One of the functions of the swimming boat (3) is a function of the boat's 
control unit.

  Or translating "master" as "dominate"

  This is hilarous but also frustrating.

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

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

[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

** No longer affects: mesa

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

Status in GStreamer:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91

  ---

  Backtrace goes through:

  totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
  gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
  libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)

  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.

  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---

  I.e. bug is in what is given to Mesa, not what Mesa does.

  -> NOTOURBUG

  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  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/gstreamer/+bug/1758287/+subscriptions

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

[Desktop-packages] [Bug 1825188] [NEW] Just upgraded to ubunt 18 and now ulimit -n changes hard and soft limits

2019-04-17 Thread Donald Jones

Public bug reported:

I recently upgraded from Ubuntu 14 to 18 and now I can't use ulimit -n
to increase the allowed number of files open! This is a change from my
previous version of Ubuntu.

Lines from /etc/security/limits.conf
jonesdc  hardnofile  10
jonesdc  softnofile  1

Setting in /etc/sysctl.conf
# Max open files (system limit)
fs.file-max = 10

When I first open a terminal if I type 
$ulimit -n 1000
then
$ulimit -a 
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) 1
pending signals (-i) 30927
max locked memory   (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files  (-n) 1000
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30927
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Now if I type
$ulimit -n 999
and then try again
$ulimit -n 1000
bash: ulimit: open files: cannot modify limit: Operation not permitted

Looking further, it appears that ulimit -n changes both the hard and soft limits
$ulimit -H -a
core file size  (blocks, -c) unlimited
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 30927
max locked memory   (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files  (-n) 999
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) unlimited
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30927
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

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

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

Title:
  Just upgraded to ubunt 18 and now ulimit -n changes hard and soft
  limits

Status in lightdm package in Ubuntu:
  New

Bug description:
  I recently upgraded from Ubuntu 14 to 18 and now I can't use ulimit -n
  to increase the allowed number of files open! This is a change from my
  previous version of Ubuntu.

  Lines from /etc/security/limits.conf
  jonesdc  hardnofile  10
  jonesdc  softnofile  1

  Setting in /etc/sysctl.conf
  # Max open files (system limit)
  fs.file-max = 10

  When I first open a terminal if I type 
  $ulimit -n 1000
  then
  $ulimit -a 
  core file size  (blocks, -c) 0
  data seg size   (kbytes, -d) unlimited
  scheduling priority (-e) 0
  file size   (blocks, -f) 1
  pending signals (-i) 30927
  max locked memory   (kbytes, -l) 16384
  max memory size (kbytes, -m) unlimited
  open files  (-n) 1000
  pipe size(512 bytes, -p) 8
  POSIX message queues (bytes, -q) 819200
  real-time priority  (-r) 0
  stack size  (kbytes, -s) 8192
  cpu time   (seconds, -t) unlimited
  max user processes  (-u) 30927
  virtual memory  (kbytes, -v) unlimited
  file locks  (-x) unlimited

  Now if I type
  $ulimit -n 999
  and then try again
  $ulimit -n 1000
  bash: ulimit: open files: cannot modify limit: Operation not permitted

  Looking further, it appears that ulimit -n changes both the hard and soft 
limits
  $ulimit -H -a
  core file size  (blocks, -c) unlimited
  data seg size   (kbytes, -d) unlimited
  scheduling priority (-e) 0
  file size   (blocks, -f) unlimited
  pending signals (-i) 30927
  max locked memory   (kbytes, -l) 16384
  max memory size (kbytes, -m) unlimited
  open files  (-n) 999
  pipe size(512 bytes, -p) 8
  POSIX message queues (bytes, -q) 819200
  real-time priority  (-r) 0
  stack size  (kbytes, -s) unlimited
  cpu time   (seconds, -t) unlimited
  max user processes  (-u) 30927
  virtual memory  (kbytes, -v) unlimited
  file locks  (-x) unlimited

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

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

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

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

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

Title:
  LIbreoffice crashes on startup

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:


  $ libreoffice --norestore
  Application Error

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 16 12:58:04 2018
  InstallationDate: Installed on 2014-04-07 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago)

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

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

[Desktop-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

I changed the name of the gmail account to USER.

** Attachment added: "$ gio mount -li"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825167/+attachment/5256545/+files/gio_mount_-liV2.txt

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

** Changed in: gstreamer
   Status: Unknown => New

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

Status in GStreamer:
  New
Status in Mesa:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91

  ---

  Backtrace goes through:

  totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
  gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
  libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)

  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.

  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---

  I.e. bug is in what is given to Mesa, not what Mesa does.

  -> NOTOURBUG

  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  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/gstreamer/+bug/1758287/+subscriptions

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

[Desktop-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

** Changed in: nautilus
   Status: Unknown => New

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1825006] Re: snapp apps not showing in software center

2019-04-17 Thread Larika

I think that "Strumenti di sviluppo" is "Development tools" in english.

https://snag.gy/6PA0yX.jpg

But, snap apps are not showing in any of the gnome-software lists,
neither in the main one.

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

Title:
  snapp apps not showing in software center

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Not installed snap apps are not listed in software center. 
  They appear only if you manually search them.

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

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

[Desktop-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

2019-04-17 Thread Sebastien Bacher

Thank you for your bug report, could you provide the output of "$ gio
mount -li" ?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

https://gitlab.gnome.org/GNOME/nautilus/issues/991

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1825167] [NEW] It does not correctly display the hard drive icon