date:20190703

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

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

Title:
  High CPU usage of the Xorg process

Status in xorg-server package in Ubuntu:
  New

Bug description:
  when I see for a long time on firefox a video on youtube.
  Xorg is begining to use the processor by incraese a two core processor for an 
average use on 40%.
  When I close firefox xorg ix in excution in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 28 23:05:17 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 82G33/G31 Express Integrated Graphics Controller 
[17aa:303c]
  InstallationDate: Installed on 2015-07-16 (1382 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 222
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=b8485282-6c4c-4911-8054-b3658a58f78b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 52KT38AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr52KT38AUS:bd05/07/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 222
  dmi.product.version: LENOVO 
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 28 19:27:56 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19232 
   vendor GSM
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1826786/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)

2019-07-03 Thread Timo Aaltonen

and disco still works on my hardware

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

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

Title:
  radeonsi: GTK elements become invisible in some applications (GIMP,
  LibreOffice)

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Disco:
  Fix Committed

Bug description:
  [impact]

  imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 :

  "I am currently experiencing some issues with GTK elements
  (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.

  I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).

  My hardware is a Ryzen 5 2400G APU with vega graphics."

  [test case]

  test that GIMP/Libreoffice work fine on AMD Vega/Raven

  [regression potential]

  the fix/workaround is already in mesa 19.0.4, shouldn't regress
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1826786] Re: High CPU usage of the Xorg process

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  High CPU usage of the Xorg process

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  when I see for a long time on firefox a video on youtube.
  Xorg is begining to use the processor by incraese a two core processor for an 
average use on 40%.
  When I close firefox xorg ix in excution in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 28 23:05:17 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 82G33/G31 Express Integrated Graphics Controller 
[17aa:303c]
  InstallationDate: Installed on 2015-07-16 (1382 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 222
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=b8485282-6c4c-4911-8054-b3658a58f78b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 52KT38AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr52KT38AUS:bd05/07/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 222
  dmi.product.version: LENOVO 
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 28 19:27:56 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19232 
   vendor GSM
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1826786/+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 1815550] Re: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted

It looks like most (not all) of the leak is fixed in the next version
19.01.4:

https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/issues/104#note_546483

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

Title:
  gnome-shell high memory and CPU usage when desktop files are
  constantly created or deleted

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  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-extension-desktop-icons/+bug/1815550/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-03 Thread Pat

I have also tested the updated kernel from bionic-proposed using the VM
in which the original problem was first experienced.


'uname -a' after adding bionic-proposed to /etc/apt/sources.list and doing 
'sudo apt update; sudo apt upgrade'

Linux ubuntuvm1 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux


Like Daniel, the changes incorporated into 4.15.0-55 are working for me as well.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64

[Desktop-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio

2019-07-03 Thread Hui Wang

Need you to collect some logs, then let us see if it can be fixed
through kernel driver.


This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1833793

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.


** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Updating to 19.04 audio keeps clicking when nothing is playing audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu version: Ubuntu 19.04
  My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller 
(rev 02)

  What I expect to happen:
  Sound is absolutely quiet when no audio is playing

  What happens now:
  Audio output starts clicking every second incredibly annoyingly and loud.

  What previously happened on Ubuntu 18.10:
  I heard the click twice during boot and then it worked properly (without 
clicking during the time it should have been silent)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1136644] Re: gedit search function is not practical anymore

2019-07-03 Thread Steve Kieu

Yes it is really annoying but Ubuntu seems not care about it.

At the time you type it start searching even the first characters. It
even does not wait for some milisecs to do the search (just to detect
user continue to type text rather than search the whole word. Then it
cause cpu crazy hungry and eventually I have to kill it.

The person who marks this to be invalid? I dare to ask a quesiton? Have
you bothered to repeat what the reporter here do and see if it is valid
or invalid?

SImple. Start gedit - open a pretty large text document (some 200Kb or
so) . Then Ctrl + F. Start typing your word to search.

You will see it and perhaps you wont mark it as Invalid.

Hope somebody cares, somebody hear 

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

Title:
  gedit search function is not practical anymore

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  i use gedit a lot, and i find it comfortable in general.

  the new small search window is extremely impractical. FOCUS PROBLEM:
  CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find 
  and now, typing ESC brings one back to the former place!
  when trying to use CTRL-F again, the search string is replaced by new text.
   
  if one wants to stay in the found passage, one must use the mouse/touchpad to 
click into the text.

  this is an extremely annoying feature/behavior.

  i simply would like to have the old search window + its behavior back. 
  i am working very quickly and mostly using shortcuts. 
  gedit now completely interrupts my way of working. 

  additionally, where are the other search functions such as case-
  sensitive search?

  additionally, i do not want the search function to slow down so much.
  for me it is ok to start the search after i have finished typing my
  search string :-) this new energy-consuming ZEITGEIST-etc-fashion is
  not good for quick workers with serious amounts of data.

  best wishes, vollmanr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1136644/+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 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension

** Summary changed:

- gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
+ gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when 
using the GPaste extension

** Description changed:

  https://errors.ubuntu.com/problem/ced4a4eb6e94763756d8b463a6135c31dd711619
