[Desktop-packages] [Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell

2019-02-26 Thread SamuelB.
I'm fine with 1817546 ;)

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

Title:
  Changing the volume (with the mouse wheel over icon) locks up gnome-
  shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Confirmed

Bug description:
  If I change the volume, the display freezes right after the volume
  display floating indictor appears in the middle of the screen. I have
  to either reboot or switch to virtual terminal and killall -3 gnome-
  shell to restart the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 13:20:49 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-19 (615 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+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 640439] Re: An error occurred during a connection to localhost:8443. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_lo

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  An error occurred during a connection to localhost:8443.  SSL received
  a record that exceeded the maximum permissible length.  (Error code:
  ssl_error_rx_record_too_long)

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  An error occurred during a connection to localhost:8443.

  SSL received a record that exceeded the maximum permissible length.

  (Error code: ssl_error_rx_record_too_long)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.9+build1+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Thu Sep 16 14:38:22 2010
  FirefoxPackages:
   firefox 3.6.9+build1+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.9+build1+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.9+build1+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/640439/+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 892764] Re: al cerrar terminal se pierde mi configuración en openbox (when closing terminal my configuration is lost in openbox)

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  al cerrar terminal se pierde mi configuración en openbox (when closing
  terminal my configuration is lost in openbox)

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Uso Ubuntu 11.10, deseo usarlo con openbox, abro la terminal y lo
  configuro pero cada vez que la cierro se peride todo lo configurado.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Nov 20 12:20:41 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-10-21 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/892764/+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 730394] Re: Text copied from Empathy can't be pasted in Gnome Terminal

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Text copied from Empathy can't be pasted in Gnome Terminal

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-terminal

  After copying text from the chat history in an open Empathy
  conversation I am unable to paste the results into gnome-terminal.

  Pasting seems to work fine in most other applications. Thus a
  workaround is to paste the text into a plain-text field (something
  like gedit) and then paste from there.

  It seems to be something with the way these two applications interact.
  I'm wondering if rich-text contents are not being handled properly by
  gnome-terminal or if empathy is not correctly setting the plain-text
  version of the clipboard.

  Using klipper I get a odd result if trying to "edit" the clipboard:
  the edit box is empty despite the klipper menu showing the cut text.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-terminal 2.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Mar  7 13:14:20 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/730394/+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 794560] Re: Gnome-terminal: sometimes un-focused term continues to blink its cursor.

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Gnome-terminal: sometimes un-focused term continues to blink its
  cursor.

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-terminal

  I move my mouse to cause focus to move to another window and the old
  cursor continues to blink (so that I have two or more windows with
  blinking cursors).  This is somewhat confusing because if I do
  something on my other computer and come back, I occasionally start
  typing in the wrong window.  If this is not a Unity bug, I apologize.
  But it started happening when I upgraded to Natty (11.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-terminal 2.32.1-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Jun  8 09:05:12 2011
  ExecutablePath: /usr/bin/gnome-terminal
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to natty on 2011-05-03 (35 days ago)
  XsessionErrors:
   (quicksynergy:2217): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: 
assertion `GTK_IS_WIDGET (widget)' failed
   (quicksynergy:2217): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: 
assertion `GTK_IS_WIDGET (widget)' failed
   (quicksynergy:2217): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: 
assertion `GTK_IS_WIDGET (widget)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/794560/+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 873662] Re: gnome-terminal icon doesn't appear at Unity sidebar when launched

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gnome-terminal icon doesn't appear at Unity sidebar when launched

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  When I open a terminal window it didn't appear at Unity sidebar and
  when it is minimized I can't get it again. Alt+Tab can't see any open
  gnome-terminal window too.

  Update: this issue occurs only on the Oneiric first run after fresh
  installation. Tested in multiple machines.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 13 17:10:34 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/873662/+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 951725] Re: Black Background

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Black Background

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Using FF 11, when I logoff and then log back on again, the FF
  background is black.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 11.0~b7+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phil   1822 F pulseaudio
  BuildID: 20120309112843
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Channel: beta
  CurrentDmesg: [ 1017.764387] soffice.bin[2826]: segfault at 629ce78 ip 
0398e0ab sp bfb9e910 error 4 in libQtCore.so.4.8.0[3812000+2d4000]
  Date: Sat Mar 10 11:41:05 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Test Pilot - ID=testpi...@labs.mozilla.com, 
Version=1.2, minVersion=3.5, maxVersion=10.0a1, Location=app-profile, 
Type=extension, Active=Yes
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.109  metric 
1
  Plugins:
   Shockwave Flash - Lib=libflashplayer.so, 
Location=/usr/lib/flashplugin-installer
   Skype Buttons for Kopete - Lib=skypebuttons.so, 
Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0/20120309112843 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-03-10 (0 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HH807
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0HH807:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/951725/+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 581904] Re: external drive / multiple partitions no right click unmount

2019-02-26 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  external drive / multiple partitions  no right click unmount

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Hey guys,

  Ubuntu Lucid 10.04
  External drive with multiple partitions...drive icons on Desktop... highlight 
all drive icons...right click...no unmount option or safely remove drive 
options..
   Highlight single partition icon right click has safely remove drive 
option, however when executing this  it gives error pop up ;

  Error detaching: helper exited with exit code 1: Detaching device /dev/sdc
  USB device: /sys/devices/pci:00/:00:1d.7/usb1/1-6)
  SYNCHRONIZE CACHE: FAILED: No such file or directory
  (Continuing despite SYNCHRONIZE CACHE failure.)
  STOP UNIT: FAILED: No such file or directory

  any way to fix this?

  coz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/581904/+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 1001444] Re: firefox don't start for the non-admin user

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  firefox don't start for the non-admin user

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I would like to report 2 notes:
  1. Firefox tries to restart a crashed session;
  2. my daughter had installed a toolbar.
  When I kill the process using Terminal the next time Firefox doesn't show 
even the window.
  Items menu are disappeared (no commands are there, i.e.: no commands are 
present under "File" menu)
  Tnx

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 12.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 
82801CA-ICH3]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lorenzo2576 F pulseaudio
  BuildID: 20120423122624
  Card0.Amixer.info:
   Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with AD1886A at irq 11'
 Mixer name : 'Analog Devices AD1886A'
 Components : 'AC97a:41445363'
 Controls  : 38
 Simple ctrls  : 24
  Channel: release
  Date: Fri May 18 22:50:11 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.10  metric 
2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423122624 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-05-15 (3 days ago)
  dmi.bios.date: 05/24/2003
  dmi.bios.vendor: Compaq
  dmi.bios.version: 68P4F v2.49 F.14
  dmi.board.name: 07F4
  dmi.board.vendor: Compaq
  dmi.board.version: KBC Version   .
  dmi.chassis.asset.tag: CNU3440NH5
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compaq
  dmi.modalias: 
dmi:bvnCompaq:bvr68P4Fv2.49F.14:bd05/24/2003:svnCompaq:pnEvoEvoN610c:pvr:rvnCompaq:rn07F4:rvrKBCVersion.:cvnCompaq:ct10:cvr:
  dmi.product.name: Evo Evo N610c
  dmi.sys.vendor: Compaq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1001444/+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 914740] Re: Not able to view Telugu Unicode letters clearly in Terminal

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Not able to view Telugu Unicode letters clearly in Terminal

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  1. I have created a directory having name in Telugu letters as 'వసంతం'
  2. That directory name is clearly view-able in any window except the Terminal

  Please find the attached screen shots

  b) Telugu letters from window - In the window dir names are clear.

  Please provide the fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan 11 17:56:07 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/914740/+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 922867] Re: Daemon is inhibited cannt unmount partition

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Daemon is inhibited cannt unmount partition

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  trying to install ubunyu permantly to hard drive

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Fri Jan 27 16:00:30 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Zorin OS 5.2 32bit - Release i386
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to natty on 2012-01-24 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/922867/+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 1503132] Re: Terminal lists non existing files

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Terminal lists non existing files

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  I have only one folder on my desktop. When I used "cd Desktop" and
  "ls" commands, in stead of one folder, it listed so many non existent
  files

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Tue Oct  6 10:49:16 2015
  DistUpgraded: 2015-09-16 19:17:17,482 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4330/4350/4550] [1002:9552] (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:02be]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Studio 1555
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=B868B3C768B38324 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2015-09-16 (19 days ago)
  dmi.bios.date: 11/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0C234M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd11/07/2009:svnDellInc.:pnStudio1555:pvrA08:rvnDellInc.:rn0C234M:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Studio 1555
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.7
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.7
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.17
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1503132/+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 1212431] Re: gnome-terminal is installed but not shown in unity

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gnome-terminal is installed but not shown in unity

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Fresh daily iso (2013-08-14) install on real hardware. And updated to
  latest updates

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Wed Aug 14 23:48:53 2013
  InstallationDate: Installed on 2013-08-14 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130814)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1212431/+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 1018953] Re: unable to drag url to bookmarks folder in firefox

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unable to drag url to  bookmarks folder in firefox

Status in firefox package in Ubuntu:
  Expired

Bug description:
  In kubuntu 12.04 and firefox 13.0.1, whenever dragging a url from the
  address bar to a folder in the bookmark menu, the menu will disappear
  as you mouse over contents in the folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1018953/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2019-02-26 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1221870] Re: Password error on some sites, was spotted and the 32 bit version.

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Password error on some sites, was spotted and the 32 bit version.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Keyboard input method uses a "th-gtk", the password was checked and is
  entered correctly, but on the sites error occurred wrong password.
  Solves the problem of switching with the mouse pointer into Russian
  and then back into English.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 23.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
  Uname: Linux 3.5.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a3 1489 F pulseaudio
  BuildID: 20130803215302
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 20'
 Mixer name : 'Analog Devices AD1988B'
 Components : 'HDA:11d4198b,104381f6,00100400'
 Controls  : 50
 Simple ctrls  : 27
  Channel: Unavailable
  Date: Fri Sep  6 22:01:48 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.42.0.0/24 dev eth0  proto kernel  scope link  src 10.42.0.1  metric 1 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 10.45.42.10 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   ppp0  no wireless extensions.
   
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  MostRecentCrashID: bp-9bb32e1e-0ebc-4fc2-9068-62ea82130803
  PciNetwork:
   
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=23.0/20130803215302 (In use)
  RelatedPackageVersions:
   icedtea-6-plugin  1.2.3-0ubuntu0.12.04.3
   rhythmbox-mozilla 2.96-0ubuntu4.3
   totem-mozilla 3.0.1-0ubuntu21.1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-9bb32e1e-0ebc-4fc2-9068-62ea82130803
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1804
  dmi.board.name: M2N-SLI DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1804:bd09/16/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1221870/+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 1510927] Re: coub does'nt play, load bar line is half-filed every time

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  coub does'nt play, load bar line is half-filed every time

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When clicking play(screenshot_1.png) on Coub frame button nothing
  happens, but bottom load bar of the frame gets filled up to
  half(screenshot_2.png). Lubuntu Linux LXDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: firefox 41.0.2+build2-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   freelsd1361 F...m plugin-containe
   /dev/snd/controlC0:  freelsd1166 F lxpanel
freelsd1361 F plugin-containe
   /dev/snd/timer:  freelsd1361 f plugin-containe
  BuildID: 20151015172656
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Tue Oct 27 00:19:45 2015
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-03-23 (217 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.88.1 dev wlan0  proto static  metric 400 
   192.168.88.0/24 dev wlan0  proto kernel  scope link  metric 400
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=41.0.2/20151015172656 (In use)
  RelatedPackageVersions: gecko-mediaplayer 1.0.9-2ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (178 days ago)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd12/01/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1510927/+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 1012133] Re: browser choppy scrolling

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  browser choppy scrolling

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Since switching to the new Cinnamon Desktop in Ununtu 12.04 LTS, I
  noticed general scrolling is much more difficult in a browser. I
  recently got a bigger monitor so I switched to Cinnamon since that's
  the only way I could get the optimum resolution using dual monitors on
  my ATI HD 5400 series. Maybe it's just the fact that I have an ATI
  card, on a MSI motherboard.

  The resolution worked, but now the graphics are just choppy,
  especially when scrolling in a browser or watching any video. Looks
  great when it's not moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 13.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  innabawks   1600 F pulseaudio
   /dev/snd/controlC0:  innabawks   1600 F pulseaudio
   /dev/snd/pcmC0D0p:   innabawks   1600 F...m pulseaudio
  BuildID: 20120601173917
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe70 irq 41'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,14627680,0010'
 Controls  : 42
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfe64 irq 42'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: release
  Date: Tue Jun 12 08:26:27 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 192.168.1.1 dev wlan2  proto static 
   169.254.0.0/16 dev wlan2  scope link  metric 1000 
   192.168.1.0/24 dev wlan2  proto kernel  scope link  src 192.168.1.2  metric 2
  MostRecentCrashID: bp-2855b4ce-cee7-4438-ade8-90a40209
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0/20120601173917 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-2855b4ce-cee7-4438-ade8-90a40209
   bp-7be3be0d-3543-4b0d-939a-506a2208
   bp-3eb02b4d-6724-4fa7-9135-3ef6d208
  UpgradeStatus: Upgraded to precise on 2012-04-28 (44 days ago)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V17.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P23 (MS-7680)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV17.0:bd03/14/2011:svnMSI:pnMS-7680:pvr3.0:rvnMSI:rnH61M-P23(MS-7680):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.name: MS-7680
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1012133/+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 1250379] Re: Gnome terminal window is invisible

2019-02-26 Thread Launchpad Bug Tracker
[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Gnome terminal window is invisible

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  Terminal launches but window is invisible (only edges are visible).
  Login ubuntu in mode Gnome Flashback (no effects), terminal is visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Tue Nov 12 11:05:58 2013
  InstallationDate: Installed on 2013-03-25 (231 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-11-08 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1250379/+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 1021763] Re: No se reproducen los videos que tengos en skydrive

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No se reproducen los videos que tengos en skydrive

Status in firefox package in Ubuntu:
  Expired

Bug description:
  No puedo reproducir los videos que tengo en skydrive en firefox

  Google translation:
  I can not play the videos that I have on skydrive in firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 13.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: wl fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stalin 2473 F pulseaudio
  BuildID: 20120615112143
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xd440 irq 16'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c3613,00100400 
HDA:11c11040,103c1378,00100200'
     Controls  : 18
     Simple ctrls  : 11
  Channel: release
  Date: Fri Jul  6 16:46:01 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.1.1 dev eth2  proto static
   169.254.0.0/16 dev eth2  scope link  metric 1000
   192.168.1.0/24 dev eth2  proto kernel  scope link  src 192.168.1.189  metric 
2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615112143 (In use)
  RelatedPackageVersions:
   totem-mozilla 3.0.1-0ubuntu21
   gecko-mediaplayer 1.0.4-2ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPP Ver. F.0D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30E4
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.20
  dmi.chassis.asset.tag: CNU8504XTH
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPPVer.F.0D:bd08/03/2009:svnHewlett-Packard:pnHPCompaq6735s:pvrF.0D:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.20:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6735s
  dmi.product.version: F.0D
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1021763/+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 1540566] Re: excessive memory usage when opening https://elements.polymer-project.org/

2019-02-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  excessive memory usage when opening https://elements.polymer-
  project.org/

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When I open specifically https://elements.polymer-project.org/ and
  https://elements.polymer-project.org/guides/flex-layout, Firefox keeps
  on eating memory until system hangs. I have 8 GB RAM  firefox eats
  upto 60% RAM with no other tabs opened. (Firefox has crashed several
  times and I restored session only opening these pages).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: firefox 44.0+build3-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bipin  1600 F pulseaudio
   /dev/snd/pcmC0D0p:   bipin  1600 F...m pulseaudio
   /dev/snd/controlC0:  bipin  1600 F pulseaudio
  BuildID: 20160125133541
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Feb  2 01:41:25 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-12-24 (39 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.33  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=44.0/20160125133541 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   adobe-flashplugin 1:20151228.1-0ubuntu0.15.10.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6BCN44WW(V2.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y500
  dmi.modalias: 
dmi:bvnLENOVO:bvr6BCN44WW(V2.04):bd05/21/2013:svnLENOVO:pn20193:pvrLenovoIdeaPadY500:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY500:
  dmi.product.name: 20193
  dmi.product.version: Lenovo IdeaPad Y500
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1540566/+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 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-02-26 Thread Bryce
Will do.

On Tue, Feb 26, 2019, 9:00 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:

> Bryce,
>
> I am not talking about an "issue" at all. If you are experiencing
> problems then please log new bugs for them.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-02-26 Thread Daniel van Vugt
Bryce,

I am not talking about an "issue" at all. If you are experiencing
problems then please log new bugs for them.

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


Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-02-26 Thread Bryce
Might that be the same issue affecting the context menu (right click) when
using zoom? How does the drawing work for those menus?

On Tue, Feb 26, 2019, 8:35 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:

> And it only occurred to me today that zoom performance should (and does
> seem to) increase too. Because the combination of the two fixes:
>
>   https://gitlab.gnome.org/GNOME/mutter/commit/8655bc5d
>   https://gitlab.gnome.org/GNOME/gnome-shell/commit/f77b3da7
>
> means that panels/docks don't need to get regenerated every time you
> move the mouse while in zoom.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

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

[Desktop-packages] [Bug 1817793] Re: Audio is not switchable through Plasma widgets

2019-02-26 Thread Kai-Heng Feng
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Audio is not switchable through Plasma widgets

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my convertible, there seems to be no way to adept to changing audio 
drains; except of starting and re-configuring PulseAudio Volume Control. 
  I have a tablet, with a detachable keyboard and an external monitor with 
audio. What the normal volume control offers is irrelevant at switching those. 
Changing audio sources is not detected, and none of the usual controls allows 
for manual adaptations except PulseAudio Volume Control. 

  I have attached 4 screenshots: 
   - The standard volume control. It is possible to control all three drains 
(Devices), but it doesn't help when you disconnect. 
   - The PulseAudio Volume Control Configuration. Also that doesn't help.
   - The PulseAudio Volume Control Playback is the only place to select to 
where the audio goes. Alas, if one or even more disappear, here it is getting 
stuck there. Leaving the user without sound.
   - The somewhat most obvious place then is the standard volume control 
(Applications). However, this works differently from the almost identical one 
in PulseAudio Volume Control, in that it doesn't allow switching drains. 
Instead, one can increase the volume above 100%

  I do agree this bug is rather a RFE, though one that is obvious: The system 
does 'know' when a drain disappears, but it is not 'intelligent' enough to 
follow the still available ones. It would be natural, to allow the user to 
define preferences to which one it changes.
  As long as this doesn't exist, it is even more obvious to allow for that 
switching through the standard volume control.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel1822 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1822 F...m pulseaudio
   /dev/snd/controlC0:  udippel1822 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (10 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817793/+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-02-26 Thread Daniel van Vugt
And it only occurred to me today that zoom performance should (and does
seem to) increase too. Because the combination of the two fixes:

  https://gitlab.gnome.org/GNOME/mutter/commit/8655bc5d
  https://gitlab.gnome.org/GNOME/gnome-shell/commit/f77b3da7

means that panels/docks don't need to get regenerated every time you
move the mouse while in zoom.

-- 
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 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-02-26 Thread Daniel van Vugt
You're welcome. I'm glad this fix is finally seeing the light of day.

Also verified mutter version 3.28.3+git20190124-0ubuntu18.04.1 has fixed
this bug on bionic.

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

-- 
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 1779615] Re: Shell text and some icons have sharp edges during zoom

2019-02-26 Thread Daniel van Vugt
Verified mutter version 3.28.3+git20190124-0ubuntu18.04.1 has fixed this
bug on bionic.

** 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/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 1815708] Re: Use ODRS for reviews

2019-02-26 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Use ODRS for reviews

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  In Progress
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The Ubuntu review server is being retired which will cause all Ubuntu package 
reviews to stop working. We are switching to using the Open Desktop Review 
Service (https://odrs.gnome.org/). This plugin has existed for sometime in the 
GNOME Software source, so it is well tested. This change will allow Snap 
packages to be reviewed (new feature).

  [Test Case]
  1. Open GNOME Software
  2. Select a popular app (e.g. Firefox)

  [Expected Result]
  Reviews are shown for this package. They will be different to the previous 
reviews. You are able to create reviews for both .deb and snap apps.

  [Regression Potential]
  There is a risk of new bugs encountered in the ODRS plugin. This has been 
enabled in Disco without major issue and has been used in other distributions 
for many releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-02-26 Thread Daniel van Vugt
This sounds like it might be bug 1754693. But still, please follow the
steps above.

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04 (bionic) GNOME 3.28.2 .15.0-45-generic
  Since some updates in the last 2 weeks the interface started to freeze for 
15-20 seconds and then reloads (like a crash of the UI, then it got killed by 
the OS, and then restarted).

  The computer is unusable for 15-20 seconds then it works as nothing
  happened (I got proper sound and I believe everything is working - I
  just don't see it and I can not interact).

  I updated again and again (with the hope it's something terrible that
  affected a lot of users and is already fixed, but looks it's not).

  I started observing the problem more closely:
  The logs app that comes with Ubuntu shows this error (under System section) 
at similar times the interface crashes:

  gnome-shell[22505]: segfault at 28 ip 7f9a80434fe0 sp
  7ffd7fb8b058 error 4 in libmutter-2.so.0.0.0[7f9a803b1000+157000]

  gnome-shell[3366]: segfault at 28 ip 7ffa74598fe0 sp
  7ffc912713c8 error 4 in libmutter-2.so.0.0.0[7ffa74515000+157000]

  The problem appears in most cases when I'm on a video call using Slack or 
Zoom, so probably be related to that (not sure is it limited to that actually - 
may be it happened even when I was not on a call).
  I heavily use multiple desktops and switch between them very often (on a 
single TFT display).

  I'll be glad if anyone has an idea how to resolve this or report it
  (without reinstalling, which actually may be faster and easier).

  Thanks
  NK

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

2019-02-26 Thread Daniel van Vugt
Are you able to say what you were/are doing when the system hangs?

Also, does that include the mouse pointer? Or does the mouse pointer
still move?

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

** Summary changed:

- system hangs
+ [nouveau] system hangs

** Tags added: nouveau

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

Title:
  [nouveau] system hangs

Status in xorg-server package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb 26 12:19:26 2019
  DistUpgraded: 2016-11-14 14:16:19,712 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
  InstallationDate: Installed on 2016-11-12 (835 days ago)
  InstallationMedia: Edubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803.1)
  MachineType: LENOVO 20157
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic 
root=UUID=3006e45f-5f40-45c8-a376-3b9473cb4f8b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2016-11-14 (833 days ago)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN44WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake 2
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr62CN44WW:bd02/01/2013:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: 20157
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 26 09:04:52 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16978 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1817666/+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 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-02-26 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04 (bionic) GNOME 3.28.2 .15.0-45-generic
  Since some updates in the last 2 weeks the interface started to freeze for 
15-20 seconds and then reloads (like a crash of the UI, then it got killed by 
the OS, and then restarted).

  The computer is unusable for 15-20 seconds then it works as nothing
  happened (I got proper sound and I believe everything is working - I
  just don't see it and I can not interact).

  I updated again and again (with the hope it's something terrible that
  affected a lot of users and is already fixed, but looks it's not).

  I started observing the problem more closely:
  The logs app that comes with Ubuntu shows this error (under System section) 
at similar times the interface crashes:

  gnome-shell[22505]: segfault at 28 ip 7f9a80434fe0 sp
  7ffd7fb8b058 error 4 in libmutter-2.so.0.0.0[7f9a803b1000+157000]

  gnome-shell[3366]: segfault at 28 ip 7ffa74598fe0 sp
  7ffc912713c8 error 4 in libmutter-2.so.0.0.0[7ffa74515000+157000]

  The problem appears in most cases when I'm on a video call using Slack or 
Zoom, so probably be related to that (not sure is it limited to that actually - 
may be it happened even when I was not on a call).
  I heavily use multiple desktops and switch between them very often (on a 
single TFT display).

  I'll be glad if anyone has an idea how to resolve this or report it
  (without reinstalling, which actually may be faster and easier).

  Thanks
  NK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+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 1817646] Re: locking ubuntu doesn't work properly

2019-02-26 Thread Daniel van Vugt
This bug was fixed in updates a few weeks ago (bug 1769383).

What version of package 'gnome-shell-extension-ubuntu-dock' are you
using?

Also, please run this command to send us more information about the
system:

  apport-collect 1817646

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

Title:
  locking ubuntu doesn't work properly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When you lock ubuntu with keyboard or mouse with the right top menu,
  the sidebar stays still. The applications can be run from there. No
  input we can provide for these apps, but still we can use every
  feature the sidebar provides including starting "Compose new message"
  window.

  The attachment is the screenshot of related to the problem.
  PrintScreen button worked and took screenshot of screen, saved it when
  we are not logged in. Spotify example is one such example shows the
  problem. ( Screenshot from 2019-02-26 03-30-54.png, Screenshot from
  2019-02-26 03-38-58.png).

  Have a good day.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 26 03:43:04 2019
  InstallationDate: Installed on 2018-10-29 (119 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  SourcePackage: evince
  UpgradeStatus: Upgraded to bionic on 2018-10-29 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817646/+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 1817620] Re: High cpu usage on alt-tab-ing

2019-02-26 Thread Daniel van Vugt
Also, please run this command to send us more information about the
affected machine:

  apport-collect 1817620

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

** Changed in: mutter (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/1817620

Title:
  High cpu usage on alt-tab-ing

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

Bug description:
  Switching between apps was feeling extremely laggy and unsmooth after
  some days of keeping the laptop on and just alt-tab-ing between apps
  would keep the cpu consistently at 100% when hitting it more than 8-9
  times per second and *not* letting go of Alt (meaning I stay at the
  same app).

  Also, just whizzing the mouse around on the screen (not moving
  anything) would keep the cpu at 40-50%.

  Some investigation (1) led me to try out restarting the gnome-shell
  instance (killall followed by manually starting it in the terminal),
  upon which everything seemed zippy again. No lagginess. The restart
  was a supposed fix for a memory leak bug (2), but according to the
  comments a bug fix was supposed to have landed in 18.04 long ago. So
  either this has not been fixed or this bug is about something else -
  probably the latter, as the reported memory usage in htop was nowhere
  near the gigabytes of memory reported in the bug issue for 16722297.

  Another thing worth mentioning perhaps, based on comments in (3) found
  through (4), is that I have disabled all extensions. I used to use the
  Coverflow extension.

  Expected behaviour:
  There should be no percieved lag or stuttering in the interface when 
switching between applications.

  Actual behaviour:
  Switching between applications causes a noticable lag/stuttering when the 
computer has been running for an extended period of time (weeks, but where it 
has mostly been suspended, meaning actual usage is limited to 3-4 days).

  
  1. 
https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts
  2. https://bugs.launchpad.net/gnome-shell/+bug/1672297
  3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959
  4. https://askubuntu.com/a/1090987/165026

  System info:
  
  Running Wayland.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-shell:
Installert: 3.28.3-0ubuntu0.18.04.4
Kandidat:   3.28.3-0ubuntu0.18.04.4
Versjonstabell:
   *** 3.28.3-0ubuntu0.18.04.4 500
  500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+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 1817620] Re: High cpu usage on alt-tab-ing

2019-02-26 Thread Daniel van Vugt
Performance of window previews is significantly improved in mutter
3.28.4 (which doesn't exist yet :) due to:

https://gitlab.gnome.org/GNOME/mutter/commit/d81dcd13e4e14a8c80b7c9d475feb58c258babc0

But I think 18.04 will get that fix soon as part of the proposed update:

https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.1

Gnome 3.30 (Ubuntu 18.10) onward already contains that fix. So could you
please test one of:

 * Ubuntu 18.10
 * Ubuntu 19.04
 * Ubuntu 18.04 with proposed updates enabled

and tell us the version of the 'mutter' package you are testing.

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

Title:
  High cpu usage on alt-tab-ing

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

Bug description:
  Switching between apps was feeling extremely laggy and unsmooth after
  some days of keeping the laptop on and just alt-tab-ing between apps
  would keep the cpu consistently at 100% when hitting it more than 8-9
  times per second and *not* letting go of Alt (meaning I stay at the
  same app).

  Also, just whizzing the mouse around on the screen (not moving
  anything) would keep the cpu at 40-50%.

  Some investigation (1) led me to try out restarting the gnome-shell
  instance (killall followed by manually starting it in the terminal),
  upon which everything seemed zippy again. No lagginess. The restart
  was a supposed fix for a memory leak bug (2), but according to the
  comments a bug fix was supposed to have landed in 18.04 long ago. So
  either this has not been fixed or this bug is about something else -
  probably the latter, as the reported memory usage in htop was nowhere
  near the gigabytes of memory reported in the bug issue for 16722297.

  Another thing worth mentioning perhaps, based on comments in (3) found
  through (4), is that I have disabled all extensions. I used to use the
  Coverflow extension.

  Expected behaviour:
  There should be no percieved lag or stuttering in the interface when 
switching between applications.

  Actual behaviour:
  Switching between applications causes a noticable lag/stuttering when the 
computer has been running for an extended period of time (weeks, but where it 
has mostly been suspended, meaning actual usage is limited to 3-4 days).

  
  1. 
https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts
  2. https://bugs.launchpad.net/gnome-shell/+bug/1672297
  3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959
  4. https://askubuntu.com/a/1090987/165026

  System info:
  
  Running Wayland.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-shell:
Installert: 3.28.3-0ubuntu0.18.04.4
Kandidat:   3.28.3-0ubuntu0.18.04.4
Versjonstabell:
   *** 3.28.3-0ubuntu0.18.04.4 500
  500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+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 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell

2019-02-26 Thread Daniel van Vugt
I suggest using bug 1817335 instead, out of respect for the person who
reported it first.

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

Title:
  Changing the volume (with the mouse wheel over icon) locks up gnome-
  shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Disco:
  Confirmed

Bug description:
  If I change the volume, the display freezes right after the volume
  display floating indictor appears in the middle of the screen. I have
  to either reboot or switch to virtual terminal and killall -3 gnome-
  shell to restart the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 13:20:49 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-19 (615 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420

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

2019-02-26 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

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

Title:
  Video driver

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb 25 17:05:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1817617/+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 1817609] Re: Spinning mouse cursor is invisible when zoom is enabled

2019-02-26 Thread Daniel van Vugt
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1817609

Title:
  Spinning mouse cursor is invisible when zoom is enabled

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

Bug description:
  I have enabled the zoom accessibility feature in GNOME Settings in
  Ubuntu 18.04.2, but the mouse  cursor will be missing every time the
  mouse cursor changes to the spinning one (e.g. when the application is
  doing some tasks in the background or when the application is not
  responding). Mouse cursor will be visible again when the cursor
  changes back to the normal mouse pointer. This happens in both Ubuntu
  (Ambiance-themed) session and the communitheme session. With regard to
  the display server, It happens in X.Org, but in Wayland, the spinning
  cursor is visible but is not spinning. (It stays still)

  Please note that this bug is not related to the bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767648 and the
  proposed update for that bug as this newly-reported bug happens both
  before and after I install the update. Another observation is that the
  bug may be specific to Ubuntu as I previously installed Arch Linux and
  didn't notice this issue.

  Steps to reproduce.
  1. Go to Settings > Universal Access > Zoom and enable it.
  2. Do something that would normally change mouse cursor to the spinning one. 
(e.g. open Synaptic Package Manager)
  3. When the package list is loading, instead of seeing a spinning cursor, the 
mouse cursor becomes invisible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Feb 26 00:58:52 2019
  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'48'
  InstallationDate: Installed on 2019-02-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817609/+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 1817620] Re: High cpu usage on alt-tab-ing

2019-02-26 Thread Daniel van Vugt
** Tags added: bionic performance

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

Title:
  High cpu usage on alt-tab-ing

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

Bug description:
  Switching between apps was feeling extremely laggy and unsmooth after
  some days of keeping the laptop on and just alt-tab-ing between apps
  would keep the cpu consistently at 100% when hitting it more than 8-9
  times per second and *not* letting go of Alt (meaning I stay at the
  same app).

  Also, just whizzing the mouse around on the screen (not moving
  anything) would keep the cpu at 40-50%.

  Some investigation (1) led me to try out restarting the gnome-shell
  instance (killall followed by manually starting it in the terminal),
  upon which everything seemed zippy again. No lagginess. The restart
  was a supposed fix for a memory leak bug (2), but according to the
  comments a bug fix was supposed to have landed in 18.04 long ago. So
  either this has not been fixed or this bug is about something else -
  probably the latter, as the reported memory usage in htop was nowhere
  near the gigabytes of memory reported in the bug issue for 16722297.

  Another thing worth mentioning perhaps, based on comments in (3) found
  through (4), is that I have disabled all extensions. I used to use the
  Coverflow extension.

  Expected behaviour:
  There should be no percieved lag or stuttering in the interface when 
switching between applications.

  Actual behaviour:
  Switching between applications causes a noticable lag/stuttering when the 
computer has been running for an extended period of time (weeks, but where it 
has mostly been suspended, meaning actual usage is limited to 3-4 days).

  
  1. 
https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts
  2. https://bugs.launchpad.net/gnome-shell/+bug/1672297
  3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959
  4. https://askubuntu.com/a/1090987/165026

  System info:
  
  Running Wayland.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  gnome-shell:
Installert: 3.28.3-0ubuntu0.18.04.4
Kandidat:   3.28.3-0ubuntu0.18.04.4
Versjonstabell:
   *** 3.28.3-0ubuntu0.18.04.4 500
  500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+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 1817391] Re: [Acer Aspire XC-603] Audio stuttering

2019-02-26 Thread Daniel van Vugt
Your system has a modified config file here:

https://launchpadlibrarian.net/412444169/modified.conffile..etc.modprobe.d
.alsa-base.conf.txt

--- /etc/modprobe.d/alsa-base.conf  2015-07-31 11:42:17.0 +0800
+++ Downloads/modified.conffile..etc.modprobe.d.alsa-base.conf.txt  
2019-02-27 10:26:15.241596972 +0800
@@ -41,3 +41,4 @@
 options snd-pcsp index=-2
 # Keep snd-usb-audio from beeing loaded as first soundcard
 options snd-usb-audio index=-2
+options snd-hda-intel position_fix=2

but I don't know if that's relevant to this bug. In case it is then
please try commenting out the line:

  options snd-hda-intel position_fix=2

by changing it to:

  #options snd-hda-intel position_fix=2

and reboot.

As for testing other flavours, that's not the same as testing other
versions. Please follow the links in comment #3, boot each of the live
sessions and tell us if they exhibit the same bug.

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

Title:
  [Acer Aspire XC-603] Audio stuttering

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1817391/+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 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window

2019-02-26 Thread Daniel van Vugt
** Description changed:

+ https://gitlab.gnome.org/GNOME/mutter/issues/475
+ 
+ ---
+ 
  This is similar in some ways to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but
  affects only the mouse, not the keyboard, and is consistent almost all
  (99%+) of the time.  This is happening for Ubuntu 18.04.2 LTS (bionic)
  in the default desktop environment (Ubuntu).  It also happens for the
  GNOME and GNOME Classic desktop environments.  The version of gnome-
  shell is 3.28.3-0ubuntu0.18.04.4.
  
  Our program is a blend of C# winforms (Mono) with embedded web browser
  windows using Geckofx45 (mozilla version 45).  Editing windows in the
  program use HTML to display formatting and  typescript/javascript code
  to assist with popup dialogs and other editing help.  Inside these
  editing windows, left mouse clicks are essentially ignored.  Keyboarding
  still works fine as far as I can tell.  Clicking on the gear button
  inside the editing window fails to bring up the Styles dialog more than
  95% of the time.  When the dialog does display, it is always (100%)
  nonfunctional as the first click in it causes it to close immediately.
  
  Tracing the internal behavior of the code, it appears that clicking the
  first time inside the editing (browser) window causes a series of
  WM_FOCUS messages to be sent and the javascript to hook up a left mouse
  click handler to a gear button displayed in the lower left corner of the
  editing window.  This is the expected behavior, and the same as on other
  window managers.  But then, on GNOME Shell only, a series of
  WM_KILLFOCUS messages are sent immediately.  This does not happen for
  other window managers.  (The main window receives a WM_ACTIVATE message
  with the argument to make it deactivate.)  Any other left mouse clicks
  inside that window are ignored >95% of the time, probably only when
  double clicking quickly enough to occur before those messages to lose
  focus/deactivate are handled.  (Right mouse clicks are handled at a
  higher level and appear to function normally.)
  
  The program in question is called Bloom.  The source code is available
  at https://github.com/BloomBooks/BloomDesktop and prebuilt debian/ubuntu
  packages are available at http://packages.sil.org/ubuntu/ as bloom-
  desktop or bloom-desktop-beta.  After spending a few days looking at
  this problem, I've reluctantly come to the conclusion that it must be a
  GNOME Shell bug that I can't work around in our code.  It's working fine
  in Microsoft Windows and all the other Linux window managers that I've
  tested (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE).

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

Title:
  GNOME Shell consistently ignores mouse clicks in a particular app
  window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/475

  ---

  This is similar in some ways to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but
  affects only the mouse, not the keyboard, and is consistent almost all
  (99%+) of the time.  This is happening for Ubuntu 18.04.2 LTS (bionic)
  in the default desktop environment (Ubuntu).  It also happens for the
  GNOME and GNOME Classic desktop environments.  The version of gnome-
  shell is 3.28.3-0ubuntu0.18.04.4.

  Our program is a blend of C# winforms (Mono) with embedded web browser
  windows using Geckofx45 (mozilla version 45).  Editing windows in the
  program use HTML to display formatting and  typescript/javascript code
  to assist with popup dialogs and other editing help.  Inside these
  editing windows, left mouse clicks are essentially ignored.
  Keyboarding still works fine as far as I can tell.  Clicking on the
  gear button inside the editing window fails to bring up the Styles
  dialog more than 95% of the time.  When the dialog does display, it is
  always (100%) nonfunctional as the first click in it causes it to
  close immediately.

  Tracing the internal behavior of the code, it appears that clicking
  the first time inside the editing (browser) window causes a series of
  WM_FOCUS messages to be sent and the javascript to hook up a left
  mouse click handler to a gear button displayed in the lower left
  corner of the editing window.  This is the expected behavior, and the
  same as on other window managers.  But then, on GNOME Shell only, a
  series of WM_KILLFOCUS messages are sent immediately.  This does not
  happen for other window managers.  (The main window receives a
  WM_ACTIVATE message with the argument to make it deactivate.)  Any
  other left mouse clicks inside that window are ignored >95% of the
  time, probably only when double clicking quickly enough to occur
  before those messages to lose focus/deactivate are handled.  (Right
  mouse clicks are handled at a higher leve

[Desktop-packages] [Bug 1817208] Re: [nouveau] desktop pc doesnt wake up after display going black, display connected over displayport

2019-02-26 Thread Daniel van Vugt
** Summary changed:

- desktop pc doesnt wake up after display going black, display connected over 
displayport
+ [nouveau] desktop pc doesnt wake up after display going black, display 
connected over displayport

** Tags added: nouveau

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

Title:
  [nouveau] desktop pc doesnt wake up after display going black, display
  connected over displayport

Status in Ubuntu Budgie:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  My desktop pc doesnt wake up anymore after the screen has gone black.
  I am suspecting that this has to do with the display being connected
  with DisplayPort.

  I am running Ubuntu Budgie 18.04.2

  I've replaced the DisplayPort cable with an HDMI cable now and the issue has 
resolved. So I can confirm that the issue is related to the display being 
connected with a DisplayPort cable.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-02-19 (5 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  LightdmDisplayLog:
   (EE) client bug: timer event3 debounce short: offset negative (-0ms)
   (EE) client bug: timer event3 debounce short: offset negative (-3ms)
   (EE) client bug: timer event3 debounce short: offset negative (-1ms)
  MachineType: EVGA INTERNATIONAL CO.,LTD Default string
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.01
  dmi.board.asset.tag: Default string
  dmi.board.name: 134-KS-E279
  dmi.board.vendor: EVGA INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA INTERNATIONAL CO.,LTD
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd12/29/2016:svnEVGAINTERNATIONALCO.,LTD:pnDefaultstring:pvrDefaultstring:rvnEVGAINTERNATIONALCO.,LTD:rn134-KS-E279:rvr1.0:cvnEVGAINTERNATIONALCO.,LTD:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: EVGA INTERNATIONAL CO.,LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1817208/+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 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked

2019-02-26 Thread Daniel van Vugt
** Summary changed:

- [nvidia-415] gnome-shell eats 100% cpu when seconds display is on and screen 
is locked
+ [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is 
locked

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

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

Title:
  [nvidia] gnome-shell eats 100% cpu when seconds display is on and
  screen is locked

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu 
desktop (gnome-shell), no application running
  just activate second display in gnome tweak, let it lock itself
  the fan is going fast, simply moving the mouse and the fan slow down.
  wrote a simple script to append a top every minut in a log file, show that 
gnome-shell consumes 100% when locked.
  workaround : disabling second displaying and no more CPU usage / fan noise 
when locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  415.27  Thu Dec 20 17:25:03 
CST 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  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: Thu Jan 31 16:19:16 2019
  DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 415.27, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2018-06-08 (236 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago)
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0502
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814125/+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 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg

2019-02-26 Thread Daniel van Vugt
Fix committed to cosmic (see bug 1813350).

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
   Status: Fix Released

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

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

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

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

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

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

** Changed in: gnome-shell (Ubuntu Cosmic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  App grid animation causes heavy CPU spikes and dropped frames in
  Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  Upstream Issues:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  https://gitlab.gnome.org/GNOME/mutter/issues/233

  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.28.2
  System Theme: CommuniTheme

  Opening the Applications Overview (App Grid) displays a very janky
  animation, and my CPU will spike to nearly 90% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall higher impact on resource usage.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-shell/+bug/1750197/+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-02-26 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
Milestone: ubuntu-18.04.2 => ubuntu-18.04.3

-- 
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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-26 Thread Daniel van Vugt
Note to self, and others:

I think there might still be uninitialized memory problems in mutter,
similar to an earlier fix:

https://gitlab.gnome.org/GNOME/mutter/commit/294cceaeb8ecfd468132eff8af1f75c9d60ff21d

I remember thinking at the time that similar bugs might exist elsewhere
in mutter, but was focussed on fixing just the bug at hand (which I
could reproduce). Unfortunately I cannot reproduce bug 1181666, so
that's one reason why it's not yet fixed.

Separately, as mentioned in comment #68, there's a chance that this
patch might help:

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/189

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.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/gnome-shell/+bug/1181666/+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 1758736] Please test proposed package

2019-02-26 Thread Brian Murray
Hello Kaj, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.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.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 

[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-26 Thread Brian Murray
Hello Kaj, or anyone else affected,

Accepted pulseaudio into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:12.2-0ubuntu5 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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: pulseaudio (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10

[Desktop-packages] [Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-26 Thread Cliff Carson
Added the three debug ddebs and re-ran the test with valgrind.  Just as
a note calling gedit and only adding a single text file will also fail
with a memory error.  Have a second system also running 19.04 which also
appears to fails the same way with gedit.

** Attachment added: "valgrind.log"
   
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+attachment/5241932/+files/valgrind.log

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

Title:
  gedit assert failure: corrupted size vs. prev_size

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Third failure of this type.  Occurs when editing one or more files and
  using the window close "X" to terminate.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  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
  AssertionMessage: corrupted size vs. prev_size
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 24 07:13:25 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-06 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcCmdline: /usr/bin/gedit --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f34c797ec00 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f34c797cc9a "corrupted size vs. 
prev_size") at malloc.c:5336
   malloc_consolidate (av=av@entry=0x7f34c79b5c40 ) at malloc.c:4442
   _int_free (av=av@entry=0x7f34c79b5c40 , p=0x5641963c0fd0, 
have_lock=have_lock@entry=1) at malloc.c:4348
   _int_realloc (av=av@entry=0x7f34c79b5c40 , 
oldp=oldp@entry=0x5641963bcfc0, oldsize=oldsize@entry=32784, nb=nb@entry=16400) 
at malloc.c:4636
  Title: gedit assert failure: corrupted size vs. prev_size
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Theo Linkspfeifer
No changes were made to xubuntu-core and xubuntu-desktop yet, so the bug
is obviously not fixed yet. However, the part regarding xfce4-session
was fixed (should not pull in xscreensaver anymore).

** Changed in: xfce4-session (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  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: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-26 Thread Sebastien Bacher
Thanks, valgrind tend to avoid the segfault but does collect the errors
still, your log has one

==18294== Invalid free() / delete / delete[] / realloc()
==18294==at 0x483897B: free (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==18294==by 0x4891CEF: ??? (in /usr/lib/x86_64-linux-gnu/gedit/

That's missing debug symbols though, could you install those debug packages and 
try again?
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.5-1ubuntu1/+build/16354960/+files/libgtk-3-0-dbgsym_3.24.5-1ubuntu1_amd64.ddeb
https://launchpad.net/ubuntu/+source/glib2.0/2.59.2-2/+build/16381172/+files/libglib2.0-0-dbgsym_2.59.2-2_amd64.ddeb
https://launchpad.net/ubuntu/+source/gedit/3.31.90-1build1/+build/16354854/+files/gedit-dbgsym_3.31.90-1build1_amd64.ddeb

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

Title:
  gedit assert failure: corrupted size vs. prev_size

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Third failure of this type.  Occurs when editing one or more files and
  using the window close "X" to terminate.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  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
  AssertionMessage: corrupted size vs. prev_size
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 24 07:13:25 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-06 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcCmdline: /usr/bin/gedit --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gedit
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f34c797ec00 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f34c797cc9a "corrupted size vs. 
prev_size") at malloc.c:5336
   malloc_consolidate (av=av@entry=0x7f34c79b5c40 ) at malloc.c:4442
   _int_free (av=av@entry=0x7f34c79b5c40 , p=0x5641963c0fd0, 
have_lock=have_lock@entry=1) at malloc.c:4348
   _int_realloc (av=av@entry=0x7f34c79b5c40 , 
oldp=oldp@entry=0x5641963bcfc0, oldsize=oldsize@entry=32784, nb=nb@entry=16400) 
at malloc.c:4636
  Title: gedit assert failure: corrupted size vs. prev_size
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1817459/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: openjpa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in gro

Re: [Desktop-packages] [Bug 1817391] Re: Audio stuttering

2019-02-26 Thread Andrew Crome
Hi

all the suggestions that have been offered I have tried no changes were 
made as far as I know, I tried other flavours  all do the same !

On 25/2/19 1:16 pm, Daniel van Vugt wrote:
> It seems you have made some changes to the sound configuration, so can
> you please first try live booting:
>
>http://releases.ubuntu.com/18.10/
>
> and 19.04:
>
>http://cdimages.ubuntu.com/daily-live/current/
>
> then tell us if they have the same problem in a live session?
>
> ** Also affects: pulseaudio (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - Audio stuttering
> + [Acer Aspire XC-603] Audio stuttering
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: pulseaudio (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  [Acer Aspire XC-603] Audio stuttering

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since installing Ubuntu 18.10 on my system which previously had
  windows 10 I now get an intermittent stutter or hiccup for want of a
  better word. It happens in Firefox Quantum and Chrome/Chromium I have
  tried a number of fixes from you tube and various forums, but it still
  happens and I'm at my wits end as it is so random.

  My system is a Acer Aspire XC-603

  1tb HDD
  4gb ram
  Intel Celeron J1900 @ 1.99 GHz

  The sound card is integrated on the mother board

  HDA-Intell-HDA intel PCH this problem is so random i never know when
  its going to happen some times it does it one sometimes multiple
  times.

  I'm totally at a loss

  Can any one help ? I'm relatively new to this

  I'm unable to locate the package version

  I expected a clean audio output without any bugs and I'm getting
  hiccups and stuttering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 5045 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 23 16:10:25 2019
  InstallationDate: Installed on 2019-02-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B1
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-02-23T12:07:26.743044

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1817391/+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 1817738] Re: Can't change virtual terminal when auto-login is enabled

2019-02-26 Thread Eric Desrochers
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: 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/1817738

Title:
  Can't change virtual terminal when auto-login is enabled

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in gdm3 source package in Bionic:
  New
Status in linux source package in Bionic:
  New

Bug description:
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
  mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
  mprotect(0x561e17e87000, 4096, PROT_READ) = 0
  mprotect(0x7f5059e9, 4096, PROT_READ) = 0
  munmap(0x7f5059e7d000, 74655) = 0
  brk(NULL) = 0x561e1843
  brk(0x561e18451000) = 0x561e18451000
  openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
  mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
  close(3) = 0
  openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for 
device)
  close(3) = 0
  openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
  ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
  ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
  ioctl(3, VT_ACTIVATE, 0x4) = 0
  ioctl(3, VT_WAITACTIVE, 0x4

  VT_ACTIVATE will cause a switch to VT number.
  VT_WAITACTIVE will sleep/wait until the specified VT has been activated.

  $ sudo cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  Enable debuglogs doesn't provide additional details.

  As soon as auto-login is turned off, chvt is back to normal.

  The above has been reproduced on Ubuntu:
  - Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
  - Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Norbert
Bug still exists. Simple installation of Xubuntu Desktop on top of 19.04
(disco) mini.iso with `sudo apt install xubuntu-desktop` results in long
list of unwanted GNOME packages.

I have created two outputs of `dpkg -l` before (mini.iso) and after
xubuntu-desktop installation.


$ diff before after  | grep gnome | awk '{print $3}'
language-pack-gnome-en
language-pack-gnome-en-base
libsoup-gnome2.4-1:amd64
gir1.2-gnomebluetooth-1.0:amd64
gir1.2-gnomedesktop-3.0:amd64
gkbd-capplet
gnome-accessibility-themes
gnome-bluetooth
gnome-control-center
gnome-control-center-data
gnome-control-center-faces
gnome-desktop3-data
gnome-font-viewer
gnome-icon-theme
gnome-keyring
gnome-keyring-pkcs11:amd64
gnome-menus
gnome-mines
gnome-online-accounts
gnome-power-manager
gnome-screensaver
gnome-session-bin
gnome-session-common
gnome-settings-daemon
gnome-settings-daemon-common
gnome-shell
gnome-shell-common
gnome-software
gnome-software-common
gnome-software-plugin-snap
gnome-startup-applications
gnome-sudoku
gnome-system-tools
gnome-themes-extra:amd64
gnome-themes-extra-data
gnome-themes-standard
gnome-user-docs
language-pack-gnome-en
language-pack-gnome-en-base
language-selector-gnome
libgnome-bluetooth13:amd64
libgnome-desktop-3-17:amd64
libgnome-games-support-1-3:amd64
libgnome-games-support-common
libgnome-menu-3-0:amd64
libgnomekbd-common
libgnomekbd8:amd64
libpam-gnome-keyring:amd64
libreoffice-gnome
libsoup-gnome2.4-1:amd64
network-manager-gnome
network-manager-pptp-gnome
pinentry-gnome3
policykit-1-gnome
yaru-theme-gnome-shell


and unity:

$ diff before after  | grep unity | awk '{print $3}'
libmeanwhile1:amd64
libunity-control-center1
libunity-protocol-private0:amd64
libunity-scopes-json-def-desktop
libunity-settings-daemon1:amd64
libunity9:amd64
unity-control-center
unity-greeter
unity-settings-daemon
xubuntu-community-wallpapers
xubuntu-community-wallpapers-bionic
yaru-theme-gnome-shell

So user still can't simply install Xubuntu on top of minimal system.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  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: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

2019-02-26 Thread Oliver Kamer
I have the same issue,  but I just double checked, it works on my
machine with bionic, the problem only arises on my cosmic machine.

iPad version: 12.1.4
works with 18.04.01 LTS
doesn't work on 18.10

If anyone has any ideas for me to try, please let me know, I'm happy to
try.

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-02-26 Thread Norbert
** Changed in: xfce4-session (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  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: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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-02-26 Thread Lee Clark
I've tested the updated package in a 18.04 VM and also installed on my
laptop in both cases the issue is fixed.

Thank you everyone who has worked on this issue. Very much appreciated.

-- 
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 1817785] [NEW] installation of texlive-latex-base-doc does not make the documentation available to 'texdoc'

2019-02-26 Thread Ernst Kloppenburg
Public bug reported:

I had texlive installed previously, on a freshly installed 18.04 system.
Now I installed texlive-latex-base-doc.

after installation, texdoc did not find the requested documentation, e.g. 
$texdoc amsldoc
Sorry, no documentation found for amsldoc.

Only after executing 'dpkg-reconfigure texlive-base' the documentation
was found.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: texlive-latex-base-doc (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Feb 26 20:56:05 2019
InstallationDate: Installed on 2014-08-28 (1643 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
SourcePackage: texlive-base
UpgradeStatus: Upgraded to bionic on 2018-08-14 (196 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  installation of texlive-latex-base-doc does not make the documentation
  available to 'texdoc'

Status in texlive-base package in Ubuntu:
  New

Bug description:
  I had texlive installed previously, on a freshly installed 18.04 system.
  Now I installed texlive-latex-base-doc.

  after installation, texdoc did not find the requested documentation, e.g. 
  $texdoc amsldoc
  Sorry, no documentation found for amsldoc.

  Only after executing 'dpkg-reconfigure texlive-base' the documentation
  was found.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 26 20:56:05 2019
  InstallationDate: Installed on 2014-08-28 (1643 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: texlive-base
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1817785/+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 1816205] Re: When using the Gedit icons they disappear from the desktop

2019-02-26 Thread Edson José dos Santos
Any solution for this case? The problem still continues, see attachment

** Attachment added: "Captura de tela de 2019-02-26 16-42-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+attachment/5241880/+files/Captura%20de%20tela%20de%202019-02-26%2016-42-11.png

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

Title:
  When using the Gedit icons they disappear from the desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  Hello guys

  When you open Gedit and edit any text or not, and click save, the
  desktop icons disappear, disappear, and move from side to side. After
  you click save the icons reappear again.

  The following images are attached:

  *

  Olá Pessoal

  Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em
  salvar, os ícones da área de trabalho desaparecem, somem e se movem de
  um lado para o outro. Após clicar em salvar os ícones reaparecem
  novamente.

  Segue imagens em anexo:

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  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: Fri Feb 15 21:46:27 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+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 1816205] Re: When using the Gedit icons they disappear from the desktop

2019-02-26 Thread Edson José dos Santos
Any solution for this case? The problem still continues, see attachment

** Attachment added: "Captura de tela de 2019-02-26 16-41-55.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+attachment/5241879/+files/Captura%20de%20tela%20de%202019-02-26%2016-41-55.png

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

Title:
  When using the Gedit icons they disappear from the desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  Hello guys

  When you open Gedit and edit any text or not, and click save, the
  desktop icons disappear, disappear, and move from side to side. After
  you click save the icons reappear again.

  The following images are attached:

  *

  Olá Pessoal

  Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em
  salvar, os ícones da área de trabalho desaparecem, somem e se movem de
  um lado para o outro. Após clicar em salvar os ícones reaparecem
  novamente.

  Segue imagens em anexo:

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  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: Fri Feb 15 21:46:27 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+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 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty

2019-02-26 Thread Edson José dos Santos
Hello guys

The problem still continues to be attached



Olá Pessoal

O Problema ainda continua vide anexo

** Attachment added: "Captura de tela de 2019-02-26 16-29-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+attachment/5241878/+files/Captura%20de%20tela%20de%202019-02-26%2016-29-42.png

-- 
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 gnome-software package in Ubuntu:
  Triaged
Status in libxmlb package in Ubuntu:
  Triaged

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/gnome-software/+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 1814416] Re: The application store constantly crashing

2019-02-26 Thread Edson José dos Santos
Hello guys

The problem of freezing the Ubuntu Software screen continues, see attachment
Besides the freezing of the screen does not appear the list of installed 
applications, see annex.

Thank you and awaiting solution

**
Olá Pessoal

O problema de congelar a  tela do Ubuntu Software continua, vide anexo
Além do congelamento da tela não aparece a lista de aplicativos instalados, 
vide anexo

Obrigado e aguardando solução?field.comment=
Hello guys

The problem of freezing the Ubuntu Software screen continues, see attachment
Besides the freezing of the screen does not appear the list of installed 
applications, see annex.

Thank you and awaiting solution

**
Olá Pessoal

O problema de congelar a  tela do Ubuntu Software continua, vide anexo
Além do congelamento da tela não aparece a lista de aplicativos instalados, 
vide anexo

Obrigado e aguardando solução

** Attachment added: "Captura de tela de 2019-02-26 09-09-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1814416/+attachment/5241875/+files/Captura%20de%20tela%20de%202019-02-26%2009-09-22.png

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

Title:
  The application store constantly crashing

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  The application store constantly crashing

  Ubuntu Disco Dingo (development branch)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1814416/+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 1814416] Re: The application store constantly crashing

2019-02-26 Thread Edson José dos Santos
Besides the freezing of the screen does not appear the list of installed
applications, see annex.

** Attachment added: "Captura de tela de 2019-02-26 16-29-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1814416/+attachment/5241877/+files/Captura%20de%20tela%20de%202019-02-26%2016-29-42.png

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

Title:
  The application store constantly crashing

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  The application store constantly crashing

  Ubuntu Disco Dingo (development branch)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1814416/+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 1647059] Re: On screen keyboard partially clipped or completely off screen

2019-02-26 Thread yoyoma2
This bug is still present in 16.04 LTS.  The steps are the same.  Login
with the onscreen keyboard once, then logout/reboot.  Then the onscreen
keyboard keyboard is now invisible and turning it on/off doesn't make it
come back.  The two workarounds listed in the initial bug report for
14.04 LTS still work.

Environment: laptop with a 2000 pixel high built-in screen with the lid
closed and connected to a 1080p hdmi tv.


** Attachment added: "ubuntu-bug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1647059/+attachment/5241876/+files/ubuntu-bug.txt

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

Title:
  On screen keyboard partially clipped or completely off screen

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  The on screen keyboard is too low and partially clipped or completely
  off the bottom of the screen.

  On a laptop with a 2000 pixel high built-in screen with the lid closed
  and connected to a 1080p hdmi tv.  The built-in screen is turned off
  in the display settings in case that's relevant.

  Replication steps

  1) Turn on the on screen keyboard and log in using it
  2) Logout or reboot
  3) Lightdm remembers that the on screen keyboard is on and tries to display it

  = Lightdm displays the on screen keyboard using the size of the unused
  2000 pixel high screen for alignment instead of the 1080 high screen
  in use.  Only the top of the keyboard is visible at the bottom of the
  screen.  If lightdm is configured to use 720p then the on screen
  keyboard is completely clipped and invisible.

  The problem only occurs when lightdm remembers that the on screen
  keyboard is on.  Turning it on manually correctly displays it at the
  bottom of the screen.  Toggling a misplaced keyboard off and back on
  unfortunately doesn't fix the problem.

  Workaround 1

  When logging in, after typing password, turn off the on screen
  keyboard and click the small login arrow instead of clicking the on
  screen enter key.  Each time logging in you'll need to turn the on
  screen keyboard on and off again.  Turning off an invisible/clipped
  keyboard and rebooting will temporarily fix the problem.

  Workaround 2

  Dangerous hack.  Run a script to turn off the on screen keyboard in
  lightdm's dconf database.  To make this script run as a startup
  application the sudo commands need to be removed and the lightdm group
  membership given to the user running it as well as r/w access to
  /var/lib/lightdm/.config/dconf/user.

  #!/bin/bash
  sudo cp /var/lib/lightdm/.config/dconf/user ~/.config/dconf/lightdm
  printf %s\\n "user-db:lightdm" > ~/db_profile_lightdm
  export ONSCREEN_KBD=$(DCONF_PROFILE=~/db_profile_lightdm dconf read 
/com/canonical/unity-greeter/onscreen-keyboard)
  #echo 'ONSCREEN_KBD=' $ONSCREEN_KBD
  if [ "$ONSCREEN_KBD" != "false" ]; then
     DCONF_PROFILE=~/db_profile_lightdm dconf write 
/com/canonical/unity-greeter/onscreen-keyboard false
     sudo cp ~/.config/dconf/lightdm /var/lib/lightdm/.config/dconf/user
  fi
  rm -f ~/db_profile_lightdm ~/.config/dconf/lightdm
  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  3 09:16:31 2016
  InstallationDate: Installed on 2014-07-09 (877 days ago)
  InstallationMedia: sonar 13.10 - Release amd64
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-07-09 (877 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1647059/+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 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-02-26 Thread Valeriy Pogrebitskiy
I have installed VirtualBox on my Mac laptop, and built Ubuntu 19.04
guest VM - but had issues with everything that requires HTTP/HTTPS
access. Eventually, I came across this post - which matches the issue I
have and explains why that's so...

To have another look at it, I searched for other ways (other than using
SSL import utility) - and came across 'pk12util' which "supposed to" be
able to import PK12 certificates (under normal circumstances). Using
this utility, I'm getting "SEC_ERROR_LEGACY_DATABASE: The
certificate/key database is in an old, unsupported format" errors:

vpogrebi@vpogrebi-VirtualBox:/usr/local/share/ca-certificates$ sudo pk12util -i 
cacert.pem 
pk12util: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key 
database is in an old, unsupported format.
vpogrebi@vpogrebi-VirtualBox:/usr/local/share/ca-certificates$ sudo pk12util -i 
IDEXX-NewPKI-SHA2-Chain.crt 
pk12util: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key 
database is in an old, unsupported format.
vpogrebi@vpogrebi-VirtualBox:/usr/local/share/ca-certificates$ sudo pk12util -i 
dockercom.crt 
pk12util: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key 
database is in an old, unsupported format.


Hope this can help resolving the issue; but in the meantime - it seems that I 
have to completely delete Ubuntu 18.04 VM and start all over using older (16.04 
?) version.

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+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 1817308] Re: GhostScript Update causes Blue Background

2019-02-26 Thread Brian Foster
I can confirm this latest update also seems to be working fine (no blue
background):

Start-Date: 2019-02-26  18:47:20
Commandline: apt-get dist-upgrade
Requested-By: [redacted]
Upgrade: libldb1:amd64 (2:1.4.0+really1.3.5-2, 2:1.4.0+really1.3.5-2ubuntu0.1), 
libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), 
ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), 
ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 
9.26~dfsg+0-0ubuntu0.18.10.7), libgs9-common:amd64 
(9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), firefox:amd64 
(65.0+build2-0ubuntu0.18.10.1, 65.0.1+build2-0ubuntu0.18.10.1), 
opera-stable:amd64 (58.0.3135.68, 58.0.3135.79)
End-Date: 2019-02-26  18:48:57

This was on my Lubuntu18.10 "recovery" USB-based system (not my main 
Kubuntu18.04 LTS "main"
HDD-based system); same printer (HP OfficeJet Pro 6970).  Many Thanks!

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at 
 and then 
sent an e-mail to marc.deslauri...@ubuntu.com (whose name was on the update 
information) who advised me to post this bug
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-jaxb2-plugin into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/maven-
jaxb2-plugin/0.14.0-1~18.04.1 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: maven-jaxb2-plugin (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam packag

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** No longer affects: graxxia (Ubuntu)

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source packa

[Desktop-packages] [Bug 1814133] Please test proposed package

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-enforcer into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/maven-
enforcer/3.0.0~M2-1~18.04.1 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: maven-plugin-tools (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in U

[Desktop-packages] [Bug 1814133] Please test proposed package

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-plugin-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/maven-
plugin-tools/3.5-6ubuntu1~18.04.1 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.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignme

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted maven-bundle-plugin into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/maven-bundle-plugin/3.5.1-2~18.04.1 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: maven-bundle-plugin (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: maven-enforcer (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ub

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: zeroc-ice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in g

[Desktop-packages] [Bug 1807127] Please test proposed package

2019-02-26 Thread Brian Murray
Hello Eugene, or anyone else affected,

Accepted gnome-desktop3 into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.30.2.1-0ubuntu1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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.

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

Title:
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Bionic:
  Fix Released
Status in gnome-desktop3 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs.

  Test Case
  =
  Install Ubuntu 18.10 32-bit
  Install the update. Log out and log back in.
  Download a picture from the internet.
  Open your file browser to the directory that contains the picture. The file 
should show a thumbnail preview.

  Regression Potential
  
  This fix was cherry-picked to the stable gnome-3-30 branch.
  It was additionally tested by Iain Lane on usrmerged and non-usrmerged 
systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.)

  Other Info
  ==
  Triaged as Critical for 18.04 LTS since this was a regression introduced in 
the security update that backported the bubblewrap hardening to the 
gnome-desktop3 thumbnailer.

  Original Bug Report
  ===
  Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu.

  Looks like same issue in upstream -
  https://bugzilla.redhat.com/show_bug.cgi?id=1651952

  Cause - bubblewrap runs with --ro-bind /lib64 option, then fails.
  Workaround - create empty /lib64 directory at root.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 12:07:28 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-desktop3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1807983] Re: Update gnome-desktop3 to 3.30.2

2019-02-26 Thread Brian Murray
Hello Jeremy, or anyone else affected,

Accepted gnome-desktop3 into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.30.2.1-0ubuntu1 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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-cosmic
** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Update gnome-desktop3 to 3.30.2

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  This updates the GNOME version number reported in Settings > Details > About 
to 3.30.2

  This is the final scheduled point release for GNOME 3.30.

  I'm also cherry-picking a potential crash bug fix from the gnome-3-30
  branch since there might not be another 3.30 release tarball.

  This also includes the fix for LP: #1807127

  Test Case
  =
  From Ubuntu 18.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.30.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807983/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: bindex (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gatk-native-bindings (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: jackson-module-jaxb-annotations (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: jameica-datasource (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jboss-jdeparser2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jboss-modules (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libxml-security-java (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in ort

[Desktop-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu2

---
gtk+3.0 (3.22.30-1ubuntu2) bionic; urgency=medium

  * Cherry-pick Force-emoji-presentation.patch:
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
  * Cherry-pick emojichooser-Pass-chooser-to-add_emoji.patch:
- Fix variant selector in emoji chooser (LP: #1807721)
  * Update Vcs fields for ubuntu/bionic branch

 -- Jeremy Bicha   Mon, 10 Dec 2018 13:39:31 -0500

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+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 1807721] Re: Fix variant selection in emoji chooser

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu2

---
gtk+3.0 (3.22.30-1ubuntu2) bionic; urgency=medium

  * Cherry-pick Force-emoji-presentation.patch:
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
  * Cherry-pick emojichooser-Pass-chooser-to-add_emoji.patch:
- Fix variant selector in emoji chooser (LP: #1807721)
  * Update Vcs fields for ubuntu/bionic branch

 -- Jeremy Bicha   Mon, 10 Dec 2018 13:39:31 -0500

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+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 1817766] [NEW] [SRU] libreoffice 6.1.5 for cosmic

2019-02-26 Thread Olivier Tilloy
Public bug reported:

[Impact]

 * LibreOffice 6.1.5 is the fifth bugfix release of the still 6.1 line. Version 
6.1.4 is currently in cosmic.
   For a list of fixed bugs compared to 6.1.4 see the list of bugs fixed in the 
two release candidates:
 https://wiki.documentfoundation.org/Releases/6.1.5/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/6.1.5/RC2#List_of_fixed_bugs
   (that's a total of 78 bugs)

 * Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU a
minor release rather than cherry-pick selected bug fixes.

[Test Case]

 * No specific test case, bugs fixed upstream hopefully come with
unit/regression tests, and the release itself is extensively exercised
upstream (both in an automated manner and manually) by a community of
testers. Each minor release normally goes through two release
candidates.

 * The libreoffice packages include autopkgtests, those should be run
and verified to pass.

 * General smoke testing of all the applications in the office suite
should be carried out.

[Regression Potential]

 * A minor release with a total of 78 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

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

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

** Affects: libreoffice (Ubuntu Cosmic)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged

** Affects: libreoffice-l10n (Ubuntu Cosmic)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: libreoffice-l10n (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Cosmic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Status: New => Triaged

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

Title:
  [SRU] libreoffice 6.1.5 for cosmic

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libreoffice source package in Cosmic:
  Triaged
Status in libreoffice-l10n source package in Cosmic:
  Triaged

Bug description:
  [Impact]

   * LibreOffice 6.1.5 is the fifth bugfix release of the still 6.1 line. 
Version 6.1.4 is currently in cosmic.
     For a list of fixed bugs compared to 6.1.4 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.5/RC2#List_of_fixed_bugs
     (that's a total of 78 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 78 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Olivier Tilloy
** Also affects: libreoffice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in graxxia package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in

[Desktop-packages] [Bug 1808233] Re: Update gtk to 3.24.4

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

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

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 3.24.3 releases.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
  font you have installed: currently, that's fonts-symbola which we no
  longer install by default). Previously, it was ❙/○ for most languages
  but ON/OFF for English (because English has short words that could fit
  on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.5 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+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 1807721] Re: Fix variant selection in emoji chooser

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+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 1807719] Re: Some emoji in emoji chooser are black & white

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1

---
gtk+3.0 (3.24.4-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1808233)
- Ensure that all emoji from the emoji chooser use emoji presentation
  instead of the black-and-white text presentation (LP: #1807719)
- Fix variant selector in emoji chooser (LP: #1807721)
  * debian/libgtk-3-0.symbols: Add new symbols
  * Add patches to revert late changes that broke our build tests
- Revert-update-some-a11y-test-results.patch
- Revert-Update-a11-test-output.patch
  * Drop wayland-Avoid-crashes-inside-wl_proxy_marshal.patch:
- Applied in new release
  * Update Vcs fields for ubuntu/cosmic branch

 -- Jeremy Bicha   Mon, 21 Jan 2019 12:13:24 -0500

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

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

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: mckoisqldb (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jameica-util (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

2019-02-26 Thread Frank
[OP]

Just tested Marc's new update on my HP OfficeJet 6700 and it seems to
work fine.

Thanks for the quick responses.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at 
 and then 
sent an e-mail to marc.deslauri...@ubuntu.com (whose name was on the update 
information) who advised me to post this bug
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+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 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window

2019-02-26 Thread Steve McConnel
Daniel,
This bug has been reported as
https://gitlab.gnome.org/GNOME/mutter/issues/475.
--
Steve McConnel


On Wed, Feb 20, 2019 at 6:55 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thanks for the quick response.
>
> It sounds like the bug(s) would still exist in the latest mutter/gnome-
> shell code so please report the problem to the Gnome developers here:
>
>   https://gitlab.gnome.org/GNOME/mutter/issues
>
> and then tell us the new issue ID.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816634
>
> Title:
>   GNOME Shell consistently ignores mouse clicks in a particular app
>   window
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   This is similar in some ways to
>   https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but
>   affects only the mouse, not the keyboard, and is consistent almost all
>   (99%+) of the time.  This is happening for Ubuntu 18.04.2 LTS (bionic)
>   in the default desktop environment (Ubuntu).  It also happens for the
>   GNOME and GNOME Classic desktop environments.  The version of gnome-
>   shell is 3.28.3-0ubuntu0.18.04.4.
>
>   Our program is a blend of C# winforms (Mono) with embedded web browser
>   windows using Geckofx45 (mozilla version 45).  Editing windows in the
>   program use HTML to display formatting and  typescript/javascript code
>   to assist with popup dialogs and other editing help.  Inside these
>   editing windows, left mouse clicks are essentially ignored.
>   Keyboarding still works fine as far as I can tell.  Clicking on the
>   gear button inside the editing window fails to bring up the Styles
>   dialog more than 95% of the time.  When the dialog does display, it is
>   always (100%) nonfunctional as the first click in it causes it to
>   close immediately.
>
>   Tracing the internal behavior of the code, it appears that clicking
>   the first time inside the editing (browser) window causes a series of
>   WM_FOCUS messages to be sent and the javascript to hook up a left
>   mouse click handler to a gear button displayed in the lower left
>   corner of the editing window.  This is the expected behavior, and the
>   same as on other window managers.  But then, on GNOME Shell only, a
>   series of WM_KILLFOCUS messages are sent immediately.  This does not
>   happen for other window managers.  (The main window receives a
>   WM_ACTIVATE message with the argument to make it deactivate.)  Any
>   other left mouse clicks inside that window are ignored >95% of the
>   time, probably only when double clicking quickly enough to occur
>   before those messages to lose focus/deactivate are handled.  (Right
>   mouse clicks are handled at a higher level and appear to function
>   normally.)
>
>   The program in question is called Bloom.  The source code is available
>   at https://github.com/BloomBooks/BloomDesktop and prebuilt
>   debian/ubuntu packages are available at
>   http://packages.sil.org/ubuntu/ as bloom-desktop or bloom-desktop-
>   beta.  After spending a few days looking at this problem, I've
>   reluctantly come to the conclusion that it must be a GNOME Shell bug
>   that I can't work around in our code.  It's working fine in Microsoft
>   Windows and all the other Linux window managers that I've tested
>   (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816634/+subscriptions
>

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

Title:
  GNOME Shell consistently ignores mouse clicks in a particular app
  window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is similar in some ways to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but
  affects only the mouse, not the keyboard, and is consistent almost all
  (99%+) of the time.  This is happening for Ubuntu 18.04.2 LTS (bionic)
  in the default desktop environment (Ubuntu).  It also happens for the
  GNOME and GNOME Classic desktop environments.  The version of gnome-
  shell is 3.28.3-0ubuntu0.18.04.4.

  Our program is a blend of C# winforms (Mono) with embedded web browser
  windows using Geckofx45 (mozilla version 45).  Editing windows in the
  program use HTML to display formatting and  typescript/javascript code
  to assist with popup dialogs and other editing help.  Inside these
  editing windows, left mouse clicks are essentially ignored.
  Keyboarding still works fine as far as I can tell.  Clicking on the
  gear button inside the editing window fails to bring up the Styles
  dialog more than 95% of the time.  When the dialog does display, it is
  always (100%) nonfunctional as the first click in it causes it to
  close immediately.

  Tracing the internal behavior 

[Desktop-packages] [Bug 1813583] Re: libdbusmenu ftbfs in 18.04 LTS

2019-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package libdbusmenu -
16.04.1+18.04.20171206-0ubuntu2

---
libdbusmenu (16.04.1+18.04.20171206-0ubuntu2) bionic; urgency=medium

  * Added debian/patches/fix-gtkdoc-checks.patch:
- Fix FTBFS on bionic (LP: #1813583).

 -- Łukasz 'sil2100' Zemczak   Fri, 25 Jan
2019 13:22:04 +0100

** Changed in: libdbusmenu (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  libdbusmenu ftbfs in 18.04 LTS

Status in libdbusmenu package in Ubuntu:
  Fix Released
Status in libdbusmenu source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libdbusmenu ftbfs.

  It is important that main packages all build correctly in case
  security updates need to be released for the package.

  [Test Case]

  Ensure that the new package builds successfully. No sanity-testing
  required as the build failure is caused by a test issue.

  [Regression Potential]

  None. The package FBTFS because of a test-tooling regression regarding
  documentation. The test has been modified to work and run.

  [Original Description]

  FAIL: test_libdbusmenu_glib_gtkdoc
  ==

  TEST: /usr/bin/gtkdoc-check... (pid=20512)
  usage: gtkdoc-check [-h] [--version]
  gtkdoc-check: error: unrecognized arguments: --quiet --keep-going -m=quick 
--GTestLogFD=4
  FAIL: /usr/bin/gtkdoc-check
  FAIL test_libdbusmenu_glib_gtkdoc (exit status: 1)

  FAIL: test_libdbusmenu_gtk_gtkdoc
  =

  TEST: /usr/bin/gtkdoc-check... (pid=20525)
  usage: gtkdoc-check [-h] [--version]
  gtkdoc-check: error: unrecognized arguments: --quiet --keep-going -m=quick 
--GTestLogFD=4
  FAIL: /usr/bin/gtkdoc-check
  FAIL test_libdbusmenu_gtk_gtkdoc (exit status: 1)

  
  Testsuite summary for libdbusmenu 16.04.0
  
  # TOTAL: 16
  # PASS:  14
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  2
  # XPASS: 0
  # ERROR: 0
  
  See tests/test-suite.log
  Please report to t...@canonical.com
  
  Makefile:1946: recipe for target 'test-suite.log' failed
  make[5]: *** [test-suite.log] Error 1
  make[5]: Leaving directory 
'/<>/libdbusmenu-16.04.1+18.04.20171206/builddir/gtk2/tests'
  Makefile:2052: recipe for target 'check-TESTS' failed
  make[4]: *** [check-TESTS] Error 2
  make[4]: Leaving directory 
'/<>/libdbusmenu-16.04.1+18.04.20171206/builddir/gtk2/tests'
  Makefile:2230: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory 
'/<>/libdbusmenu-16.04.1+18.04.20171206/builddir/gtk2/tests'
  Makefile:487: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory 
'/<>/libdbusmenu-16.04.1+18.04.20171206/builddir/gtk2'
  dh_auto_test: cd builddir/gtk2 && make -j1 check VERBOSE=1 returned exit code 
2
  debian/rules:42: recipe for target 'dotest-gtk2' failed
  make[1]: *** [dotest-gtk2] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1813583/+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 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps

2019-02-26 Thread Will Cooke
** Description changed:

  Steps to reproduce
  
  In GNOME Shell, make sure the Ubuntu dock is visible
  Using a finger drag, for example, a LibreOffice icon up and down the dock and 
then drop it on Nautilus.
- Notice that the icon will continue to float above the dock and that the mouse 
will keep the clicky-finger icon.
+ Notice that (sometimes?) the icon will continue to float above the dock and 
that the mouse will keep the clicky-finger icon.
  Notice that you can still open Activities and launch an application
  Notice however, that you can't actually interact with the application you 
have just launched
  
  = What I expected to happen =
  
  When releasing the drag the icon would land back on the dock and I could
  continue to use the desktop as usual.

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

Title:
  Touching and dragging an icon on the dock blocks input to other apps

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce

  In GNOME Shell, make sure the Ubuntu dock is visible
  Using a finger drag, for example, a LibreOffice icon up and down the dock and 
then drop it on Nautilus.
  Notice that (sometimes?) the icon will continue to float above the dock and 
that the mouse will keep the clicky-finger icon.
  Notice that you can still open Activities and launch an application
  Notice however, that you can't actually interact with the application you 
have just launched

  = What I expected to happen =

  When releasing the drag the icon would land back on the dock and I
  could continue to use the desktop as usual.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1817020/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: rdp-alignment (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: rdp-readseq (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: rdp-classifier (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: resteasy3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: unsafe-mock (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Stat

[Desktop-packages] [Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-02-26 Thread Brian Murray
** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  Ubuntu 18.04 interface freeze - during video call or screen sharing
  (using Slack or Zoom)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 (bionic) GNOME 3.28.2 .15.0-45-generic
  Since some updates in the last 2 weeks the interface started to freeze for 
15-20 seconds and then reloads (like a crash of the UI, then it got killed by 
the OS, and then restarted).

  The computer is unusable for 15-20 seconds then it works as nothing
  happened (I got proper sound and I believe everything is working - I
  just don't see it and I can not interact).

  I updated again and again (with the hope it's something terrible that
  affected a lot of users and is already fixed, but looks it's not).

  I started observing the problem more closely:
  The logs app that comes with Ubuntu shows this error (under System section) 
at similar times the interface crashes:

  gnome-shell[22505]: segfault at 28 ip 7f9a80434fe0 sp
  7ffd7fb8b058 error 4 in libmutter-2.so.0.0.0[7f9a803b1000+157000]

  gnome-shell[3366]: segfault at 28 ip 7ffa74598fe0 sp
  7ffc912713c8 error 4 in libmutter-2.so.0.0.0[7ffa74515000+157000]

  The problem appears in most cases when I'm on a video call using Slack or 
Zoom, so probably be related to that (not sure is it limited to that actually - 
may be it happened even when I was not on a call).
  I heavily use multiple desktops and switch between them very often (on a 
single TFT display).

  I'll be glad if anyone has an idea how to resolve this or report it
  (without reinstalling, which actually may be faster and easier).

  Thanks
  NK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+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 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager

2019-02-26 Thread Sebastien Bacher
Said differently, a first step would be to add a testcase that others
could follow to trigger the bug

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

Title:
  [16.04] Unable to import OpenVPN configuration into Network Manager

Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  New

Bug description:
  In 16.04, it is currently not possible to import OpenVPN
  configurations.  Specifically, imports fail with the error of:

  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.

  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.

  --

  An example configuration that fails to import is as follows (with some
  critical components excluded, like a proper remote address, or a
  proper x509 name); this is a config that otherwise works with a Sophos
  XG Firewall-based SSL VPN system

  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
  remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0

  --

  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.

  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.

  Note that the same configuration made by hand in the new VPN window
  works fine, but the import function fails.  (Which is a pretty severe
  bug)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 14:59:54 2018
  InstallationDate: Installed on 2016-12-20 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+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 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager

2019-02-26 Thread Sebastien Bacher
Deleting the bionic line since it lacks enough details to be acted on at
this point and has no owner, if you want to suggest it to be reviewed
for that target best to tag it rls-bb-incoming so the team owning the
package can review and decide if that's an item they want to own (which
is blocking not the case until it has the required details to be worked
on)

** No longer affects: network-manager-openvpn (Ubuntu Bionic)

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

Title:
  [16.04] Unable to import OpenVPN configuration into Network Manager

Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  New

Bug description:
  In 16.04, it is currently not possible to import OpenVPN
  configurations.  Specifically, imports fail with the error of:

  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.

  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.

  --

  An example configuration that fails to import is as follows (with some
  critical components excluded, like a proper remote address, or a
  proper x509 name); this is a config that otherwise works with a Sophos
  XG Firewall-based SSL VPN system

  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
  remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0

  --

  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.

  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.

  Note that the same configuration made by hand in the new VPN window
  works fine, but the import function fails.  (Which is a pretty severe
  bug)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 14:59:54 2018
  InstallationDate: Installed on 2016-12-20 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+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 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-26 Thread Matthias Klose
** Also affects: libjdo-api-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libjdom1-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libnetx-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libquartz-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libswingx-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libxstream-java (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: orthanc-imagej (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in libgpars-groovy-java source package in Bionic:
  Fix Committed
Status in logback source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in

[Desktop-packages] [Bug 1817682] [NEW] Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)

2019-02-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm using Ubuntu 18.04 (bionic) GNOME 3.28.2 .15.0-45-generic
Since some updates in the last 2 weeks the interface started to freeze for 
15-20 seconds and then reloads (like a crash of the UI, then it got killed by 
the OS, and then restarted).

The computer is unusable for 15-20 seconds then it works as nothing
happened (I got proper sound and I believe everything is working - I
just don't see it and I can not interact).

I updated again and again (with the hope it's something terrible that
affected a lot of users and is already fixed, but looks it's not).

I started observing the problem more closely:
The logs app that comes with Ubuntu shows this error (under System section) at 
similar times the interface crashes:

gnome-shell[22505]: segfault at 28 ip 7f9a80434fe0 sp
7ffd7fb8b058 error 4 in libmutter-2.so.0.0.0[7f9a803b1000+157000]

gnome-shell[3366]: segfault at 28 ip 7ffa74598fe0 sp
7ffc912713c8 error 4 in libmutter-2.so.0.0.0[7ffa74515000+157000]

The problem appears in most cases when I'm on a video call using Slack or Zoom, 
so probably be related to that (not sure is it limited to that actually - may 
be it happened even when I was not on a call).
I heavily use multiple desktops and switch between them very often (on a single 
TFT display).

I'll be glad if anyone has an idea how to resolve this or report it
(without reinstalling, which actually may be faster and easier).

Thanks
NK

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


** Tags: bot-comment
-- 
Ubuntu 18.04 interface freeze - during video call or screen sharing (using 
Slack or Zoom)
https://bugs.launchpad.net/bugs/1817682
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1815708] Re: Use ODRS for reviews

2019-02-26 Thread Sebastien Bacher
Robert uploaded to the cosmic SRU queue

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: gnome-software (Ubuntu Cosmic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Use ODRS for reviews

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Bionic:
  New
Status in gnome-software source package in Cosmic:
  In Progress
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The Ubuntu review server is being retired which will cause all Ubuntu package 
reviews to stop working. We are switching to using the Open Desktop Review 
Service (https://odrs.gnome.org/). This plugin has existed for sometime in the 
GNOME Software source, so it is well tested. This change will allow Snap 
packages to be reviewed (new feature).

  [Test Case]
  1. Open GNOME Software
  2. Select a popular app (e.g. Firefox)

  [Expected Result]
  Reviews are shown for this package. They will be different to the previous 
reviews. You are able to create reviews for both .deb and snap apps.

  [Regression Potential]
  There is a risk of new bugs encountered in the ODRS plugin. This has been 
enabled in Disco without major issue and has been used in other distributions 
for many releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1809443] Re: Lock-screen does not enable one to switch keyboard layouts

2019-02-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Lock-screen does not enable one to switch keyboard layouts

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  First, I am not quite sure where the problem lies: in the power
  manager, gnome-screensaver or xfce-screensaver.

  I use keyboard layouts  in more than one alphabet. If the screen-lock
  happens when I am using a non-latin alphabet the unlock screen gives
  me no way of switching keyboard layouts. I have to use a tty login to
  kill the session, or reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 21 10:58:46 2018
  InstallationDate: Installed on 2018-11-06 (44 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1809443/+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 1817617] Re: Video driver

2019-02-26 Thread Timo Aaltonen
you have the hwe stack, so install -intel-hwe-18.04 (and then configure
it)

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

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

Title:
  Video driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb 25 17:05:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1817617/+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 1817308] Re: GhostScript Update causes Blue Background

2019-02-26 Thread Marc Deslauriers
I have found a way to test the new updates, and have released them:

https://usn.ubuntu.com/3866-3/

Thanks.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at 
 and then 
sent an e-mail to marc.deslauri...@ubuntu.com (whose name was on the update 
information) who advised me to post this bug
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+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 1817128] Re: gnome-keyring not automatically unlocked on login

2019-02-26 Thread Edson José dos Santos
The problem still continues, see attachment

Thanks Sebastian


*
O problema ainda continua, vide anexo

Obrigado Sebastian


** Attachment added: "WhatsApp Image 2019-02-26 at 10.39.22.jpeg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+attachment/5241807/+files/WhatsApp%20Image%202019-02-26%20at%2010.39.22.jpeg

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Triaged

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26

2019-02-26 Thread Marc Deslauriers
I have found a way to test the new updates, and have released them:

https://usn.ubuntu.com/3866-3/

Thanks.

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

Title:
  Printer stopped printing paper size 4"x6" after update ghostscript to
  9.26

Status in GS-GPL:
  Fix Released
Status in ghostscript package in Ubuntu:
  Triaged
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released
Status in ghostscript source package in Bionic:
  Fix Released
Status in ghostscript source package in Cosmic:
  Fix Released
Status in ghostscript source package in Disco:
  Triaged

Bug description:
  
  I have an issue with Ghostscript and printing.
  I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 
6"x4"), it does not print anything, however I still able to print A4 paper size.
  I use Ubuntu 18.04 and Gutenprint 5.3.1.

  The printing fail with message:
  
  [Job 143] Start rendering...
  [Job 143] Processing page 1...
  [Job 143]  Unable to open the initial device, quitting.
  [Job 143] Rendering completed
  ...
  [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
  ...
  [Job 143] printer-state-message="Filter failed"
  [Job 143] printer-state-reasons=none

  The message "Unable to open the initial device, quitting" comes from
  Ghostscript.

  
  When I downgrade Ghostscript to 9.22, 
  I am again able to print 4"x6" paper size.

  To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1

  I found similar issue for HP printer at Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=908205

  
  System info:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ghostscript:
Installed: 9.26~dfsg+0-0ubuntu0.18.04.4
Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4
Versions:
   *** 9.26~dfsg+0-0ubuntu0.18.04.4 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   9.22~dfsg+1-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  cups:
Installed: 2.2.7-1ubuntu2.3
Candidate: 2.2.7-1ubuntu2.3
Versions:
   *** 2.2.7-1ubuntu2.3 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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


  1   2   >