- 
- Using gnome-shell-pomodoro package https://packages.ubuntu.com/bionic
- /gnome-shell-pomodoro (no extension enabled) clicked Start Pomodoro and
- gnome-shell crashed and restarted
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 24 16:34:05 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (999 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa4603b6021 :  
mov(%rbx),%rdi
   PC (0x7fa4603b6021) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   clutter_container_get_child_meta () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (173 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
  when using the GPaste extension

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

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 24 16:34:05 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (999 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa4603b6021 :  
mov(%rbx),%rdi
   PC (0x7fa4603b6021) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   clutter_container_get_child_meta () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (173 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+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 1832946] Re: Icon spring animation performs worse and skips frames if there are windows open

A black screen would be a different bug. Please open a new bug for that
:(

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

Title:
  Icon spring animation performs worse and skips frames if there are
  windows open

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

Bug description:
  You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 15 18:50:37 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-14 (1 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.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/1832946/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

You will also need to undo your change to /etc/default/apport :)

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

If possible, please install 'openssh-server' and log into the machine
from a second machine via the 'ssh' command. Now find out the PID of
gnome-shell (the one running as yourself, not gdm), and type out this
command without yet pressing Enter:

  apport-cli --hanging -P PID

Now reproduce the freeze on the first machine and while it is freezing
press Enter on the above command on the second machine. If it doesn't
work then retry with:

  sudo apport-cli --hanging -P PID

That will hopefully create a new bug report showing where it is
freezing.


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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

It sounds like you're describing two different bugs and only the first
one is your own so I am going to hide the second one from the
description.

** Description changed:

  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.
  
  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell error
  messages being reports. On the longer freezes the display often corrupts
  and the compositor can take a number of minutes to recover.
- 
- I see that there a number of bug reports with similar problems.
- Returning to the computer after a period of activity also can cause a
- long delay when wakoen up by a key press (similsr to #1830255)..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'command-history' redacted by apport
-  b'org.gnome.shell' b'favorite-apps' redacted by apport
-  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'command-history' redacted by apport
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
-  # set this to 0 to disable apport, or to 1 to enable it
-  # you can temporarily override this with
-  # sudo service apport start force_start=1
-  enabled=0
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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

-- 
Mailing

[Desktop-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio

2019-07-03 Thread Avamander

@hui.wang Your suggestion worked and you saved my sanity. Thank you so
much.

Could Ubuntu developers please sort out the power saving, so that the
sound card actually shuts down instead of continuous clicking
(reinitialization?), just for the sake of others on this chipset.

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

Title:
  Updating to 19.04 audio keeps clicking when nothing is playing audio

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu version: Ubuntu 19.04
  My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller 
(rev 02)

  What I expect to happen:
  Sound is absolutely quiet when no audio is playing

  What happens now:
  Audio output starts clicking every second incredibly annoyingly and loud.

  What previously happened on Ubuntu 18.10:
  I heard the click twice during boot and then it worked properly (without 
clicking during the time it should have been silent)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-03 Thread Eric Desrochers

** Tags removed: verification-needed-bionic
** Tags added: 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/1832138

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze

Re: [Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2019-07-03 Thread Ping-Wu

Oops.  False alarm.  The Chinese input frame seems to be working OK in
190703 daily build.    However, the first entry of the input method is
labeled as "汉语“ （Chinese）。  Either that should be changed to "英语”
（English），because it is indeed an English keyboard.  Or assign
ibus-libpinyin as the input method for "汉语" and remove the ibus-libpinyin
（"智能拼音"）entry.  The latter is, of course, preferred.  Please see attached
screenshot.

Anyway, huge improvement!

On Wed, Jul 3, 2019 at 8:51 AM Gunnar Hjalmarsson <
1786...@bugs.launchpad.net> wrote:

> On 2019-07-03 18:15, Ping-Wu wrote:
> > On Wed, Jul 3, 2019 at 12:05 AM Gunnar Hjalmarsson
> > <1786...@bugs.launchpad.net> wrote:
> >> On 2019-07-03 08:31, Ping-Wu wrote:
> >>> I have tried today's daily built iso of 18.04.
> >>
> >> Where did you find that ISO?
> >
> > http://cdimage.ubuntu.com/bionic/daily-live/
>
> Thanks! I didn't know there was such a thing. Then we should be able to
> confirm it the day after version 3.28.1-0ubuntu1.3 has been moved to
> bionic-updates.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786344
>
> Title:
>   Default IBus input method ignored in live session
>
> Status in gnome-settings-daemon package in Ubuntu:
>   Fix Released
> Status in gnome-settings-daemon source package in Bionic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   If you
>
>   * start your computer with a bootable USB stick or DVD with the
> 18.04.2 desktop ISO
>
>   * wait until Ubiquity's welcome screen shows up (only possible on
> systems with legacy BIOS; bug #1766047)
>
>   * select a language which requires an input method for typing
>
>   * click the "Try Ubuntu" button
>
>   no IBus method is made easily available via the input source indicator
>   in the session you enter. If you for instance select zh_CN as language
>   and "Try Ubuntu", you would expect to enter a session with the
>   "Intelligent Pinyin" method included among the available input
>   sources.
>
>   The proposed fix should ensure that an IBus method is always available
>   in "live sessions" in languages which are prepared for it.
>
>   [Test Case]
>
>   1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
>  not included among your available input sources.
>
>   2. Generate the Chinese locale:
>
>  sudo locale-gen zh_CN.UTF-8
>
>   3. Add to ~/.profile this line:
>
>  export LC_CTYPE=zh_CN.UTF-8
>
>   4. Remove the gnome-settings-daemon stamp file:
>
>  rm ~/.local/share/gnome-settings-daemon/input-sources-converted
>
>   5. Log out and log in again.
>
>   => Find that the "Intelligent Pinyin" method was not added (since the
>   sources already in the list prevented it from being added).
>
>   6. Install gnome-settings-daemon from bionic-proposed.
>
>   7. Repeat step 4 and 5.
>
>   => Find that the "Intelligent Pinyin" method was added.
>
>   [Regression Potential]
>
>   The proposed upload includes a small change which specifically
>   addresses the issue as described above. I find that the risk for
>   adverse side effects is low.
>
>   [Original description]
>
>   Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
>   input Chinese character. From Settings -> Regions and Languages, selected
>   Intelligent Pinyin, also could not input Chinese.
>
>   ---
>
>   18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
>   Languages，选择 智能拼音，也无法输入中文。
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+subscriptions
>


** Attachment added: "Screenshot from 2019-07-03 13-00-59.png"
   
https://bugs.launchpad.net/bugs/1786344/+attachment/5274961/+files/Screenshot%20from%202019-07-03%2013-00-59.png

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  If you

  * start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

  * wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

  * select a language which requires an input method for typing

  * click the "Try Ubuntu" button

  no IBus method is made easily available via the input source indicator
  in the session you enter. If you for instance select zh_CN as language
  and "Try Ubuntu", you would expect to enter a session with the
  "Intelligent Pinyin" method included among the available input
  sources.

  The proposed fix should ensure that an IBus method is always available
  in "live sessions" in languages which are prepared for it.

  [Test Case]

  1. Install

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-03 Thread Daniel Gutierrez

bionic-proposed confirmation:

I have tested the updates in bionic-proposed with the VM I created for
this bug as described in comment #63 and can confirm this, like the test
in comment #75, also resolves the issue.

The login screen appears as expected after reboot (with kernel and
updated packages for gir1.2-mutter-2, gnome-shell, gnome-shell-common, &
libmutter-2-0).

uname -a before:
Linux test-vm 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

uname -a after:
Linux test-vm 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA

Re: [Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2019-07-03 Thread Ping-Wu

>
>
> we should be able to
> confirm it the day after version 3.28.1-0ubuntu1.3 has been moved to
> bionic-updates.
>
>
I am seeing that this package has already been moved to the daily build
that I tested.  Please see the attached manifest.

** Attachment added: "bionic-desktop-amd64.manifest"

https://bugs.launchpad.net/bugs/1786344/+attachment/5274960/+files/bionic-desktop-amd64.manifest

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Bionic:
Fix Committed

Bug description:
[Impact]

If you

* start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

* wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

* select a language which requires an input method for typing

* click the "Try Ubuntu" button

no IBus method is made easily available via the input source indicator
in the session you enter. If you for instance select zh_CN as language
and "Try Ubuntu", you would expect to enter a session with the
"Intelligent Pinyin" method included among the available input
sources.

The proposed fix should ensure that an IBus method is always available
in "live sessions" in languages which are prepared for it.

[Test Case]

1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
not included among your available input sources.

2. Generate the Chinese locale:

sudo locale-gen zh_CN.UTF-8

3. Add to ~/.profile this line:

export LC_CTYPE=zh_CN.UTF-8

4. Remove the gnome-settings-daemon stamp file:

rm ~/.local/share/gnome-settings-daemon/input-sources-converted

5. Log out and log in again.

=> Find that the "Intelligent Pinyin" method was not added (since the
sources already in the list prevented it from being added).

6. Install gnome-settings-daemon from bionic-proposed.

7. Repeat step 4 and 5.

=> Find that the "Intelligent Pinyin" method was added.

[Regression Potential]

The proposed upload includes a small change which specifically
addresses the issue as described above. I find that the risk for
adverse side effects is low.

[Original description]

Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+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 1833832] Re: NVIDIA kernel module fails with KMS on optimus hardware

2019-07-03 Thread Doug McMahon

Fixed with latest gdm3 package, i.e 3.32.0-1ubuntu2

** This bug is no longer a duplicate of bug 1716857
   nvidia-drm.modeset=1 results in no monitors detected by Xorg

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

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

Title:
  NVIDIA kernel module fails with KMS on optimus hardware

Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  Test case;
  An optimus laptop
  fresh 19.10 install, updated.
  Install nvidia-driver-430
  Enable nvidia-drm.modeset ( done here thru a .conf /etc/modprobe.d
  Reboot

  What happens:
  Boots to login screen, all attempts to log into a ubuntu session loop back to 
log in screen

  Attached log from journalctl

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 22 21:13:04 2019
  InstallationDate: Installed on 2019-06-22 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2019-06-22T20:52:09.277952

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-07-03 Thread spi

Have the same issue for quite some time. Couldn't find any pattern yet.
Also have the impression gdm is waiting for something. It happens for me
when I am on Ethnernet as well when on wifi.

Have Dell XPS13 with Ubuntu 18.04.2, kernel 4.18.0-25-generic.

Found today dozens in syslog:

/usr/lib/gdm3/gdm-x-session[475]: (II) systemd-logind: got pause for
13:67

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero

[Desktop-packages] [Bug 1835315] [NEW] Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs

2019-07-03 Thread Luca Mastromatteo

Public bug reported:

Ubuntu version: 18.04.2 LTS

Mesa version: 19.0.2
Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, 
LLVM 8.0.0)
Video card: AMD RX 580 8GB, 

There is an issue when the Vulkan mesa RADV drivers are compiled with
LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some
programs using the RADV Vulkan backend

Upgrading to a mesa build compiled with LLVM 9, or reverting back to the
bionic version from bionic-updates (which uses LLVM 6) fixes the
problem.

Using the AMDVLK vulkan driver workarounds the problem too.

The program I have personally tested is RPCS3


I could put additional info about the LLVM bug but at this moment I do
not have the upstream reference

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

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

Title:
  Vulkan funcionality broken when mesa is compiled with LLVM 8 in some
  programs

Status in mesa package in Ubuntu:
  New

Bug description:
  Ubuntu version: 18.04.2 LTS

  Mesa version: 19.0.2
  Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, 
LLVM 8.0.0)
  Video card: AMD RX 580 8GB, 

  There is an issue when the Vulkan mesa RADV drivers are compiled with
  LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some
  programs using the RADV Vulkan backend

  Upgrading to a mesa build compiled with LLVM 9, or reverting back to
  the bionic version from bionic-updates (which uses LLVM 6) fixes the
  problem.

  Using the AMDVLK vulkan driver workarounds the problem too.

  The program I have personally tested is RPCS3


  I could put additional info about the LLVM bug but at this moment I do
  not have the upstream reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+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 1733100] Re: Wrong date display in French

2019-07-03 Thread Jean-Marc

Hello,

Issue is fixed with GNOME Calendar 3.28.2

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

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

Title:
  Wrong date display in French

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  In French, the date displayed in GNOME Calendar should be "le 15
  octobre" and not "le octobre 15", see attached snapshot.

  Ubuntu 16.04
  GNOME Calendar 3.20.4

  Best regards

  Jean-Marc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1733100/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-03 Thread NIckolas Holloway

Hi Ludovic,

I can provide the output as soon as I get back in front of that machine;
I'm referring to the built in smart card reader in a Dell Precision 7730
mobile workstation. It's a Broadcom BCM58102PB0KFBG smart card reader,
my apologies.

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box

2019-07-03 Thread Ludovic Rousseau

I have no idea what the "Precision 7730 smart card reader".
Can you add here the output of the "lsusb" command?

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835285] Re: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.

2019-07-03 Thread daniel CURTIS

** Description changed:

  Hello.
  
  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
- hardening from Ubuntu 18.10 Release. However, it seems to be impossible
- to open any '.pdf' files. After Evince update, I notices I can't open
- any '.pdf'. When I try to do it, Evince show this info:
+ hardening from Ubuntu 18.10 Release. However, now, it is impossible to
+ open any '.pdf' files. When I try to open such file, there is an
+ information (on the red background) in the main Evince window. And It
+ looks this way:
  
  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
  | Failed to load backend for 'application/pdf': 
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `
  
  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:
  
  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `
  
  
  I think, that the whole problem is related with AppArmor changes in the 
latest update, because - for example - day before everything was okay. The 
described problem started right after Evince updated to the latest version. (To 
check differences between versions, please see 2. and 3.). The 'Evince' profile 
has never been changed by the Users. 
  
  If it's about AppArmor: I've tried to change Evince profile mode form 
'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any 
valuable entries in system log files etc. (I'm sorry, but for now, I can not 
check other variants/solutions, such as: (a) disabling Evince profile with 
'aa-disable(8)' command or (b) making links between 
'/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next 
using 'apparmor_parser(8)' command to remove profile etc.)
   
+ Here are some additional informations: 
  
- Here are some technical informations:
+ ✗ Description: Ubuntu 16.04.6 LTS
+ ✗ Release: 16.04
+ ✗ Architecture:  x86_32/i386
+ ✗ Linux: 4.4.0-154-generic (4.4.0-155-generic is already 
installed, but reboot is needed)
  
- ✗ Description:Ubuntu 16.04.6 LTS
- ✗ Release:16.04
- ✗ Architecture: x86_32/i386
- ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, 
but reboot is needed)
- 
- ✓ AppArmor: 2.10.95-0ubuntu2.11
- ✓ Evince:   3.18.2-1ubuntu4.5
+ ✓ AppArmor:  2.10.95-0ubuntu2.11
+ ✓ Evince:   3.18.2-1ubuntu4.5
  
  
  Best regards.
  __
  [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html
  [2] 
http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz
  [3] 
http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz

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

Title:
  PDF files do not open. 'Failed to load backend for 'application/pdf':
  libpdfdocument.so' and 'Invalid ELF header'.

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
  hardening from Ubuntu 18.10 Release. However, now, it is impossible to
  open any '.pdf' files. When I try to open such file, there is an
  information (on the red background) in the main Evince window. And It
  looks this way:

  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
  | Failed to load backend for 'application/pdf': 
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `

  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:

  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `

  
  I think,

[Desktop-packages] [Bug 1835297] [NEW] Precision 7730 smart card reader does not work out of box

2019-07-03 Thread NIckolas Holloway

Public bug reported:

The Canonical certified smart card reader will not function until the
following commands are run:

sudo mkdir /tmp/USH

cd /tmp/USH

sudo mkdir debs

cd debs

sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
dev_1.8.24-1_amd64.deb

sudo wget https://http.kali.org/pool/main/p/pcsc-
lite/libpcsclite1_1.8.24-1_amd64.deb

sudo wget https://http.kali.org/pool/main/p/pcsc-
lite/pcscd_1.8.24-1_amd64.deb

sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
tools_1.5.4-1_amd64.deb

cd ..

sudo apt-get -f install -y

sudo apt purge lib-pcsc* pcscd* -y

sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
install libusb-1.0-0-dev sudo wget https://alioth-
archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

sudo tar xvfj ccid-*.tar.bz2

cd ccid-1.4.25/

./configure

sudo make

sudo make install

sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


sudo systemctl restart pcscd

sudo systemctl status pcscd

sudo pcsc_scan


Additionally, the following commands, which do the same thing as the
above in a cleaner way, do NOT resolve the issue in both the OEM and
public image:

sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

sudo systemctl restart pcscd

sudo systemctl status pcscd

sudo pcsc_scan

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Precision 7730 smart card reader does not work out of box

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  The Canonical certified smart card reader will not function until the
  following commands are run:

  sudo mkdir /tmp/USH

  cd /tmp/USH

  sudo mkdir debs

  cd debs

  sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite-
  dev_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/libpcsclite1_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-
  lite/pcscd_1.8.24-1_amd64.deb

  sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc-
  tools_1.5.4-1_amd64.deb

  cd ..

  sudo apt-get -f install -y

  sudo apt purge lib-pcsc* pcscd* -y

  sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get
  install libusb-1.0-0-dev sudo wget https://alioth-
  archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2

  sudo tar xvfj ccid-*.tar.bz2

  cd ccid-1.4.25/

  ./configure

  sudo make

  sudo make install

  sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/


  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan


  Additionally, the following commands, which do the same thing as the
  above in a cleaner way, do NOT resolve the issue in both the OEM and
  public image:

  sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools
  libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1

  sudo systemctl restart pcscd

  sudo systemctl status pcscd

  sudo pcsc_scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835285] Re: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.

Thank you for your bug report, could you add the log from 'journalctl -b 0' 
after getting the issue?
Also what's the output of 
$ debsums libevdocument3-4


** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  PDF files do not open. 'Failed to load backend for 'application/pdf':
  libpdfdocument.so' and 'Invalid ELF header'.

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
  hardening from Ubuntu 18.10 Release. However, it seems to be
  impossible to open any '.pdf' files. After Evince update, I notices I
  can't open any '.pdf'. When I try to do it, Evince show this info:

  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
  | Failed to load backend for 'application/pdf': 
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `

  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:

  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  | (evince:26918): EvinceDocument-WARNING **:
  | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
  | header
  |
  `

  
  I think, that the whole problem is related with AppArmor changes in the 
latest update, because - for example - day before everything was okay. The 
described problem started right after Evince updated to the latest version. (To 
check differences between versions, please see 2. and 3.). The 'Evince' profile 
has never been changed by the Users. 

  If it's about AppArmor: I've tried to change Evince profile mode form 
'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any 
valuable entries in system log files etc. (I'm sorry, but for now, I can not 
check other variants/solutions, such as: (a) disabling Evince profile with 
'aa-disable(8)' command or (b) making links between 
'/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next 
using 'apparmor_parser(8)' command to remove profile etc.)
   

  Here are some technical informations:

  ✗ Description:Ubuntu 16.04.6 LTS
  ✗ Release:16.04
  ✗ Architecture: x86_32/i386
  ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, 
but reboot is needed)

  ✓ AppArmor: 2.10.95-0ubuntu2.11
  ✓ Evince:   3.18.2-1ubuntu4.5

  
  Best regards.
  __
  [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html
  [2] 
http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz
  [3] 
http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+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 1835295] [NEW] Closing a window on the desktop freezes the desktop for a minute or more.

2019-07-03 Thread Roger James

Public bug reported:

When I close a window on the gnome desktop. The desktop often freezes
for anything between 30 seconds and a number of minutes. I notice this
most often when closing a terminal window with ctrl+d.

When look at the syslog and cpu usage (top) from a terminal logged in
via ssh I see gnome-shell running at 100% and various gnome-shell error
messages being reports. On the longer freezes the display often corrupts
and the compositor can take a number of minutes to recover.

I see that there a number of bug reports with similar problems.
Returning to the computer after a period of activity also can cause a
long delay when wakoen up by a key press (similsr to #1830255)..

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  3 20:04:23 2019
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-07-01 (1097 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

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


** Tags: amd64 apport-bug disco

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  I see that there a number of bug reports with similar problems.
  Returning to the computer after a period of activity also can cause a
  long delay when wakoen up by a key press (similsr to #1830255)..

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1831204] Re: Package geckodriver

This bug was fixed in the package firefox - 68.0+build1-0ubuntu1

---
firefox (68.0+build1-0ubuntu1) eoan; urgency=medium

  * New upstream stable release (68.0build1)

  [ Olivier Tilloy ]
  * Update debian/patches/unity-menubar.patch
  * Work around a GGC bug on i386 and s390x (https://gcc.gnu.org/PR90756)
- debian/patches/skcms-workaround-gcc-bug.patch
  * New firefox-geckodriver package (LP: #1831204)
  * Stop building firefox-testsuite (LP: #1805019)
  * Port chromium-browser's autopkgtests to firefox (LP: #1831454)
  * Remove a patch that is upstream:
- debian/patches/simd-rust-1.33.patch

  [ Rico Tzschichholz ]
  * Update patches
- debian/patches/mark-distribution-search-engines-as-read-only.patch
- debian/patches/no-region-overrides-for-google-search.patch
- debian/patches/partially-revert-google-search-update.patch
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/support-coinstallable-trunk-build.patch
- debian/patches/ubuntu-ua-string-changes.patch
  * Bump build-dep on rustc >= 1.34.0 and cargo >= 0.35
- debian/control{,.in}
  * Update cbindgen to 0.8.7
- debian/build/create-tarball.py
  * Update locales, remove 'as', 'mai', 'ml' and 'or'
  * Update debian/config/searchplugins.conf
  * Follow change of location of list.json for searchplugins
- debian/rules

 -- Olivier Tilloy   Tue, 02 Jul 2019
17:20:58 +0200

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

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

Title:
  Package geckodriver

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Using selenium to drive firefox requires an executable called
  geckodriver, which is nowhere to be found in Ubuntu packages. Instead,
  all the information I could find on the internet suggests fetching
  that executable from upstream and installing it to /usr/local/bin (see
  e.g. https://askubuntu.com/questions/851401/where-to-find-geckodriver-
  needed-by-selenium-python-package).

  The sources for geckodriver are included in the firefox source tarball, and 
the executable is being built when building packages, but it's not installed 
anywhere.
  I propose to create a new firefox-geckodriver binary package for this 
purpose, similar to the chromium-chromedriver package.

  For context, I became interested in driving firefox with selenium when
  attempting to replicate chromium-browser's autopkgtests
  (https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-
  stable/files/head:/debian/tests/).

  Upstream documentation for geckodriver: https://firefox-source-
  docs.mozilla.org/testing/geckodriver/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1831204/+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 1831454] Re: Port chromium-browser's autopkgtests to firefox

This bug was fixed in the package firefox - 68.0+build1-0ubuntu1

---
firefox (68.0+build1-0ubuntu1) eoan; urgency=medium

  * New upstream stable release (68.0build1)

  [ Olivier Tilloy ]
  * Update debian/patches/unity-menubar.patch
  * Work around a GGC bug on i386 and s390x (https://gcc.gnu.org/PR90756)
- debian/patches/skcms-workaround-gcc-bug.patch
  * New firefox-geckodriver package (LP: #1831204)
  * Stop building firefox-testsuite (LP: #1805019)
  * Port chromium-browser's autopkgtests to firefox (LP: #1831454)
  * Remove a patch that is upstream:
- debian/patches/simd-rust-1.33.patch

  [ Rico Tzschichholz ]
  * Update patches
- debian/patches/mark-distribution-search-engines-as-read-only.patch
- debian/patches/no-region-overrides-for-google-search.patch
- debian/patches/partially-revert-google-search-update.patch
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/support-coinstallable-trunk-build.patch
- debian/patches/ubuntu-ua-string-changes.patch
  * Bump build-dep on rustc >= 1.34.0 and cargo >= 0.35
- debian/control{,.in}
  * Update cbindgen to 0.8.7
- debian/build/create-tarball.py
  * Update locales, remove 'as', 'mai', 'ml' and 'or'
  * Update debian/config/searchplugins.conf
  * Follow change of location of list.json for searchplugins
- debian/rules

 -- Olivier Tilloy   Tue, 02 Jul 2019
17:20:58 +0200

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

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

Title:
  Port chromium-browser's autopkgtests to firefox

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  chromium-browser has had for about 2 years autopkgtests that make use
  of selenium to drive the browser in headless mode
  (https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-
  stable/revision/1356).

  Since firefox currently doesn't have any autopkgtests, it would be
  useful to port those as a base (and maybe add more in the future, if
  relevant).

  
  Note that this depends on bug #1831204 being fixed first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1831454/+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 1805019] Re: Please stop building firefox-testsuite

This bug was fixed in the package firefox - 68.0+build1-0ubuntu1

---
firefox (68.0+build1-0ubuntu1) eoan; urgency=medium

  * New upstream stable release (68.0build1)

  [ Olivier Tilloy ]
  * Update debian/patches/unity-menubar.patch
  * Work around a GGC bug on i386 and s390x (https://gcc.gnu.org/PR90756)
- debian/patches/skcms-workaround-gcc-bug.patch
  * New firefox-geckodriver package (LP: #1831204)
  * Stop building firefox-testsuite (LP: #1805019)
  * Port chromium-browser's autopkgtests to firefox (LP: #1831454)
  * Remove a patch that is upstream:
- debian/patches/simd-rust-1.33.patch

  [ Rico Tzschichholz ]
  * Update patches
- debian/patches/mark-distribution-search-engines-as-read-only.patch
- debian/patches/no-region-overrides-for-google-search.patch
- debian/patches/partially-revert-google-search-update.patch
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/support-coinstallable-trunk-build.patch
- debian/patches/ubuntu-ua-string-changes.patch
  * Bump build-dep on rustc >= 1.34.0 and cargo >= 0.35
- debian/control{,.in}
  * Update cbindgen to 0.8.7
- debian/build/create-tarball.py
  * Update locales, remove 'as', 'mai', 'ml' and 'or'
  * Update debian/config/searchplugins.conf
  * Follow change of location of list.json for searchplugins
- debian/rules

 -- Olivier Tilloy   Tue, 02 Jul 2019
17:20:58 +0200

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

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

Title:
  Please stop building firefox-testsuite

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox-testsuite became an empty binary package almost 4 years ago
  https://launchpad.net/ubuntu/+source/firefox/35.0+build3-0ubuntu1

  It is now uninstallable on s390x because it depends on gnome-session (which 
ultimately depends on gjs which is unavailable on s390x now).
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

  I think we might as well remove firefox-testsuite now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1805019/+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 1786344] Re: Default IBus input method ignored in live session

On 2019-07-03 18:15, Ping-Wu wrote:
> On Wed, Jul 3, 2019 at 12:05 AM Gunnar Hjalmarsson
> <1786...@bugs.launchpad.net> wrote:
>> On 2019-07-03 08:31, Ping-Wu wrote:
>>> I have tried today's daily built iso of 18.04.
>>
>> Where did you find that ISO?
>
> http://cdimage.ubuntu.com/bionic/daily-live/

Thanks! I didn't know there was such a thing. Then we should be able to
confirm it the day after version 3.28.1-0ubuntu1.3 has been moved to
bionic-updates.

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Bionic:
Fix Committed

Bug description:
[Impact]

If you

* start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

* wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

* select a language which requires an input method for typing

* click the "Try Ubuntu" button

The proposed fix should ensure that an IBus method is always available
in "live sessions" in languages which are prepared for it.

[Test Case]

1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
not included among your available input sources.

2. Generate the Chinese locale:

sudo locale-gen zh_CN.UTF-8

3. Add to ~/.profile this line:

export LC_CTYPE=zh_CN.UTF-8

4. Remove the gnome-settings-daemon stamp file:

rm ~/.local/share/gnome-settings-daemon/input-sources-converted

5. Log out and log in again.

=> Find that the "Intelligent Pinyin" method was not added (since the
sources already in the list prevented it from being added).

6. Install gnome-settings-daemon from bionic-proposed.

7. Repeat step 4 and 5.

=> Find that the "Intelligent Pinyin" method was added.

[Regression Potential]

The proposed upload includes a small change which specifically
addresses the issue as described above. I find that the risk for
adverse side effects is low.

[Original description]

Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

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

[Desktop-packages] [Bug 1422004] Re: pkservice.py crashed with AttributeError in init(): 'module' object has no attribute 'MainLoop'

2019-07-03 Thread peacecop kalmer:

This is no solution as these lines are commented out in 3.19.6 already. 
Downloading firmware doesn't succeed:
Unable to communicate with device or device is in an error state.

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

Title:
  pkservice.py crashed with AttributeError in __init__(): 'module'
  object has no attribute 'MainLoop'

Status in HPLIP:
  Fix Committed
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip source package in Vivid:
  Fix Released

Bug description:
  If an HP printer needs HPLIP with HP's proprietary plug-in (firmware
  files for printers, proprietary driver code pieces for printing and/or
  scanning) the automatically initiated installation of the plug-in
  fails and causes crash reports, leading to crash report pop-ups and
  non-working printing and scanning functionality. The problem is caused
  by the switchover from Python2 to Python3 in Vivid, especially also
  that the Python3 executable is named "python3" and not "python".

  If the crash happens shortly before shutdown or reboot the pop-up can
  appear right after log-in.

  [Impact]

  All Vivid users who use a printer or multi-function device which needs
  HP's proprietary plug-in get crash pop-ups and their devices will not
  completely work or not work at all.

  [Test Case]

  Connect an HP printer or multi-function device which needs the plug-in
  (for which models see this bug report and the numerous duplicates) and
  set it up. As soon as the plug-in gets downloaded and installed, crash
  reports pop up, and the devices functionality which needs the plug-in
  will not work as plug-in installation does not complete.

  The proposed package solves the problem.

  To test without having an appropriate printer, simply run the command

  hp-plugin

  in a terminal window. With the current package it will fail as
  mentioned, with the proposed package plug-in installation will
  succeed.

  [Regression Potential]

  Very low. The patch is trivial and it affects only users who need the
  plug-in. All users of other HP printers or non-HP printers are not
  affected.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: hplip-data 3.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog: E [14/Feb/2015:19:56:52 +0100] Unable to open listen socket for 
address [v1.::1]:631 - Cannot assign requested address.
  Date: Sat Feb 14 05:59:51 2015
  ExecutablePath: /usr/share/hplip/pkservice.py
  InstallationDate: Installed on 2014-05-08 (282 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  Lpstat:
   device for HP-Deskjet-1000-J110-series: 
usb://HP/Deskjet%201000%20J110%20series?serial=CN33A18VXG05YD
   device for PDF: cups-pdf:/
  MachineType: Acer Aspire 5943G
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   HP-Deskjet-1000-J110-series: HP Deskjet 1000 j110 Series, hpcups 3.15.2
   PDF: Generic CUPS-PDF Printer
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-pkservice
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=e9be64c9-5b7e-438a-ac82-6b89bf946a86 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/bin/hp-pkservice']
  SourcePackage: hplip
  Title: pkservice.py crashed with AttributeError in __init__(): 'module' 
object has no attribute 'MainLoop'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5943G
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5943G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1422004/+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 1835285] Re: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.

2019-07-03 Thread daniel CURTIS

** Description changed:

  Hello.
  
  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
  hardening from Ubuntu 18.10 Release. However, it seems to be impossible
  to open any '.pdf' files. After Evince update, I notices I can't open
  any '.pdf'. When I try to do it, Evince show this info:
  
  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
- | Failed to load backend for 'application/pdf': 
/usr/lib/i386-linux-gnu/evince/4/backends
- | /libpdfdocument.so: Invalid ELF header
+ | Failed to load backend for 'application/pdf': 
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
  |
  `
  
  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:
  
  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
- | (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
- | /libpdfdocument.so: Invalid ELF header
+ | (evince:26918): EvinceDocument-WARNING **:
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
  |
- | (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
- | /libpdfdocument.so: Invalid ELF header
+ | (evince:26918): EvinceDocument-WARNING **:
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
  |
  `
  
  
  I think, that the whole problem is related with AppArmor changes in the 
latest update, because - for example - day before everything was okay. The 
described problem started right after Evince updated to the latest version. (To 
check differences between versions, please see 2. and 3.). The 'Evince' profile 
has never been changed by the Users. 
  
  If it's about AppArmor: I've tried to change Evince profile mode form 
'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any 
valuable entries in system log files etc. (I'm sorry, but for now, I can not 
check other variants/solutions, such as: (a) disabling Evince profile with 
'aa-disable(8)' command or (b) making links between 
'/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next 
using 'apparmor_parser(8)' command to remove profile etc.)
   
  
  Here are some technical informations:
  
  ✗ Description:Ubuntu 16.04.6 LTS
  ✗ Release:16.04
  ✗ Architecture: x86_32/i386
  ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, 
but reboot is needed)
  
  ✓ AppArmor: 2.10.95-0ubuntu2.11
  ✓ Evince:   3.18.2-1ubuntu4.5
  
  
  Best regards.
  __
  [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html
  [2] 
http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz
  [3] 
http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz

** Description changed:

  Hello.
  
  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
  hardening from Ubuntu 18.10 Release. However, it seems to be impossible
  to open any '.pdf' files. After Evince update, I notices I can't open
  any '.pdf'. When I try to do it, Evince show this info:
  
  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
  | Failed to load backend for 'application/pdf': 
- | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
+ | header
  |
  `
  
  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:
  
  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
  | (evince:26918): EvinceDocument-WARNING **:
- | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
+ | header
  |
  | (evince:26918): EvinceDocument-WARNING **:
- | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
header
+ | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF 
+ | header
  |
  `
  
  
  I think, that the whole problem is related with AppArmor changes in the 
latest update, because - for example - day before everything was okay. The 
described problem started right after Evince updated to the latest version. (To 
check differences between versions, please

[Desktop-packages] [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed

2019-07-03 Thread peacecop kalmer:

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

I confirm that the error still exists:
$ hp-setup 

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

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

Searching... (bus=usb, search=(None), desc=0)
 
HP Linux Imaging and Printing System (ver. 3.19.6)
Plugin Download and Install Utility ver. 2.1

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


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

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

Downloading plug-in from: file:///home/peacecop/hplip-3.19.6-plugin.run
1100%Receiving digital keys: /usr/bin/gpg --homedir 
/home/peacecop/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu 
--recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
Creating directory plugin_tmp
Verifying archive integrity... All good.
Uncompressing HPLIP 3.19.6 Plugin Self Extracting 
Archive..

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

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

Plug-in version: 3.19.6
Installed HPLIP version: 3.19.6
Number of files to install: 64

Plugin installation failed
error: Python gobject/dbus may be not installed
error: Plug-in install failed.

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

Done.

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

Title:
  hp-plugin crashes with error: Python gobject/dbus may be not installed

Status in HPLIP:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure an HP LaserJet P1102w, when running hp-plugin
  I get errors and can not proceed:

  nessita@miro:~$ hp-plugin
  error: Unable to locate models.dat file

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

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

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.
  nessita@miro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 19:23:41 2015
  InstallationDate: Installed on 2014-11-30 (100 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet
  MachineType: LENOVO 3249CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET61WW (1.31 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Desktop-packages] [Bug 1835285] [NEW] PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.

2019-07-03 Thread daniel CURTIS

Public bug reported:

Hello.

On Wed, Jun 19. 2019, Evince has been updated to version
'3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
hardening from Ubuntu 18.10 Release. However, it seems to be impossible
to open any '.pdf' files. After Evince update, I notices I can't open
any '.pdf'. When I try to do it, Evince show this info:


,[ Evince .pdf issue ]
|
| Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
| Failed to load backend for 'application/pdf': 
/usr/lib/i386-linux-gnu/evince/4/backends
| /libpdfdocument.so: Invalid ELF header
|
`


There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:


,[ $ evince Docs/foo-bar.pdf ]
|
| (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
| /libpdfdocument.so: Invalid ELF header
|
| (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
| /libpdfdocument.so: Invalid ELF header
|
`


I think, that the whole problem is related with AppArmor changes in the latest 
update, because - for example - day before everything was okay. The described 
problem started right after Evince updated to the latest version. (To check 
differences between versions, please see 2. and 3.). The 'Evince' profile has 
never been changed by the Users. 

If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' 
to 'complain'. Unfortunately, nothing changed. There wasn't any valuable 
entries in system log files etc. (I'm sorry, but for now, I can not check other 
variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' 
command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and 
'/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command 
to remove profile etc.)
 

Here are some technical informations:

✗ Description:  Ubuntu 16.04.6 LTS
✗ Release:  16.04
✗ Architecture: x86_32/i386
✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, but 
reboot is needed)

✓ AppArmor: 2.10.95-0ubuntu2.11
✓ Evince:   3.18.2-1ubuntu4.5


Best regards.
__
[1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html
[2] 
http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz
[3] 
http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz

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


** Tags: elf evince header libpdfdocument.so pdf xenial

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

Title:
  PDF files do not open. 'Failed to load backend for 'application/pdf':
  libpdfdocument.so' and 'Invalid ELF header'.

Status in evince package in Ubuntu:
  New

Bug description:
  Hello.

  On Wed, Jun 19. 2019, Evince has been updated to version
  '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
  hardening from Ubuntu 18.10 Release. However, it seems to be
  impossible to open any '.pdf' files. After Evince update, I notices I
  can't open any '.pdf'. When I try to do it, Evince show this info:

  
  ,[ Evince .pdf issue ]
  |
  | Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
  | Failed to load backend for 'application/pdf': 
/usr/lib/i386-linux-gnu/evince/4/backends
  | /libpdfdocument.so: Invalid ELF header
  |
  `

  
  There is a reference to 
'/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to 
dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is 
already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' 
file via terminal, but nothing changed. Here are the results:

  
  ,[ $ evince Docs/foo-bar.pdf ]
  |
  | (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
  | /libpdfdocument.so: Invalid ELF header
  |
  | (evince:26918): EvinceDocument-WARNING **: 
/usr/lib/i386-linux-gnu/evince/4/backends
  | /libpdfdocument.so: Invalid ELF header
  |
  `

  
  I think, that the whole problem is related with AppArmor changes in the 
latest update, because - for example - day before everything was okay. The 
described problem started right after Evince updated to the latest version. (To 
check differences between versions, please see 2. and 3.). The 'Evince' profile 
has never been changed by the Users. 

  If it's about AppArmor: I've tried to change Evince profile mode form 
'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any 
valuable entries in system log files etc. (I'm sorry, but for now, I can not 
check other

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-07-03 Thread Jeremy Soller

I tested on a System76 NVIDIA laptop that was affected by this issue, on
bionic and disco with proposed enabled. The eDP displays are detected as
builtin displays, as expected.

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

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Bionic:
  Fix Committed
Status in gnome-desktop3 source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false.

  [ Fix ]

  mutter provides a more reliable API to get the "type" of a connector
  (output). The fix switches gnome-desktop to use this API instead of
  looking at the output's name - which can be anything apparently.

  (This drops a visible symbol, but it was only one which you could have
  used if you included "libgnome-desktop/gnome-rr-private.h", which is
  not shipped in the -dev package.)

  [ QA ]

  If you have an affected system - an NVIDIA-using laptop which doesn't
  sleep if the lid is closed: install the update, and check if the
  laptop does now sleep.

  [ Regression potential ]

  Changes the heuristic-based scheme for detecting if a display is
  "built-in" to a method based on the reported connector type. There's a
  low chance that this could be wrong for some machines which were right
  previously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+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 1786344] Re: Default IBus input method ignored in live session

2019-07-03 Thread Ping-Wu

http://cdimage.ubuntu.com/bionic/daily-live/

On Wed, Jul 3, 2019 at 12:05 AM Gunnar Hjalmarsson <
1786...@bugs.launchpad.net> wrote:

> On 2019-07-03 08:31, Ping-Wu wrote:
> > I have tried today's daily built iso of 18.04.
>
> Where did you find that ISO?
>
> > I selected simplified Chinese during boot. Still couldn't input
> > Chinese.
>
> The new version of gnome-settings-daemon is in bionic-proposed. Only
> when it has reached bionic-updates (in 7+ days) it will be taken into
> account when building 18.04 ISOs.
>
> On 2019-07-03 08:49, Ping-Wu wrote:
> > However, the ability to input Chinese characters was activated only
> > after I clicked on the third option "汉语（智能拼音）“。 For a Chinese
> > user, this extra step should not be necessary.
> >
> > Also as shown in the attached screenshot, the first (top) two
> > entries are confusing and have no function.  Should be removed.
>
> Without having a firm opinion on that, I can confirm the behavior. It's
> similar for Japanese as mentioned in bug #1796722.
>
> If that behavior is considered non-desirable, I'd suggest that you file
> a separate Ubiquity bug about it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786344
>
> Title:
>   Default IBus input method ignored in live session
>
> Status in gnome-settings-daemon package in Ubuntu:
>   Fix Released
> Status in gnome-settings-daemon source package in Bionic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   If you
>
>   * start your computer with a bootable USB stick or DVD with the
> 18.04.2 desktop ISO
>
>   * wait until Ubiquity's welcome screen shows up (only possible on
> systems with legacy BIOS; bug #1766047)
>
>   * select a language which requires an input method for typing
>
>   * click the "Try Ubuntu" button
>
>   no IBus method is made easily available via the input source indicator
>   in the session you enter. If you for instance select zh_CN as language
>   and "Try Ubuntu", you would expect to enter a session with the
>   "Intelligent Pinyin" method included among the available input
>   sources.
>
>   The proposed fix should ensure that an IBus method is always available
>   in "live sessions" in languages which are prepared for it.
>
>   [Test Case]
>
>   1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
>  not included among your available input sources.
>
>   2. Generate the Chinese locale:
>
>  sudo locale-gen zh_CN.UTF-8
>
>   3. Add to ~/.profile this line:
>
>  export LC_CTYPE=zh_CN.UTF-8
>
>   4. Remove the gnome-settings-daemon stamp file:
>
>  rm ~/.local/share/gnome-settings-daemon/input-sources-converted
>
>   5. Log out and log in again.
>
>   => Find that the "Intelligent Pinyin" method was not added (since the
>   sources already in the list prevented it from being added).
>
>   6. Install gnome-settings-daemon from bionic-proposed.
>
>   7. Repeat step 4 and 5.
>
>   => Find that the "Intelligent Pinyin" method was added.
>
>   [Regression Potential]
>
>   The proposed upload includes a small change which specifically
>   addresses the issue as described above. I find that the risk for
>   adverse side effects is low.
>
>   [Original description]
>
>   Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
>   input Chinese character. From Settings -> Regions and Languages, selected
>   Intelligent Pinyin, also could not input Chinese.
>
>   ---
>
>   18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
>   Languages，选择 智能拼音，也无法输入中文。
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+subscriptions
>

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  If you

  * start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

  * wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

  * select a language which requires an input method for typing

  * click the "Try Ubuntu" button

  no IBus method is made easily available via the input source indicator
  in the session you enter. If you for instance select zh_CN as language
  and "Try Ubuntu", you would expect to enter a session with the
  "Intelligent Pinyin" method included among the available input
  sources.

  The proposed fix should ensure that an IBus method is always available
  in "live sessions" in languages which are prepared for it.

  [Test Case]

  1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
 not included among your

[Desktop-packages] [Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-07-03 Thread Kostadin Stoilov

Hi,
I've been running without the gpaste extension for a few weeks and gnome-shell 
no longer crashes.
So I guess this bug should be reassigned?

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

  Using gnome-shell-pomodoro package https://packages.ubuntu.com/bionic
  /gnome-shell-pomodoro (no extension enabled) clicked Start Pomodoro
  and gnome-shell crashed and restarted

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 24 16:34:05 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (999 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fa4603b6021 :  
mov(%rbx),%rdi
   PC (0x7fa4603b6021) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   clutter_container_get_child_meta () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (173 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+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 1720730] Re: Feature Request: proper "Auto-hide" for Ubuntu Dock, not just "Intelli-hide".

2019-07-03 Thread Jesse

Submitted bug via github. Issue ID is 969 (https://github.com/micheleg
/dash-to-dock/issues/969).

** Bug watch added: github.com/micheleg/dash-to-dock/issues #969
   https://github.com/micheleg/dash-to-dock/issues/969

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

Title:
  Feature Request: proper "Auto-hide" for Ubuntu Dock, not just
  "Intelli-hide".

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

Bug description:
  Wasn't sure if I was supposed to file this feature request under the
  Ubuntu Dock GNOME shell extension or here.

  BEHAVIOR
  Currently, Enabling "Auto-hide" in the Dock section of GNOME control center 
actually "intelli-hides" the dock, so that it always is present if no windows 
are near it.

  EXPECTED BEHAVIOR
  For their to be an option somewhere in the dock settings to be able to enable 
genuine Auto-hide for users who want the Ubuntu Dock hidden even if there are 
no windows near it.

  Feature requested while using:
  Ubuntu 17.10 beta 2
  GNOME Control Center 3.26.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1720730/+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 1834052] Re: autopkgtest failures: Chromium-Related in Tests

2019-07-03 Thread Olivier Tilloy

I'm building a chromium snap with a patched chromedriver that defaults
to "/snap/chromium/current/command-chromium.wrapper" for the
binary_location option. Once done I'll test and confirm whether this
fixes the kopano-webapp autopkgtests without changes.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  In Progress
Status in kopano-webapp package in Ubuntu:
  In Progress

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  --
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+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 1835220] Re: Please support /usr/lib64/sane

2019-07-03 Thread Bug Watch Updater

** Changed in: sane-backends (Debian)
   Status: Unknown => New

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane. It would be great if that directory could be
  supported too.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  If Debian accepts the proposal in ,
  the change is a SRU candidate to bionic at first hand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

I decided to break out the /usr/lib64/sane thing to bug #1835220, so we
can proceed with the more important bionic fix.

** Patch added: "sane-backends_lp1728012_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+attachment/5274902/+files/sane-backends_lp1728012_bionic.debdiff

** Description changed:

  [Impact]
  
-  * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane
+  * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane
  dll looks for third party drivers. This configuration effectively broke
  backward compatibility for all existing third-party drivers.
  
-  * A large swath of these third party drivers (most of them) are no
+  * A large swath of these third party drivers (most of them) are no
  longer supported by the OEM, so maintaining compatibility is important.
  
-  * No open source replacement drivers are currently available, nor does
+  * No open source replacement drivers are currently available, nor does
  the community have the resources to easily replace them.
  
-  * This bug represents a substantial portion of the scanners in use.
+  * This bug represents a substantial portion of the scanners in use.
  
  Scanners known to be affected include, but are not limited to:
  
-  - Brother Scanners (all Brother scanners before brscan4)
-   - DCP-145C
-   - DCP-163C
-   - DCP-165C
-   - DCP-167C
-   - DCP-185C
-   - DCP-195C
-   - DCP-197C
-   - DCP-365CN
-   - DCP-373CW
-   - DCP-375CW
-   - DCP-377CW
-   - DCP-383C
-   - DCP-385C
-   - DCP-387C
-   - DCP-395CN
-   - DCP-585CW
-   - DCP-6690CW
-   - DCP-7030
-   - DCP-7040
-   - DCP-7045N
-   - DCP-8070D
-   - DCP-8080DN
-   - DCP-8085DN
-   - DCP-9010CN
-   - DCP-9040CN
-   - DCP-9042CDN
-   - DCP-9045CDN
-   - DCP-J125
-   - DCP-J315W
-   - DCP-J515W
-   - DCP-J715W
-   - MFC-250C
-   - MFC-255CW
-   - MFC-257CW
-   - MFC-290C
-   - MFC-295CN
-   - MFC-297C
-   - MFC-490CW
-   - MFC-495CW
-   - MFC-5490CN
-   - MFC-5890CN
-   - MFC-5895CW
-   - MFC-6490CW
-   - MFC-6890CDW
-   - MFC-7320
-   - MFC-7340
-   - MFC-7345N
-   - MFC-7440N
-   - MFC-7450
-   - MFC-7840N
-   - MFC-7840W
-   - MFC-790CW
-   - MFC-795CW
-   - MFC-8370DN
-   - MFC-8380DN
-   - MFC-8480DN
-   - MFC-8510DN
-   - MFC-8680DN
-   - MFC-8880DN
-   - MFC-8890DW
-   - MFC-9010CN
-   - MFC-9120CN
-   - MFC-9320CW
-   - MFC-9440CN
-   - MFC-9450CDN
-   - MFC-9840CDW
-   - MFC-990CW
-   - MFC-J220
-   - MFC-J265W
-   - MFC-J270W
-   - MFC-J410
-   - MFC-J410W
-   - MFC-J415W
-   - MFC-J615W
-   - MFC-J630W 
+  - Brother Scanners (all Brother scanners before brscan4)
+   - DCP-145C
+   - DCP-163C
+   - DCP-165C
+   - DCP-167C
+   - DCP-185C
+   - DCP-195C
+   - DCP-197C
+   - DCP-365CN
+   - DCP-373CW
+   - DCP-375CW
+   - DCP-377CW
+   - DCP-383C
+   - DCP-385C
+   - DCP-387C
+   - DCP-395CN
+   - DCP-585CW
+   - DCP-6690CW
+   - DCP-7030
+   - DCP-7040
+   - DCP-7045N
+   - DCP-8070D
+   - DCP-8080DN
+   - DCP-8085DN
+   - DCP-9010CN
+   - DCP-9040CN
+   - DCP-9042CDN
+   - DCP-9045CDN
+   - DCP-J125
+   - DCP-J315W
+   - DCP-J515W
+   - DCP-J715W
+   - MFC-250C
+   - MFC-255CW
+   - MFC-257CW
+   - MFC-290C
+   - MFC-295CN
+   - MFC-297C
+   - MFC-490CW
+   - MFC-495CW
+   - MFC-5490CN
+   - MFC-5890CN
+   - MFC-5895CW
+   - MFC-6490CW
+   - MFC-6890CDW
+   - MFC-7320
+   - MFC-7340
+   - MFC-7345N
+   - MFC-7440N
+   - MFC-7450
+   - MFC-7840N
+   - MFC-7840W
+   - MFC-790CW
+   - MFC-795CW
+   - MFC-8370DN
+   - MFC-8380DN
+   - MFC-8480DN
+   - MFC-8510DN
+   - MFC-8680DN
+   - MFC-8880DN
+   - MFC-8890DW
+   - MFC-9010CN
+   - MFC-9120CN
+   - MFC-9320CW
+   - MFC-9440CN
+   - MFC-9450CDN
+   - MFC-9840CDW
+   - MFC-990CW
+   - MFC-J220
+   - MFC-J265W
+   - MFC-J270W
+   - MFC-J410
+   - MFC-J410W
+   - MFC-J415W
+   - MFC-J615W
+   - MFC-J630W
  
-  - Dell MFP Laser Printer 1135n
+  - Dell MFP Laser Printer 1135n
  
-  - Epson Scanners
-   - All scanners supported by the libsane-epk driver
-   - All scanners supported by the iscan driver
-   - Epson Perfection V10
-   - Epson Perfection V1000
+  - Epson Scanners
+   - All scanners supported by the libsane-epk driver
+   - All scanners supported by the iscan driver
+   - Epson Perfection V10
+   - Epson Perfection V1000
    - Epson WorkForce GT-1500
-   - Epson Perfection V33
+   - Epson Perfection V33
  
-  - Samsung M2070
+  - Samsung M2070
  
-  - Xerox Workcentre 3225
+  - Xerox Workcentre 3225
  
-  * This was working in the 17.04 release.  18.10 is an LTS release, so
- backporting is warranted for the 18.10 release.
+  * This was working in the 17.04 release.  18.04 is an LTS release, so
+ backporting is warranted for the 18.04 release.
  
  [Test Case]
  
-  * Following the standard installation procedures for any of the
+  * Following the standard installation procedures for any of the
  affected scanner drivers results in the driver files being installed to
  /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux-
  gnu/sane.

[Desktop-packages] [Bug 1833555] Re: Add OEM->Family

2019-07-03 Thread Jean-Baptiste Lallement

patch against 1.3.1 in bionic. 
This patch also includes fixes of the testsuite that affect the same code than 
the code modified by the patch.

** Patch added: "ubuntu-report_1.3.1_1.3.2.diff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+attachment/5274871/+files/ubuntu-report_1.3.1_1.3.2.diff

** Changed in: ubuntu-report (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  Add OEM->Family

Status in ubuntu-report package in Ubuntu:
  Fix Released
Status in ubuntu-report source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Some OEM store the commercial name of the product into the Family field of 
the system information record of smbios.

  This update retrieves this information from
  /sys/class/dmi/id/product_family and adds it to the OEM->Family field

  [Test Case]
  From a terminal run the command:
  $ ubuntu-report show 

  Verify that it contains a field OEM/Family and it matches the content
  of /sys/class/dmi/id/product_family

  The output should look like:
"OEM": {
  "Vendor": "Dell Inc.",
  "Product": "Inspiron 7472",
  "Family": "Inspiron"
},

  It is possible that the field is empty.


  [Regression Potential]
  Very low. This field didn't exist before and it is covered by a full 
regression test suite. 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-report 1.5.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:49:35 2019
  Dependencies:
   gcc-9-base 9.1.0-4ubuntu1
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-4ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2014-07-15 (1801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+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 1825717] Re: hplip issue during hp-setup - stuck at plugin install

2019-07-03 Thread Till Kamppeter

To the HP developers at HP:

Debian and Ubuntu (and perhaps also other modern Linux distributions)
have multi-architecture support which allows installing libraries for
different architectures on the same system (most prominently having also
32-bit i386 libraries on 64-bit amd64 systems). The libraries which got
formerly installed into /usr/lib/ are now installed into /usr/lib/x86_64
-linux-gnu for the 64-bit amd64 versions of the library binaries, into
/usr/lib/i386-linux-gnu for the 32-bit i386 versions, ...

The proprietary plugin seems not to take account of this and searches
for its libraries on hard-coded paths. Therefore adding the links as
described in comment #6 solves the problem.

Could you make the plugin in a way that it either searches alternative
paths or checks by environment variables whether the libraries are in
multi-architecture sub-directories or at other alternative positions?
This would make it much easier for users of Linux distributions to use
the plugin with the distribution's packages of HPLIP.

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1825717/+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 1835224] Re: gnome-terminal drops pam_group config

2019-07-03 Thread Philipp Takacs

** Description changed:

  If you use pam_group to add users to a group and open gnome-terminal the
  dynamic group is lost.
  
  How to reproduce:
  
  enable pam_group
  add "*;*;*;Al-2400;dialout" to /etc/security/group.conf
- log in with a user which is not in the video group
+ log in with a user which is not in the dialout group
  open gnome-terminal
- check with id if you in the video group
+ check with id if you in the dialout group
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed Jul  3 14:52:29 2019
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-terminal drops pam_group config

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If you use pam_group to add users to a group and open gnome-terminal
  the dynamic group is lost.

  How to reproduce:

  enable pam_group
  add "*;*;*;Al-2400;dialout" to /etc/security/group.conf
  log in with a user which is not in the dialout group
  open gnome-terminal
  check with id if you in the dialout group

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed Jul  3 14:52:29 2019
  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/1835224/+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 1821863] Re: Need to add Intel CML related pci-id's

This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1

---
mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium

  * Backport to bionic.

mesa (19.0.2-1ubuntu1.1) disco; urgency=medium

  * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements
with GTK on Vega/Raven. (LP: #1831498)

mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)
  * control: Build-depend on libsensors4-dev.

 -- Timo Aaltonen   Tue, 04 Jun 2019 00:10:13 +0300

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

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)

This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1

---
mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium

  * Backport to bionic.

mesa (19.0.2-1ubuntu1.1) disco; urgency=medium

  * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements
with GTK on Vega/Raven. (LP: #1831498)

mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)
  * control: Build-depend on libsensors4-dev.

 -- Timo Aaltonen   Tue, 04 Jun 2019 00:10:13 +0300

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

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

Title:
  radeonsi: GTK elements become invisible in some applications (GIMP,
  LibreOffice)

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Disco:
  Fix Committed

Bug description:
  [impact]

  imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 :

  "I am currently experiencing some issues with GTK elements
  (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.

  I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).

  My hardware is a Ryzen 5 2400G APU with vega graphics."

  [test case]

  test that GIMP/Libreoffice work fine on AMD Vega/Raven

  [regression potential]

  the fix/workaround is already in mesa 19.0.4, shouldn't regress
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1

---
mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium

  * Backport to bionic.

mesa (19.0.2-1ubuntu1.1) disco; urgency=medium

  * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements
with GTK on Vega/Raven. (LP: #1831498)

mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)
  * control: Build-depend on libsensors4-dev.

 -- Timo Aaltonen   Tue, 04 Jun 2019 00:10:13 +0300

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

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1835224] [NEW] gnome-terminal drops pam_group config

2019-07-03 Thread Philipp Takacs

Public bug reported:

If you use pam_group to add users to a group and open gnome-terminal the
dynamic group is lost.

How to reproduce:

enable pam_group
add "*;*;*;Al-2400;dialout" to /etc/security/group.conf
log in with a user which is not in the video group
open gnome-terminal
check with id if you in the video group

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Wed Jul  3 14:52:29 2019
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (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 gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1835224

Title:
  gnome-terminal drops pam_group config

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If you use pam_group to add users to a group and open gnome-terminal
  the dynamic group is lost.

  How to reproduce:

  enable pam_group
  add "*;*;*;Al-2400;dialout" to /etc/security/group.conf
  log in with a user which is not in the video group
  open gnome-terminal
  check with id if you in the video group

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed Jul  3 14:52:29 2019
  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/1835224/+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 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

This bug was fixed in the package libreoffice-l10n -
1:6.0.7-0ubuntu0.18.04.7

---
libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.7) bionic; urgency=medium

  * debian/patches/cpdmgr-check-dbus-desc.diff (LP: #1798074):
- Only create CPDManager if D-Bus descriptions present.
- Fixes LibreOffice startup crash when CPD packages installed.

libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.6) bionic; urgency=medium

  [ Ikuya Awashiro ]
  * debian/patches/new-japanese-era-name.patch (LP: #1827451):
Add new Japanse era name "Reiwa" support which taken from upstream:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=cacbb0faef77ae8462de9ff5c7307a6a2e28b2bb

https://cgit.freedesktop.org/libreoffice/core/commit/?id=597c5d75b8e72d429e096535334eaac7973455ef

  [ Olivier Tilloy ]
  * debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for custom PPA builds) (LP: #1822839)
  * debian/patches/java.vendor-Ubuntu.patch: also make jvmfwk recognize
"Ubuntu" as java.vendor (LP: #1822839)

  [ Rene Engelhard ]
  * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian"
as java.vendor as that's what is set in openjdk 11 >= 11.0.3+4-2
- see #926009 (closes: #926318) (LP: #1822839)
  * debian/control.gtk3.in:
- make libreoffice-gtk3 recommend gstreamer1.0-gtk3 (LP: #1820062)

 -- Marcus Tomlinson   Fri, 31 May 2019
11:43:00 +0100

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

   * The fix is currently in LibreOffice 6.2.2+ on disco and eoan.

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

   * A combination of autopkgtests and manual 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/df-libreoffice/+bug/1820062/+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 1798074] Re: LIbreoffice crashes on startup

This bug was fixed in the package libreoffice-l10n -
1:6.0.7-0ubuntu0.18.04.7

---
libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.7) bionic; urgency=medium

  * debian/patches/cpdmgr-check-dbus-desc.diff (LP: #1798074):
- Only create CPDManager if D-Bus descriptions present.
- Fixes LibreOffice startup crash when CPD packages installed.

libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.6) bionic; urgency=medium

  [ Ikuya Awashiro ]
  * debian/patches/new-japanese-era-name.patch (LP: #1827451):
Add new Japanse era name "Reiwa" support which taken from upstream:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=cacbb0faef77ae8462de9ff5c7307a6a2e28b2bb

https://cgit.freedesktop.org/libreoffice/core/commit/?id=597c5d75b8e72d429e096535334eaac7973455ef

  [ Olivier Tilloy ]
  * debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for custom PPA builds) (LP: #1822839)
  * debian/patches/java.vendor-Ubuntu.patch: also make jvmfwk recognize
"Ubuntu" as java.vendor (LP: #1822839)

  [ Rene Engelhard ]
  * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian"
as java.vendor as that's what is set in openjdk 11 >= 11.0.3+4-2
- see #926009 (closes: #926318) (LP: #1822839)
  * debian/control.gtk3.in:
- make libreoffice-gtk3 recommend gstreamer1.0-gtk3 (LP: #1820062)

 -- Marcus Tomlinson   Fri, 31 May 2019
11:43:00 +0100

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  LIbreoffice crashes on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
  packages installed.

   * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.

  [Test Case]

   1. apt install cpdb-backend-gcp
   2. run LibreOffice

  [Regression Potential]

   * We're backporting a patch that has already been applied to 6.2.0+
  with no regression, so potential for regression here is low.

   * A combination of autopkgtests and manual testing should provide
  reasonable confidence that no regressions sneaked in.

  [Original Description]

  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:

  $ libreoffice --norestore
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]

[Desktop-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package libclc -
0.2.0+git20190306-1~ubuntu18.04.1

---
libclc (0.2.0+git20190306-1~ubuntu18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 10 Apr 2019 13:52:07 +0300

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 -
19.0.1-1~18.04.1

---
xserver-xorg-video-amdgpu-hwe-18.04 (19.0.1-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 29 May 2019 13:19:12 +0300

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1

---
libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 10 Apr 2019 13:54:06 +0300

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

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

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1821863] Re: Need to add Intel CML related pci-id's

This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1

---
libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 10 Apr 2019 13:54:06 +0300

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

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

This bug was fixed in the package libreoffice-l10n -
1:6.0.7-0ubuntu0.18.04.7

---
libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.7) bionic; urgency=medium

  * debian/patches/cpdmgr-check-dbus-desc.diff (LP: #1798074):
- Only create CPDManager if D-Bus descriptions present.
- Fixes LibreOffice startup crash when CPD packages installed.

libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.6) bionic; urgency=medium

  [ Ikuya Awashiro ]
  * debian/patches/new-japanese-era-name.patch (LP: #1827451):
Add new Japanse era name "Reiwa" support which taken from upstream:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=cacbb0faef77ae8462de9ff5c7307a6a2e28b2bb

https://cgit.freedesktop.org/libreoffice/core/commit/?id=597c5d75b8e72d429e096535334eaac7973455ef

  [ Olivier Tilloy ]
  * debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for custom PPA builds) (LP: #1822839)
  * debian/patches/java.vendor-Ubuntu.patch: also make jvmfwk recognize
"Ubuntu" as java.vendor (LP: #1822839)

  [ Rene Engelhard ]
  * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian"
as java.vendor as that's what is set in openjdk 11 >= 11.0.3+4-2
- see #926009 (closes: #926318) (LP: #1822839)
  * debian/control.gtk3.in:
- make libreoffice-gtk3 recommend gstreamer1.0-gtk3 (LP: #1820062)

 -- Marcus Tomlinson   Fri, 31 May 2019
11:43:00 +0100

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in openjdk-lts source package in Disco:
  New
Status in libreoffice package in Debian:
  Won't Fix

Bug description:
  [Impact]

   * A recent OpenJDK update changes the value of the "java.vendor"
  property from "Oracle Corporation" to "Private Build". This breaks the
  code in LibreOffice that detects an installed JVM.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Launch the LibreOffice Start Center
   2. Open Tools > Options
   3. Navigate to LibreOffice > Advanced
   4. A JRE should be listed with Location: /usr/lib/jvm/...

  [Regression Potential]

   * This fix is small and concentrated so potential for regression
  should be relatively low.

   * A combination of autopkgtests and manual 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/df-libreoffice/+bug/1822839/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.4-1ubuntu3~18.04.1

---
xorg-server-hwe-18.04 (2:1.20.4-1ubuntu3~18.04.1) bionic; urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Thu, 02 May 2019 11:06:54 +0300

** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 -
1:1.0.16-1~18.04.1

---
xserver-xorg-video-nouveau-hwe-18.04 (1:1.0.16-1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 29 May 2019 13:19:20 +0300

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 -
1:19.0.1-0ubuntu1~18.04.1

---
xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-0ubuntu1~18.04.1) bionic; 
urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 29 May 2019 13:19:14 +0300

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Update Released

2019-07-03 Thread Adam Conrad

The verification of the Stable Release Update for llvm-toolchain-8 has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1831498] Update Released

2019-07-03 Thread Adam Conrad

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  radeonsi: GTK elements become invisible in some applications (GIMP,
  LibreOffice)

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Disco:
  Fix Committed

Bug description:
  [impact]

  imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 :

  "I am currently experiencing some issues with GTK elements
  (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.

  I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).

  My hardware is a Ryzen 5 2400G APU with vega graphics."

  [test case]

  test that GIMP/Libreoffice work fine on AMD Vega/Raven

  [regression potential]

  the fix/workaround is already in mesa 19.0.4, shouldn't regress
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1827451] Re: Japanese new era "Reiwa(令和)" support

This bug was fixed in the package libreoffice-l10n -
1:6.0.7-0ubuntu0.18.04.7

---
libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.7) bionic; urgency=medium

  * debian/patches/cpdmgr-check-dbus-desc.diff (LP: #1798074):
- Only create CPDManager if D-Bus descriptions present.
- Fixes LibreOffice startup crash when CPD packages installed.

libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.6) bionic; urgency=medium

  [ Ikuya Awashiro ]
  * debian/patches/new-japanese-era-name.patch (LP: #1827451):
Add new Japanse era name "Reiwa" support which taken from upstream:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=cacbb0faef77ae8462de9ff5c7307a6a2e28b2bb

https://cgit.freedesktop.org/libreoffice/core/commit/?id=597c5d75b8e72d429e096535334eaac7973455ef

  [ Olivier Tilloy ]
  * debian/patches/java.vendor-Ubuntu.patch: update to also recognize
"Private Build" as java.vendor (for custom PPA builds) (LP: #1822839)
  * debian/patches/java.vendor-Ubuntu.patch: also make jvmfwk recognize
"Ubuntu" as java.vendor (LP: #1822839)

  [ Rene Engelhard ]
  * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian"
as java.vendor as that's what is set in openjdk 11 >= 11.0.3+4-2
- see #926009 (closes: #926318) (LP: #1822839)
  * debian/control.gtk3.in:
- make libreoffice-gtk3 recommend gstreamer1.0-gtk3 (LP: #1820062)

 -- Marcus Tomlinson   Fri, 31 May 2019
11:43:00 +0100

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)
   7. Set “Format" to "平成11年12月31日"
   8. Cell should show "令和1年5月1日" (not "平成31年5月1日")

  [Regression Potential]

   * The fix is minor so potential for regression is low.

   * A combination of autopkgtests and manual 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/1827451/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

This bug was fixed in the package llvm-toolchain-8 - 1:8-3~ubuntu18.04.1

---
llvm-toolchain-8 (1:8-3~ubuntu18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

 -- Timo Aaltonen   Wed, 10 Apr 2019 11:46:43 +0300

** Changed in: llvm-toolchain-8 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in OEM Priority Project:
  Confirmed
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-8 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1835220] [NEW] Please support /usr/lib64/sane

Public bug reported:

The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
recognized as a directory for SANE backends. However, some .deb files
with scanner drivers, typically provided by Brother, install files in
/usr/lib64/sane. It would be great if that directory could be supported
too.

This issue has been discussed in bug #1728012, but was broken out from
there to not block another more important change in bionic.

If Debian accepts the proposal in , the
change is a SRU candidate to bionic at first hand.

** Affects: sane-backends (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: sane-backends (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #931297
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931297

** Also affects: sane-backends (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931297
   Importance: Unknown
   Status: Unknown

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane. It would be great if that directory could be
  supported too.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  If Debian accepts the proposal in ,
  the change is a SRU candidate to bionic at first hand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1825717] Re: hplip issue during hp-setup - stuck at plugin install

2019-07-03 Thread Till Kamppeter

** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  hplip issue during hp-setup - stuck at plugin install

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Kubuntu 19.04 
  Installed hplip from repositories, available version is 3.19.1+dfsg0-1

  When I start setup with hp-setup, this happens:
  1. I am asked connection type. I select network ethernet
  2. My printer is detected. I select it and hit next
  3. I am told about the proprietary plugin to download. I confirm, accept 
download. I enter my user's password. I get a confirmation that the plugin is 
correctly Installed.
  4. On next screen, I get a warning and cannot continue installation. I am 
told this printer needs a proprietary plugin to work correctly. After this I am 
stuck in a loop between points 3 and 4. I also tried to start hp-setup from 
super user on command line. but no way around this issue.

  What I did next, I manually downloaded hplip-3.19.3.run from HP
  website. Removed version of hplip installed from repositories.
  Installed from manually downloaded package, followed the very same
  steps. Everything worked fine and printer is installed successfully.

  I hope this information is useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1825717/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-03 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405]

[Desktop-packages] [Bug 1833231] Re: cups ftbfs in eoan (amd64 only)

2019-07-03 Thread Till Kamppeter

Is this still relevant?

According to

https://launchpad.net/ubuntu/+source/cups/2.2.10-6ubuntu1

the CUPS 2.2.10-6ubuntu1 package has built on all platforms.

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

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

Title:
  cups ftbfs in eoan (amd64 only)

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups ftbfs in eoan (amd64 only) in a test rebuild:

  https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan-
  amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz

  E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin".
  PASS: 8 warning messages.
  PASS: 0 notice messages.
  PASS: 760 info messages.
  PASS: 24065 debug messages.
  PASS: 25573 debug2 messages.

  Copied log file "access_log-2019-06-14-buildd" to test directory.
  Copied log file "debug_log-2019-06-14-buildd" to test directory.
  Copied log file "error_log-2019-06-14-buildd" to test directory.
  Copied log file "page_log-2019-06-14-buildd" to test directory.
  Copied report file "cups-str-2019-06-14-buildd.html" to test directory.

  1 tests failed.
  make[2]: *** [Makefile:257: check] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:17: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1834052] Re: autopkgtest failures: Chromium-Related in Tests

2019-07-03 Thread Olivier Tilloy

And I can reproduce the test failure in a qemu VM.

Interesting observations: running the chromium snap once ("snap run chromium 
--headless" or "chromium --version" or "chromium-browser --version") after 
installation and before running the tests make them pass. Deleting 
~/snap/chromium after that makes the tests fail again.
Alternatively, specifying 
chrome_options.binary_location="/snap/chromium/current/command-chromium.wrapper"
 also makes the tests pass, without a prior run of the chromium snap.

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

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in kopano-webapp package in Ubuntu:
  In Progress

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  --
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+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 1835210] [NEW] An unresolvable problem occurred while calculating the upgrade.

2019-07-03 Thread Matthew Steven Porath

Public bug reported:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

oem1@oem1-ThinkPad-T430:~$ ubuntu-bug ubuntu-release-upgrader-core
Gtk-Message: 06:49:17.732: GtkDialog mapped without a transient parent. This is 
discouraged.
comm: /var/log/dmesg: No such file or directory
oem1@oem1-ThinkPad-T430:~$ 
(/usr/lib/firefox/firefox:13444): dconf-WARNING **: 06:53:48.085: Unable to 
open /var/lib/snapd/desktop/dconf/profile/user: Permission denied


oem1@oem1-ThinkPad-T430:~$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
oem1@oem1-ThinkPad-T430:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
oem1@oem1-ThinkPad-T430:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  3 07:14:49 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-06-09 (23 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to bionic on 2019-07-03 (0 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  An unresolvable problem occurred while calculating the upgrade.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Could not calculate the upgrade

  An unresolvable problem occurred while calculating the upgrade.

   If none of this applies, then please report this bug using the
  command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If you
  want to investigate this yourself the log files in '/var/log/dist-
  upgrade' will contain details about the upgrade. Specifically, look at
  'main.log' and 'apt.log'.

  oem1@oem1-ThinkPad-T430:~$ ubuntu-bug ubuntu-release-upgrader-core
  Gtk-Message: 06:49:17.732: GtkDialog mapped without a transient parent. This 
is discouraged.
  comm: /var/log/dmesg: No such file or directory
  oem1@oem1-ThinkPad-T430:~$ 
  (/usr/lib/firefox/firefox:13444): dconf-WARNING **: 06:53:48.085: Unable to 
open /var/lib/snapd/desktop/dconf/profile/user: Permission denied

  
  oem1@oem1-ThinkPad-T430:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  oem1@oem1-ThinkPad-T430:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  oem1@oem1-ThinkPad-T430:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 07:14:49 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-06-09 (23 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to bionic on 2019-07-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835210/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2019-07-03 Thread toabm

Same issue here. I have a brand new Dell 7300 using Ubuntu 18.04, and
when I use my Asus MB16AC monitor using the USB connection with the
displaylink driver, the mice pointer starts to flicker and move around.
It can be used but it is very annoying. Can't find the cause. On my old
computer, a Toshiba Satellite with Ubuntu 18.04 it worked just
fine:(

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: Use GNOME Flashback (Metacity) session.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.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
  xserver.bootTime: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1826420] Re: Nautilus disk properties shows black circle

2019-07-03 Thread Wolf Rogner

Hi to all,

I used a MacOS icon theme. The issue did occur with Yaru but not with
Ambience.


I switched to macOS after the ongoing issues that reoccured with 19.04. I could 
not bear with it any longer (12 years are a long time).

Sorry to be of no assistance to this and any other issues any longer.

cheers

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

Title:
  Nautilus disk properties shows black circle

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 / Nautilus 3.32.0 stable (?)

  Mounting a disk (which does not show on the desktop may I add here as
  well) and asking for disk properties gives a black circle.

  Expected behaviour: different colours for used and unused parts, maybe
  gray for the unusable meta data.

  Current behaviour: a black disk telling me nothing.

  (I have no idea as to why a perfectly working file manager had to get
  crippled further, but someone managed).

  I do have a custom theme but it happens with the default theme as
  well.

  (Sorry my tone gets harsher every time but I really get tired being an
  alpha tester).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 16:48:33 2019
  InstallationDate: Installed on 2018-04-30 (360 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826420/+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 1835068] Re: When I click to top indicators, I will see freezing animations

Sebastien, thank you for support!

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

Title:
  When I click to top indicators, I will see freezing animations

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:10:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835068/+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 1832946] Re: Icon spring animation performs worse and skips frames if there are windows open

Oh my god. With pure GNOME Shell I have got the video with black screen. It
is bug of this session on any system (I noticed this, when I had used
Debian 10 GNOME). Take a word, animation is terrible too.

ср, 3 июл. 2019 г. в 13:18, Artyom Pozharov :

> Please, take the video. With this conditions pure GNOME session works bad
> too.
>

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

Title:
  Icon spring animation performs worse and skips frames if there are
  windows open

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

Bug description:
  You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 15 18:50:37 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-14 (1 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.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/1832946/+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 1834984] Re: gnome-shell freezes with 100% CPU when closing popup window

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

** This bug is no longer a duplicate of bug 1835033
   gnome-shell frozen and spinning in g_type_check_instance_cast() from 
meta_window_x11_is_focusable() from get_default_focus_window()
** This bug has been marked a duplicate of bug 1834583
   GNOME Shell hangs when closing a Java dialog; hung in (varying functions 
under) meta_stack_get_default_focus_window() from meta_window_x11_focus()

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

Title:
  gnome-shell freezes with 100% CPU when closing popup window

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I run Netbeans 11 (using either openjdk11) and (eg):

  1. Open Tools / Plugins.
  2. Go to Settings.
  3. Click on 'Add'.
  4. Click 'Cancel'.

  then gnome-shell freezes (except for the mouse), apparently
  indefinitely (I have left it for 30+ minutes.)

  I can login as another user via CTRL-ALT-F1 and kill the frozen
  session using loginctl. Sometimes this kills gnome-shell completely
  and I have to power cycle; other times I can switch back to the login
  with CTRL-ALT-F1 and continue.

  This also usually happens when I close any other popup windows in
  Netbeans.

  I have tried making the popup windows modal and non-modal, but it
  makes no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  Uname: Linux 5.2.0-050200rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  Date: Tue Jul  2 11:34:29 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834984/+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 1835033] Re: gnome-shell frozen and spinning in g_type_check_instance_cast() from meta_window_x11_is_focusable() from get_default_focus_window()

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

** This bug has been marked a duplicate of bug 1834583
   GNOME Shell hangs when closing a Java dialog; hung in (varying functions 
under) meta_stack_get_default_focus_window() from meta_window_x11_focus()

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

Title:
  gnome-shell frozen and spinning in g_type_check_instance_cast() from
  meta_window_x11_is_focusable() from get_default_focus_window()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is a dump I created by killing a gnome-shell process that had
  frozen after trying to close a Java popup window; see also
  https://bugs.launchpad.net/bugs/1834984.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  Uname: Linux 5.2.0-050200rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:24:07 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-07-01 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835033/+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 1834583] Re: GNOME Shell hangs when closing a Java dialog; hung in g_private_get() from thread_memory_from_self() from g_slice_free_chain_with_offset() from g_list_free() from

Generalized to show the same infinite loop can occur with varying stack
traces, depending on when you snapshot/coredump it. This is apparently a
result of the new loop in:

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

** Summary changed:

- GNOME Shell hangs when closing a Java dialog; hung in g_private_get() from 
thread_memory_from_self() from g_slice_free_chain_with_offset() from 
g_list_free() from stack_do_window_deletions() from stack_ensure_sorted() from 
get_default_focus_window()
+ GNOME Shell hangs when closing a Java dialog; hung in g_private_get() from 
thread_memory_from_self() from g_slice_free_chain_with_offset() from 
g_list_free() from stack_do_window_deletions() from stack_ensure_sorted() from 
get_default_focus_window() from meta_stack_get_default_focus_window() from 
meta_window_x11_focus()

** Summary changed:

- GNOME Shell hangs when closing a Java dialog; hung in g_private_get() from 
thread_memory_from_self() from g_slice_free_chain_with_offset() from 
g_list_free() from stack_do_window_deletions() from stack_ensure_sorted() from 
get_default_focus_window() from meta_stack_get_default_focus_window() from 
meta_window_x11_focus()
+ GNOME Shell hangs when closing a Java dialog; hung in (varying functions 
under) meta_stack_get_default_focus_window() from meta_window_x11_focus()

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

Title:
  GNOME Shell hangs when closing a Java dialog; hung in (varying
  functions under) meta_stack_get_default_focus_window() from
  meta_window_x11_focus()

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Pretty much as summary :)

  On my eaon system, closing any dialog in CLion (a Java program, which
  might be relevant) results in GNOME Shell hanging. I believe this to
  be a recent (in the last week or so, maybe?) regression.

  ProblemType: Hang
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 28 17:27:00 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/usr/bin/fish
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
   g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1834583/+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 1832946] Re: Icon spring animation performs worse and skips frames if there are windows open

Please, take the video. With this conditions pure GNOME session works bad
too.


** Attachment added: "simplescreenrecorder-2019-07-03_13.12.21.mkv"
   
https://bugs.launchpad.net/bugs/1832946/+attachment/5274836/+files/simplescreenrecorder-2019-07-03_13.12.21.mkv

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

Title:
  Icon spring animation performs worse and skips frames if there are
  windows open

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

Bug description:
  You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 15 18:50:37 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-14 (1 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.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/1832946/+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 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

Please, take it.

ср, 3 июл. 2019 г. в 11:50, Sebastien Bacher :

> Can you rename it with ascii naming?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1834967
>
> Title:
>   Activities overview doesn't fit the whole window in when shrinking
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
>   Uname: Linux 5.0.0-17-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jul  1 20:38:43 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-07-01 (0 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
>   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/1834967/+subscriptions
>


** Attachment added: "Pozharov_Screenshot.png"
   
https://bugs.launchpad.net/bugs/1834967/+attachment/5274835/+files/Pozharov_Screenshot.png

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

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1786344] Re: Default IBus input method ignored in live session

On 2019-07-03 08:31, Ping-Wu wrote:
> I have tried today's daily built iso of 18.04.

Where did you find that ISO?

> I selected simplified Chinese during boot. Still couldn't input
> Chinese.

The new version of gnome-settings-daemon is in bionic-proposed. Only
when it has reached bionic-updates (in 7+ days) it will be taken into
account when building 18.04 ISOs.

On 2019-07-03 08:49, Ping-Wu wrote:
> However, the ability to input Chinese characters was activated only
> after I clicked on the third option "汉语（智能拼音）“。 For a Chinese
> user, this extra step should not be necessary.
>
> Also as shown in the attached screenshot, the first (top) two
> entries are confusing and have no function. Should be removed.

Without having a firm opinion on that, I can confirm the behavior. It's
similar for Japanese as mentioned in bug #1796722.

If that behavior is considered non-desirable, I'd suggest that you file
a separate Ubiquity bug about it.

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Bionic:
Fix Committed

Bug description:
[Impact]

If you

* start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

* wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

* select a language which requires an input method for typing

* click the "Try Ubuntu" button

The proposed fix should ensure that an IBus method is always available
in "live sessions" in languages which are prepared for it.

[Test Case]

1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
not included among your available input sources.

2. Generate the Chinese locale:

sudo locale-gen zh_CN.UTF-8

3. Add to ~/.profile this line:

export LC_CTYPE=zh_CN.UTF-8

4. Remove the gnome-settings-daemon stamp file:

rm ~/.local/share/gnome-settings-daemon/input-sources-converted

5. Log out and log in again.

=> Find that the "Intelligent Pinyin" method was not added (since the
sources already in the list prevented it from being added).

6. Install gnome-settings-daemon from bionic-proposed.

7. Repeat step 4 and 5.

=> Find that the "Intelligent Pinyin" method was added.

[Regression Potential]

The proposed upload includes a small change which specifically
addresses the issue as described above. I find that the risk for
adverse side effects is low.

[Original description]

Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

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

[Desktop-packages] [Bug 1505774] Re: Feature request: Display each network adapter in network history graph

2019-07-03 Thread Max Waterman

I agree with this.

I almost always use a VPN, and it seems to me like 'Network History' is
adding together the bandwidth for all interfaces. The effect of this is
that it shows double the bandwidth when I am connected to VPN compared
to when I am not connected. I presume it is adding both wlp58s0 and tun0
- or something to that effect.

I am using expressvpn, and speedtest.net to measure.

I would expect 'network history' to use the device associated with tun0.
If anything, I would expect it to show /less/ bandwidth when connected
to VPN (due to the overhead), but certainly not more.

Ideally, I'd like options - to select the interface, take the default
route interface, or show them all, like in this request.

At least, it should be clear about which interface is being measured, or
however else it is being calculated.

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

Title:
Feature request: Display each network adapter in network history graph

Status in gnome-system-monitor package in Ubuntu:
New

Bug description:
The system monitor nicely shows CPU usage for each core and graphs a
line for each one.

It would be nice if the network history graph could do the same for
each network adapter (excluding loopback).

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

[Desktop-packages] [Bug 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)

2019-07-03 Thread Boaz Dodin

Verified on Kubuntu 18.04.2 64bit from the -proposed repository.
Everything, including Gimp and LibreOffice, looks OK.
Yay!

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

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

Title:
  radeonsi: GTK elements become invisible in some applications (GIMP,
  LibreOffice)

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Disco:
  Fix Committed

Bug description:
  [impact]

  imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 :

  "I am currently experiencing some issues with GTK elements
  (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.

  I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).

  My hardware is a Ryzen 5 2400G APU with vega graphics."

  [test case]

  test that GIMP/Libreoffice work fine on AMD Vega/Raven

  [regression potential]

  the fix/workaround is already in mesa 19.0.4, shouldn't regress
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 124406] Re: Keyboard keys get stuck and repeat

2019-07-03 Thread Serge Stroobandt

It is notable to see so much Fujitsu Siemens hardware affected.
I have the same issue with the onboard USB 2.0 of a Fujitsu Siemens P710 E90+ 
Intel i5 3470 desktop computer.

The problem occurs with any of my Varmilo VA88M keyboards, but not with
a Cherry Cymotion G-224. The Varmilo keyboards work perfectly fine on
any other desktop computer I tested but which happened to be not of the
Fujitsu brand.

However, only on the Fujitsu Siemens P710, both Varmilo keyboards would
very often, but not always, stuck and repeat key combinations like
Ctrl+C. This never happened in combination with the Cherry keyboard. So
it seems, reproducibility of this issue depends on both the computer and
the keyboard hardware.

Fed up with this behaviour, I recently installed a NEC USB 2.0 card in
its single conventional PCI slot. The problem never reoccurred over the
span of two weeks now.

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/124406/+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 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-07-03 Thread Iain Lane

Sorry, I messed up the bionic upload. Another one should be coming
shortly.

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Bionic:
  Fix Committed
Status in gnome-desktop3 source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false.

  [ Fix ]

  mutter provides a more reliable API to get the "type" of a connector
  (output). The fix switches gnome-desktop to use this API instead of
  looking at the output's name - which can be anything apparently.

  (This drops a visible symbol, but it was only one which you could have
  used if you included "libgnome-desktop/gnome-rr-private.h", which is
  not shipped in the -dev package.)

  [ QA ]

  If you have an affected system - an NVIDIA-using laptop which doesn't
  sleep if the lid is closed: install the update, and check if the
  laptop does now sleep.

  [ Regression potential ]

  Changes the heuristic-based scheme for detecting if a display is
  "built-in" to a method based on the reported connector type. There's a
  low chance that this could be wrong for some machines which were right
  previously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+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 1835068] Re: When I click to top indicators, I will see freezing animations

2019-07-03 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => 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/1835068

Title:
  When I click to top indicators, I will see freezing animations

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:10:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835068/+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 1731318] Please test proposed package

2019-07-03 Thread Andy Whitcroft

Hello Jeremy, or anyone else affected,

Accepted gnome-desktop3 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.28.2-0ubuntu1.5 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 gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1731318

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Bionic:
  Fix Committed
Status in gnome-desktop3 source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false.

  [ Fix ]

  mutter provides a more reliable API to get the "type" of a connector
  (output). The fix switches gnome-desktop to use this API instead of
  looking at the output's name - which can be anything apparently.

  (This drops a visible symbol, but it was only one which you could have
  used if you included "libgnome-desktop/gnome-rr-private.h", which is
  not shipped in the -dev package.)

  [ QA ]

  If you have an affected system - an NVIDIA-using laptop which doesn't
  sleep if the lid is closed: install the update, and check if the
  laptop does now sleep.

  [ Regression potential ]

  Changes the heuristic-based scheme for detecting if a display is
  "built-in" to a method based on the reported connector type. There's a
  low chance that this could be wrong for some machines which were right
  previously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+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 1835076] Re: No open button after installing .deb package

** Tags added: rls-ee-incoming

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

Title:
  No open button after installing .deb package

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Double click on a .deb package
  2. Software opens up
  3. Click 'Install' button
  4. After installation, there is no 'Open' button that is normally there when 
installing other software

  Tested on Xubuntu 19.10 daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835076/+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 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

Can you rename it with ascii naming?

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

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1835068] Re: When I click to top indicators, I will see freezing animations

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1423
   Importance: Unknown
   Status: Unknown

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

Title:
  When I click to top indicators, I will see freezing animations

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:10:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835068/+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 1832946] Re: Icon spring animation performs worse and skips frames if there are windows open

Can you try a GNOME session on Ubuntu and see if it has the issue? And
then enable the dock there and see if it makes a difference?

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

Title:
  Icon spring animation performs worse and skips frames if there are
  windows open

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

Bug description:
  You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 15 18:50:37 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-14 (1 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.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/1832946/+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 1835068] Re: When I click to top indicators, I will see freezing animations

The upstream report looks fine, thanks!

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

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

Title:
  When I click to top indicators, I will see freezing animations

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:10:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835068/+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 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

It's normal. Now I have Russian Ubuntu and it named photo as "Снимок экрана
от 2019-07-01 20-31-48" that meant "Screenshot at 2019-07-01 20-31-48".

ср, 3 июл. 2019 г. в 11:10, Daniel van Vugt
:

> No, it's getting a strange name ^^^
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1834967
>
> Title:
>   Activities overview doesn't fit the whole window in when shrinking
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
>   Uname: Linux 5.0.0-17-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jul  1 20:38:43 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-07-01 (0 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
>   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/1834967/+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/1834967

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1835068] Re: When I click to top indicators, I will see freezing animations

Am I right? https://gitlab.gnome.org/GNOME/gnome-shell/issues/1423

вт, 2 июл. 2019 г. в 23:00, Sebastien Bacher :

> Thank you for your bug report, could you report it upstream on
> https://gitlab.gnome.org/GNOME/gnome-shell/issues
>
> ** Changed in: gnome-shell (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835068
>
> Title:
>   When I click to top indicators, I will see freezing animations
>
> Status in gnome-shell package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
>   Uname: Linux 5.0.0-17-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jul  2 17:10:00 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-07-01 (0 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
>   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/1835068/+subscriptions
>


** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1423
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1423

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

Title:
  When I click to top indicators, I will see freezing animations

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Details here (video): https://photos.app.goo.gl/ct368UvcyAC2h7N96

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 17:10:00 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835068/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

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

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

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

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

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e
  InstallationDate: Installed on 2011-10-07 (2765 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  IwConfig:
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  Package: pulseaudio 1:8.0-0ubuntu3.10
  PackageArchitecture: amd64
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth 
usbcore.autosuspend=-1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-146-generic N/A
   linux-backports-modules-4.4.0-146-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags: xenial third-party-packages xenial
  Uname: Linux 4.4.0-146-generic x86_64
  UpgradeStatus:

[Desktop-packages] [Bug 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

No, it's getting a strange name ^^^

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

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1424201]

Yes, this bug affects me.

ср, 3 июл. 2019 г. в 05:54, Robert Mader <1424...@bugs.launchpad.net>:

> Although this bug is only about decoding support, I'd like to leave a note
> about the rendering: AFAIK rendering without any slow copies requires
> DMABUF support, so processes can share resources on the GPU.
> For the Wayland backend this about to land, see bug 1552590, quote:
>
> > Wayland dmabuf surface are located in GPU and can be attached as
> EGLImage or wl_buffer. It allows direct rendering to GPU and share the
> HW buffer across processes.
>
> Also see bug 1010527
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1832816).
> https://bugs.launchpad.net/bugs/1424201
>
> Title:
>   Web browsers lacking hardware-accelerated video decoding
>
> Status in Chromium Browser:
>   Unknown
> Status in Mozilla Firefox:
>   Confirmed
> Status in chromium-browser package in Ubuntu:
>   Confirmed
> Status in firefox package in Ubuntu:
>   Confirmed
> Status in chromium-browser package in CentOS:
>   Unknown
>
> Bug description:
>   The chromium team has done a great job to totally disable hardware
>   decoding on Linux.
>
>   Even ignoring the GPU blacklist does not enable GPU decoding.
>
>   How ever the patch is quite simple and it's already working using this
>   PPA ( using libVA ) :
>
>   https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev
>
>   the corresponding patch is here :
>
>   http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
>   browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff
>
>   that would be great if we could have this patch indefault Ubuntu
>   chromium build, this situation is really sad right now, google use
>   linux to make chromeOS so chromebook are really good at playing videos
>   but GNU/Linux chromium is slow at doing it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions
>

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

  https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-07-03 Thread Tomasz Grabarczyk

Hello, thank You for reply,
I can try with new compilation during weekend,
but as my machine is quite old can I try with one of the older 
/lighter/  LTS desktop (or would it be nonsense  in case of this issue)?
I.e Lubuntu 16.04 or Xubuntu 16.04 ?

Best Regards
Tomasz Grabarczyk

On 7/3/19 7:41 AM, Kai-Heng Feng wrote:
> Sorry for the late reply.
>
> Have you tried latest latest Ubuntu ISO?
> http://cdimages.ubuntu.com/daily-live/current/
>

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e
  InstallationDate: Installed on 2011-10-07 (2765 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  IwConfig:
   lono wireless extensions.

   lxcbr0no wireless extensions.

   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  Package: pulseaudio 1:8.0-0ubuntu3.10
  PackageArchitecture: amd64
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth 
usbcore.autosuspend=-1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic

Re: [Desktop-packages] [Bug 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

All for you, my friend;)

ср, 3 июл. 2019 г., 6:00 Daniel van Vugt
:

> Please try attaching that file again with a simpler file name that web
> browsers can handle :)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1834967
>
> Title:
>   Activities overview doesn't fit the whole window in when shrinking
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
>   Uname: Linux 5.0.0-17-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jul  1 20:38:43 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-07-01 (0 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
>   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/1834967/+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/1834967

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

Do you see it now?


** Attachment added: 
"=?UTF-8?B?0KHQvdC40LzQvtC6INGN0LrRgNCw0L3QsCDQvtGCIDIwMTktMDctMDEgMjAtMzEtNDgucG5n?="
   
https://bugs.launchpad.net/bugs/1834967/+attachment/5274816/+files/%3D%3FUTF-8%3FB%3F0KHQvdC40LzQvtC6INGN0LrRgNCw0L3QsCDQvtGCIDIwMTktMDctMDEgMjAtMzEtNDgucG5n%3F%3D

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

Title:
  Activities overview doesn't fit the whole window in when shrinking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1834967/+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 1835043] Re: Ubuntu Dock sticks if I will enter the text in the search line

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

I totally agree with you. I have same problem.

ср, 3 июл. 2019 г. в 06:00, Daniel van Vugt
:

> *** This bug is a duplicate of bug 1832317 ***
> https://bugs.launchpad.net/bugs/1832317
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1832317, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** Tags added: performance
>
> ** This bug has been marked a duplicate of bug 1832317
>A quick type in the Gnome 3 search sticks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835043
>
> Title:
>   Ubuntu Dock sticks if I will enter the text in the search line
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in the video: https://photos.app.goo.gl/4aWGw7dbR95iqZ796
>   P.S.: Sorry, I don't know the method how to load video to Launchpad.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
>   Uname: Linux 5.0.0-17-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jul  2 13:51:11 2019
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2019-07-01 (0 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
>   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/1835043/+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/1835043

Title:
  Ubuntu Dock sticks if I will enter the text in the search line

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in the video: https://photos.app.goo.gl/4aWGw7dbR95iqZ796
  P.S.: Sorry, I don't know the method how to load video to Launchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  2 13:51:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  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/1835043/+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 1834583] Re: GNOME Shell hangs when closing a Java dialog; hung in g_private_get() from thread_memory_from_self() from g_slice_free_chain_with_offset() from g_list_free() from