[Desktop-packages] [Bug 1747881] Re: mouse scroll not working

[Launchpad Bug Tracker]

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

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

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

Title:
  mouse scroll not working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using Kinzu V3 Optical mouse on my ubuntu 16.04.3 LTS (Xenial
  Xerus).

  Mouse scroll is not working.

  The mouse scroll works with my Windows 10 computer but not on my
  ubuntu laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Wed Feb  7 18:01:16 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated 
Graphics [1462:115a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
950M] [1462:115a]
  InstallationDate: Installed on 2017-08-07 (183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7925d32a-375f-4667-94c5-dc44c01247aa ro acpi_osi=! "acpi_osi=Windows 
2009" quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.109
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.109:bd10/27/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb  7 09:33:45 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1747881/+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 1838919] Re: Slow and lost keyboard and mouse events

[Brian Burch]

I didn't see any problems logging on with gnome on xorg, or starting the
first terminal session.

However, as soon as I started the second terminal, the GTK2/GTK3 error
messages poured out. Opening a new tab on the same window does not
generate the messages.

This sounds like your gnome bug report - it doesn't look like a widget,
or an application, but something more fundamental.

I wonder why my system even has the i386 packages installed - were they
pulled in by an application (such as wine) which isn't installed on my
laptop? What is the best way to locate the culprit - I now know it isn't
Chrome, thunderbird, nautilus or netbeans. It's hard to believe gnome-
terminal is the root cause.

** Attachment added: "journalctl with xorg when starting a second terminal 
session"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282548/+files/2019-08-15-xorg-gnome-second-terminal

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

Title:
  Slow and lost keyboard and mouse events

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

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.

  ProblemType: Bug
  DistroRelease: 

Re: [Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events

[Brian Burch]

On 14/8/19 8:22 pm, Traumflug wrote:
> Installed packages don't matter if their content isn't in use. It does
> matter whether you run an X11 or a Wayland session.
> 
> To switch between both, log out to get to the login screen. There is a
> gears icon right above the password entry field, click on it. This
> should open a menu allowing to choose between "Ubuntu on Xorg" and
> "Ubuntu on Wayland". Having this choice done, log in, you'll be in the
> selected type of session.

I had forgotten the gear wheel.. the last time I used it was when unity 
came out as the new default and I preferred Gnome Classic. Thanks for 
reminding me.

> Basically, all applications work in both session types, but there are a
> number of smaller visual distinctions. For example, Firefox draws its
> menu inside the window bar on Wayland, while it draws the menu under the
> window bar on X11. Also, on X11 there's a process "Xorg" running, while
> on Wayland there's a process "XWayland" (or similar).

The default on the desktop system was "ubuntu", so I changed to "Gnome 
on Xorg". The presentation details are different (obviously) but don't 
bother me. However, I get exactly the same errors logged and slow input 
events:-

Aug 15 07:21:43 schizo gnome-control-c[8320]: GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded.
   GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:43 schizo gnome-control-c[8320]: Not loading module 
"atk-bridge": The functionality is provided by GTK natively. Please try 
to not load it.
Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so 
cannot be loaded.
   GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module 
"canberra-gtk-module"
Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so 
cannot be loaded.
   GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module 
"canberra-gtk-module"

I will try again but this time only start a terminal session. I realise 
there is a lot of processes running to support a single graphical user 
session, but I'll keep Chrome and Thunderbird out of the variables.

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

Title:
  Slow and lost keyboard and mouse events

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

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Timo Aaltonen]

and attach the edid there

** No longer affects: xorg-server (Ubuntu)

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

Title:
  drm fails to accept edid version 2.4

Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Timo Aaltonen]

if current drm-intel-next mainline build or 5.3rc doesn't work, then
this bug should be filed upstream at bugs.freedesktop.org, DRI:
drm/intel

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

Title:
  drm fails to accept edid version 2.4

Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  

[Desktop-packages] [Bug 1840185] [NEW] simple-scan app closes with a big delay

[Artyom Pozharov]

Public bug reported:

When I touch closing button I will wait for a while for exiting from this 
program. There are details in my video.
Information from console:
ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
(simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: simple-scan 3.33.90-0ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 14 22:45:14 2019
InstallationDate: Installed on 2019-08-14 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Webcam
 Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
 Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 250 G6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.52
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832E
dmi.board.vendor: HP
dmi.board.version: 26.35
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 250 G6 Notebook PC
dmi.product.sku: 3DN65ES#ACB
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "simplescreenrecorder-2019-08-14_22.44.31.mkv"
   
https://bugs.launchpad.net/bugs/1840185/+attachment/5282530/+files/simplescreenrecorder-2019-08-14_22.44.31.mkv

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

Title:
  simple-scan app closes with a big delay

Status in simple-scan package in Ubuntu:
  New

Bug description:
  When I touch closing button I will wait for a while for exiting from this 
program. There are details in my video.
  Information from console:
  ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
  (simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: simple-scan 3.33.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 22:45:14 2019
  InstallationDate: Installed on 2019-08-14 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Webcam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 3DN65ES#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1840185/+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 1797222] Re: Update to 2.13.1

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/fontconfig/2.13.1-2ubuntu1

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

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

Title:
  Update to 2.13.1

Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  Updating is not risk free and there is no reason to do that now,
  that's for next cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1797222/+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 1821533] Re: drm fails to accept edid version 2.4

[Jiri Krticka]

I had the same problem and a new Fedora solved this for me. On the other
hand, I am experiencing some problems with wifi 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/1821533

Title:
  drm fails to accept edid version 2.4

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: 

[Desktop-packages] [Bug 1830748] Re: Pressing scrollbar makes it sticky

[klfyt]

Maybe related  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839610

:-)

(this looks serious bug ... is it that one which can add astronomically
idle battery power!?  O_o  :-))

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

Title:
  Pressing scrollbar makes it sticky

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  
  Pressing scrollbar in any situation makes it sticky.
  Restart does not help.  >:]
  The only workaround is to delete image cache and
  then restart the browser.

  This is a nice bug in sense that then you fix it
  browser becomes really smooth.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1830748/+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 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)

[Christopher M. Penalver]

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

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 1827945] Re: Se cancela la instalación si cierro Snap store

[Olivier Tilloy]

** Description changed:

+ [description translated to English]
+ 
+ The snap store cannot install applications if the snap store window is
+ closed, please correct this problem so that if I close the window by
+ mistake, the installation of an application is not cancelled.
+ 
+ 
+ [original description in Spanish]
+ 
  La tienda de snaps no puede instalar aplicaciones sí se cierra la
  ventana de la tienda de snap, por favor corrijan este problema para que
  si por error cierro la ventana no se cancele la instalación de una
  aplicacion

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

Title:
  Se cancela la instalación si cierro Snap store

Status in gnome-software package in Ubuntu:
  New

Bug description:
  [description translated to English]

  The snap store cannot install applications if the snap store window is
  closed, please correct this problem so that if I close the window by
  mistake, the installation of an application is not cancelled.

  
  [original description in Spanish]

  La tienda de snaps no puede instalar aplicaciones sí se cierra la
  ventana de la tienda de snap, por favor corrijan este problema para
  que si por error cierro la ventana no se cancele la instalación de una
  aplicacion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1827945/+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 1827945] Re: Se cancela la instalación si cierro Snap store

[Sergio Schvezov]

** Project changed: snapcraft => gnome-software (Ubuntu)

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

Title:
  Se cancela la instalación si cierro Snap store

Status in gnome-software package in Ubuntu:
  New

Bug description:
  [description translated to English]

  The snap store cannot install applications if the snap store window is
  closed, please correct this problem so that if I close the window by
  mistake, the installation of an application is not cancelled.

  
  [original description in Spanish]

  La tienda de snaps no puede instalar aplicaciones sí se cierra la
  ventana de la tienda de snap, por favor corrijan este problema para
  que si por error cierro la ventana no se cancele la instalación de una
  aplicacion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1827945/+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 1840146] [NEW] Don't update to 5.1.8 or newer

[Sebastien Bacher]

Public bug reported:

It's only in Debian experimental and they recommend not updating it, see
https://salsa.debian.org/debian/giflib/commit/fa219f750

** Affects: giflib (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-blocked

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

Title:
  Don't update to 5.1.8 or newer

Status in giflib package in Ubuntu:
  Triaged

Bug description:
  It's only in Debian experimental and they recommend not updating it,
  see https://salsa.debian.org/debian/giflib/commit/fa219f750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1840146/+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 1827945] [NEW] Se cancela la instalación si cierro Snap store

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

La tienda de snaps no puede instalar aplicaciones sí se cierra la
ventana de la tienda de snap, por favor corrijan este problema para que
si por error cierro la ventana no se cancele la instalación de una
aplicacion

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

-- 
Se cancela la instalación si cierro Snap store
https://bugs.launchpad.net/bugs/1827945
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 1799974] Re: [MIR] gupnp

[Chris Coulson]

This one could do with a quick review from the security team.

** Changed in: gupnp (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] gupnp

Status in gupnp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries

  * Security

  There is an old CVE recorded/fixed
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is used during build

  * Dependendies

  The package uses standard desktop libraries that are already in main

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 4.2, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+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 1839610] Re: Skipping previous view doesn't let performance degrade

[klfyt]

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

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

** No longer affects: nautilus

** Project changed: xfwm4 => ubuntu

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

Title:
  Skipping previous view doesn't let performance degrade

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in nautilus package in Fedora:
  Unknown

Bug description:
  
  Something is wrong with previous view
  killing performance and responsiveness, etc.
  The only obvious fix seems to be to skip it.

  :))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1839610/+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 1838919] Re: Slow and lost keyboard and mouse events

[Traumflug]

Installed packages don't matter if their content isn't in use. It does
matter whether you run an X11 or a Wayland session.

To switch between both, log out to get to the login screen. There is a
gears icon right above the password entry field, click on it. This
should open a menu allowing to choose between "Ubuntu on Xorg" and
"Ubuntu on Wayland". Having this choice done, log in, you'll be in the
selected type of session.

Basically, all applications work in both session types, but there are a
number of smaller visual distinctions. For example, Firefox draws its
menu inside the window bar on Wayland, while it draws the menu under the
window bar on X11. Also, on X11 there's a process "Xorg" running, while
on Wayland there's a process "XWayland" (or similar).

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

Title:
  Slow and lost keyboard and mouse events

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

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic 

[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable

[Lasse Kliemann]

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

I confirm the jumping problem. It seems to be a related to gnome
terminal. Using kitty or deepin terminal, I can have a program writing
text to the terminal continuously and not experience any jumps.

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

Title:
  universal access zoom unusable

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

Bug description:
  
  Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 
point type without magnification at normal reading distance and can barely read 
the universal access "large text" from a distance of about 2.5 inches from a 
26inch monitor at 1360x768.   So he really needs magnification and a lot more 
than the 2x default I used here for testing.   We do not live in the same town 
so providing additional details would be slow.

  Turned on zoom from the universal access button on top panel.
  Default settings were used including Zoom = 2.0, screen part = full

  Several areas are corrupted.  These zoom and scroll separately from
  the rest of the screen and in a way that severely impairs use as
  portions may not ever be visible.   Portions of these subwindows
  cannot be used because you have to move the mouse off them to be able
  see them so you can either see or click but not both.

  These areas are:
- The top panel
- The left panel (launcher)  (intermittently)
- pull down menus, particularly the universal access pull down from the top 
panel

  
  Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

  These problems persisted with all the other zoom modes.   One mode,
  however, created new bugs.  With "magnifier extends outside of
  screen", you lose the ability to see the top and left panels at all;
  you can pan over where they would be but they are not drawn.   Can't
  open the pulldown menu since there is no icon, so who knows how it
  would be rendered.

  These bugs made it very difficult to get screenshots, especially with
  the defective screenshot program gnome-screenshot which ships with
  system.   Also, the bug-reporting program did not permitted attaching
  additional screenshots once spectacle was installed.

  Ubuntu 18.04, fresh install, only a few added packages (ham radio
  related, chrome).  Not using wayland, though a wayland session runs
  concurrently with X11 even though no one has logged in with wayland.

  Another problem in making the bug report is the irresponsible practice
  of failing to identify the software being used.   The accessability
  man in circle menu does not have a heading to tell you what program is
  run for the accessability menu or any of the functions thus invoked.
  Nor does the settings.  And there is no tooltip, popup, or about menu
  item to convey this information to the user.   And running a diff on
  ps doesn't show any new processes started when zoom is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 00:04:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1163]
  InstallationDate: Installed on 2018-05-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0M858N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 

[Desktop-packages] [Bug 1033259] Re: If the user tries to open a 'Recent file' that no longer exists, LO does not offer to delete it.

[Paul White]

Reporter no longer uses Launchpad and with no one else saying they are
affected by this issue I'll close the Papercuts task too.

** Changed in: hundredpapercuts
   Status: Triaged => Won't Fix

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

Title:
  If the user tries to open a 'Recent file' that no longer exists, LO
  does not offer to delete it.

Status in LibreOffice:
  Unknown
Status in One Hundred Papercuts:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  If the user creates a file with LibreOffice and then moves/deletes it,
  the next time they try to open it from the 'Recent files' list they
  will receive a warning that it no longer exists, but no offer to
  remove it from the list.

  This should change so that they get that offer, since it will mean the
  list becomes populated with broken links that they can't do anything
  about.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Sun Aug  5 19:19:58 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-06-26 (40 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1033259/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Timo Aaltonen]

Or do a rough bisect using mainline builds of the kernel:

https://kernel.ubuntu.com/~kernel-ppa/mainline/

using 5.1, 5.2, 5.3rc first.

Install linux-image-unsigned-..-generic and linux-modules-...-generic
and then select it from the boot menu

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

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

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1839610] Re: Skipping previous view doesn't let performance degrade

[klfyt]

** Summary changed:

- If you travel BACK directly it kills visible scrolling performance
+ Skipping previous view doesn't let performance degrade

** Description changed:

  
- If you travel directly to location there you have been
- with BACK command (alt left) for example then
- scrolling seems to get worse. This is fixable
- if you revisit recent files in a new window (ctrl n)
- and close it (ctrl w).
- 
- BACK? > open recent files in a new window and close it
+ Something is wrong with previous view
+ killing performance and responsiveness, etc.
+ The only obvious fix seems to be to skip it.
  
  :))

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

Title:
  Skipping previous view doesn't let performance degrade

Status in nautilus package in Ubuntu:
  New
Status in nautilus package in Fedora:
  Unknown

Bug description:
  
  Something is wrong with previous view
  killing performance and responsiveness, etc.
  The only obvious fix seems to be to skip it.

  :))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839610/+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 1840127] [NEW] Update to 0.15.0 but not now

[Sebastien Bacher]

Public bug reported:

The new version is in Debian experimental only and it's a bit late in
the cycle/we have no real need for it, marking as 'to not update' for
now

** Affects: liborcus (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-skip-0.15.0

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

Title:
  Update to 0.15.0 but not now

Status in liborcus package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian experimental only and it's a bit late in
  the cycle/we have no real need for it, marking as 'to not update' for
  now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liborcus/+bug/1840127/+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 1684280] Re: Running espeak with mbrola voices results in error

[Michael Noack]

This is actually a bug in the mbrola package.

Download the test file alice.pho at https://github.com/numediart/MBROLA-
voices/tree/master/data/us1/TEST and try to create a wav file using:

root@terminal:~/mbrola-test# mbrola /usr/share/mbrola/us1/us1 alice.pho test.wav
*** Error in `mbrola': double free or corruption (out): 0x08f9c9e0 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67257)[0xb752a257]
/lib/i386-linux-gnu/libc.so.6(+0x6d577)[0xb7530577]
/lib/i386-linux-gnu/libc.so.6(+0x6dd31)[0xb7530d31]
/lib/i386-linux-gnu/libc.so.6(_IO_wsetb+0x69)[0xb7524fc9]
/lib/i386-linux-gnu/libc.so.6(+0x6baf2)[0xb752eaf2]
/lib/i386-linux-gnu/libc.so.6(+0x2e91a)[0xb74f191a]
/lib/i386-linux-gnu/libc.so.6(+0x2e9cf)[0xb74f19cf]
mbrola(free+0x60)[0x8048c0c]
=== Memory map: 
08048000-0805 r-xp  08:02 1188309/usr/bin/mbrola
0805-08051000 rwxp 7000 08:02 1188309/usr/bin/mbrola
08f6e000-08fac000 rwxp  00:00 0  [heap]
b730-b7321000 rwxp  00:00 0
b7321000-b740 ---p  00:00 0
b749-b74ac000 r-xp  08:02 4983464
/lib/i386-linux-gnu/libgcc_s.so.1
b74ac000-b74ad000 rwxp 0001b000 08:02 4983464
/lib/i386-linux-gnu/libgcc_s.so.1
b74c2000-b74c3000 rwxp  00:00 0
b74c3000-b7672000 r-xp  08:02 4983469
/lib/i386-linux-gnu/libc-2.23.so
b7672000-b7673000 ---p 001af000 08:02 4983469
/lib/i386-linux-gnu/libc-2.23.so
b7673000-b7675000 r-xp 001af000 08:02 4983469
/lib/i386-linux-gnu/libc-2.23.so
b7675000-b7676000 rwxp 001b1000 08:02 4983469
/lib/i386-linux-gnu/libc-2.23.so
b7676000-b7679000 rwxp  00:00 0
b7679000-b76cc000 r-xp  08:02 4983398
/lib/i386-linux-gnu/libm-2.23.so
b76cc000-b76cd000 r-xp 00052000 08:02 4983398
/lib/i386-linux-gnu/libm-2.23.so
b76cd000-b76ce000 rwxp 00053000 08:02 4983398
/lib/i386-linux-gnu/libm-2.23.so
b76e2000-b76e5000 rwxp  00:00 0
b76e5000-b76e7000 r--p  00:00 0  [vvar]
b76e7000-b76e8000 r-xp  00:00 0  [vdso]
b76e8000-b770a000 r-xp  08:02 4983282/lib/i386-linux-gnu/ld-2.23.so
b770a000-b770b000 rwxp  00:00 0
b770b000-b770c000 r-xp 00022000 08:02 4983282/lib/i386-linux-gnu/ld-2.23.so
b770c000-b770d000 rwxp 00023000 08:02 4983282/lib/i386-linux-gnu/ld-2.23.so
bfc83000-bfca4000 rwxp  00:00 0  [stack]
Aborted (core dumped)

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

Title:
  Running espeak with mbrola voices results in error

Status in espeak package in Ubuntu:
  Confirmed

Bug description:
  1. RELEASE

  amy@ThinkPad-T510:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2. PACKAGE INFO

  amy@ThinkPad-T510:~$ apt-cache policy espeak
  espeak:
Installed: 1.48.04+dfsg-2
Candidate: 1.48.04+dfsg-2
Version table:
   *** 1.48.04+dfsg-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola
  mbrola:
Installed: 3.01h+1-3
Candidate: 3.01h+1-3
Version table:
   *** 3.01h+1-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us1
  mbrola-us1:
Installed: 0.3-2
Candidate: 0.3-2
Version table:
   *** 0.3-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us2
  mbrola-us2:
Installed: 0.1-2
Candidate: 0.1-2
Version table:
   *** 0.1-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us3
  mbrola-us3:
Installed: 0.1-1
Candidate: 0.1-1
Version table:
   *** 0.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  3. EXPECTED

  When running `espeak -v mb-us3 "Hello world"`, expected espeak to
  speak "Hello world" using designated mbrola voice without error.

  4. ACTUAL

  When running `espeak -v mb-us3 "Hello world"`, espeak speaks "Hello
  world" using designated mbrola voice, but terminal reports memory leak
  stacktrace. See below:

  
  amy@ThinkPad-T510:/usr/share/mbrola/voices$ espeak -v mb-us3 "Hello world"
  *** Error in `mbrola': free(): invalid pointer: 0x09472da0 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67377)[0xf753b377]
  

[Desktop-packages] [Bug 1684280] Re: Running espeak with mbrola voices results in error

[Michael Noack]

When cloning mbrola source and building it with gcc the result works
just fine.

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

Title:
  Running espeak with mbrola voices results in error

Status in espeak package in Ubuntu:
  Confirmed

Bug description:
  1. RELEASE

  amy@ThinkPad-T510:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2. PACKAGE INFO

  amy@ThinkPad-T510:~$ apt-cache policy espeak
  espeak:
Installed: 1.48.04+dfsg-2
Candidate: 1.48.04+dfsg-2
Version table:
   *** 1.48.04+dfsg-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola
  mbrola:
Installed: 3.01h+1-3
Candidate: 3.01h+1-3
Version table:
   *** 3.01h+1-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us1
  mbrola-us1:
Installed: 0.3-2
Candidate: 0.3-2
Version table:
   *** 0.3-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us2
  mbrola-us2:
Installed: 0.1-2
Candidate: 0.1-2
Version table:
   *** 0.1-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us3
  mbrola-us3:
Installed: 0.1-1
Candidate: 0.1-1
Version table:
   *** 0.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  3. EXPECTED

  When running `espeak -v mb-us3 "Hello world"`, expected espeak to
  speak "Hello world" using designated mbrola voice without error.

  4. ACTUAL

  When running `espeak -v mb-us3 "Hello world"`, espeak speaks "Hello
  world" using designated mbrola voice, but terminal reports memory leak
  stacktrace. See below:

  
  amy@ThinkPad-T510:/usr/share/mbrola/voices$ espeak -v mb-us3 "Hello world"
  *** Error in `mbrola': free(): invalid pointer: 0x09472da0 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67377)[0xf753b377]
  /lib/i386-linux-gnu/libc.so.6(+0x6d2f7)[0xf75412f7]
  /lib/i386-linux-gnu/libc.so.6(+0x6dbb1)[0xf7541bb1]
  /lib/i386-linux-gnu/libc.so.6(_IO_wsetb+0x69)[0xf75360e9]
  /lib/i386-linux-gnu/libc.so.6(+0x6bc02)[0xf753fc02]
  /lib/i386-linux-gnu/libc.so.6(+0x2e93a)[0xf750293a]
  /lib/i386-linux-gnu/libc.so.6(+0x2e9ef)[0xf75029ef]
  mbrola(free+0x60)[0x8048c0c]
  === Memory map: 
  08048000-0805 r-xp  08:01 23465356   
/usr/bin/mbrola
  0805-08051000 rwxp 7000 08:01 23465356   
/usr/bin/mbrola
  09437000-09479000 rwxp  00:00 0  
[heap]
  f730-f7321000 rwxp  00:00 0 
  f7321000-f740 ---p  00:00 0 
  f74d3000-f74d4000 rwxp  00:00 0 
  f74d4000-f7683000 r-xp  08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7683000-f7684000 ---p 001af000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7684000-f7686000 r-xp 001af000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7686000-f7687000 rwxp 001b1000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7687000-f768a000 rwxp  00:00 0 
  f768a000-f76dd000 r-xp  08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76dd000-f76de000 r-xp 00052000 08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76de000-f76df000 rwxp 00053000 08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76e9000-f7705000 r-xp  08:01 28319113   
/lib/i386-linux-gnu/libgcc_s.so.1
  f7705000-f7706000 rwxp 0001b000 08:01 28319113   
/lib/i386-linux-gnu/libgcc_s.so.1
  f7706000-f7709000 rwxp  00:00 0 
  f7709000-f770b000 r--p  00:00 0  
[vvar]
  f770b000-f770c000 r-xp  00:00 0  
[vdso]
  f770c000-f772e000 r-xp  08:01 28321698   
/lib/i386-linux-gnu/ld-2.23.so
  f772e000-f772f000 rwxp  00:00 0 
  f772f000-f773 r-xp 00022000 08:01 28321698   
/lib/i386-linux-gnu/ld-2.23.so
  f773-f7731000 rwxp 00023000 08:01 28321698

[Desktop-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Hui Wang]

addressed the #29, change No to Low.


** Description changed:

  SRU Document:
  
  [Impact]
  
  The Lenovo P520 machine has dual analogue codecs, so there are two sinks
  and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear microphone,
  and the rear microphone always shows up in the gnome-sound-setting, When
  we plug a microphone to front audio jack, there are two input devices:
  rear mic and front mic in the gnome-sound-setting, and suppose users
  select the the front mic to record sound via audio app like arecord, the
  front mic will be bond the arecord, after the front mic is unplugged,
  there is only one rear mic left in the gnome-sound-setting, but the
  binding will not be changed, the arecrod still bind to front mic, under
  this situation if users record sound via arecord, they will find they
  can't record any sound from any other input devices even they are listed
  in the gnome-sound-setting. This problem also happens to output devices
  too.
  
  [Test Case]
  
  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from rear
  mic now. After I plug the front mic back, the arecord still record from
  front mic. Also did the similar test for output devices, it worked as
  expected too.
  
  [Regression Potential]
  
- No, Just make a simple check when creating new streams
+ Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.
  
  For the Bionic, This SRU also includes the fix of LP: #1556439, this fix
  is safe and will not introduce any regression too, because it just adds
  a sink-input/source-output state checking, if the sink-input/source-
  output is unlinking or unlinked, it is useless to move it to a new
  sink/source, furthermore it will trigger an assertion that make the
  pulseaudio crash, adding this check can fix this problem (LP: #1556439).
  
  [Other Info]
  
  No more info here

** Description changed:

  SRU Document:
  
  [Impact]
  
  The Lenovo P520 machine has dual analogue codecs, so there are two sinks
  and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear microphone,
  and the rear microphone always shows up in the gnome-sound-setting, When
  we plug a microphone to front audio jack, there are two input devices:
  rear mic and front mic in the gnome-sound-setting, and suppose users
  select the the front mic to record sound via audio app like arecord, the
  front mic will be bond the arecord, after the front mic is unplugged,
  there is only one rear mic left in the gnome-sound-setting, but the
  binding will not be changed, the arecrod still bind to front mic, under
  this situation if users record sound via arecord, they will find they
  can't record any sound from any other input devices even they are listed
  in the gnome-sound-setting. This problem also happens to output devices
  too.
  
  [Test Case]
  
  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from rear
  mic now. After I plug the front mic back, the arecord still record from
  front mic. Also did the similar test for output devices, it worked as
  expected too.
  
  [Regression Potential]
  
  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.
  
  For the Bionic, This SRU also includes the fix of LP: #1556439, this fix
- is safe and will not introduce any regression too, because it just adds
- a sink-input/source-output state checking, if the sink-input/source-
- output is unlinking or unlinked, it is useless to move it to a new
- sink/source, furthermore it will trigger an assertion that make the
- pulseaudio crash, adding this check can fix this problem (LP: #1556439).
+ is safe and is very low possible to introduce any regression too,
+ because it just adds a sink-input/source-output state checking, if the
+ sink-input/source-output is unlinking or unlinked, it is useless to move
+ it to a new sink/source, furthermore it will trigger an assertion that
+ make the pulseaudio crash, adding this check can fix this problem (LP:
+ #1556439).
  
  [Other Info]
  
  No more info here

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio 

[Desktop-packages] [Bug 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)

[Marcus Tomlinson]

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

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Daniel van Vugt]

"Regression Potential" also shouldn't start with "No".

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and will not introduce any regression too, because it just
  adds a sink-input/source-output state checking, if the sink-input
  /source-output is unlinking or unlinked, it is useless to move it to a
  new sink/source, furthermore it will trigger an assertion that make
  the pulseaudio crash, adding this check can fix this problem (LP:
  #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Hui Wang]

"Regression Potential" is updated with adding the 1556439 part in it.


** Description changed:

  SRU Document:
  
  [Impact]
  
  The Lenovo P520 machine has dual analogue codecs, so there are two sinks
  and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear microphone,
  and the rear microphone always shows up in the gnome-sound-setting, When
  we plug a microphone to front audio jack, there are two input devices:
  rear mic and front mic in the gnome-sound-setting, and suppose users
  select the the front mic to record sound via audio app like arecord, the
  front mic will be bond the arecord, after the front mic is unplugged,
  there is only one rear mic left in the gnome-sound-setting, but the
  binding will not be changed, the arecrod still bind to front mic, under
  this situation if users record sound via arecord, they will find they
  can't record any sound from any other input devices even they are listed
  in the gnome-sound-setting. This problem also happens to output devices
  too.
  
  [Test Case]
  
  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from rear
  mic now. After I plug the front mic back, the arecord still record from
  front mic. Also did the similar test for output devices, it worked as
  expected too.
  
  [Regression Potential]
  
  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.
  
+ For the Bionic, This SRU also includes the fix of LP: #1556439, this fix
+ is safe and will not introduce any regression too, because it just adds
+ a sink-input/source-output state checking, if the sink-input/source-
+ output is unlinking or unlinked, it is useless to move it to a new
+ sink/source, furthermore it will trigger an assertion that make the
+ pulseaudio crash, adding this check can fix this problem (LP: #1556439).
+ 
  [Other Info]
  
  No more info here

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  No, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and will not introduce any regression too, because it just
  adds a sink-input/source-output state checking, if the sink-input
  /source-output is unlinking or unlinked, it is useless to move it to a
  new sink/source, furthermore it will trigger an assertion that make
  the pulseaudio crash, adding this check can fix this problem (LP:
  #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Daniel van Vugt]

19.10: http://cdimage.ubuntu.com/daily-live/current/

19.04: http://releases.ubuntu.com/19.04/

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

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

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Daniel van Vugt]

Can someone experiencing this bug please try live booting Ubuntu 19.10
or 19.04, and tell us if the problem is fixed there?

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

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

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym

[Timo Aaltonen]

so libva/intel-vaapi-driver needs fixing in bionic now

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

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

** Also affects: intel-vaapi-driver (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Invalid

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

Title:
  i965_drv_video.so doesn't load any more if a Wayland server is present
  [failed to resolve wl_drm_interface(): /lib/x86_64-linux-
  gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface]

Status in Libva:
  Fix Released
Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in intel-vaapi-driver source package in Bionic:
  New
Status in libva source package in Bionic:
  New
Status in mesa source package in Bionic:
  Invalid

Bug description:
  If a Wayland server is present (anywhere on the system including even
  the gdm3 login screen) then i965_drv_video.so fails to initialize:

  $ vainfo 
  libva info: VA-API version 1.3.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_2
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  $ mpv bbb_sunflower_2160p_60fps_normal.mp4 
  Playing: bbb_sunflower_2160p_60fps_normal.mp4
   (+) Video --vid=1 (*) (h264 3840x2160 60.000fps)
   (+) Audio --aid=1 (*) (mp3 2ch 48000Hz)
   Audio --aid=2 (*) (ac3 6ch 48000Hz)
  File tags:
   Artist: Blender Foundation 2008, Janus Bager Kristensen 2013
   Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net
   Composer: Sacha Goedegebure
   Genre: Animation
   Title: Big Buck Bunny, Sunflower version
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

  Meanwhile, it continues to work after you have logged into a Xorg
  session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: i965-va-driver 2.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  Date: Thu Jan 24 16:54:21 2019
  InstallationDate: Installed on 2018-12-04 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1813131/+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 1835622] Re: Cannot start desktop session with compositor enabled

[k3dar7]

additional test - not help Mesa:
- today bionic-update/main 19.0.8-0ubuntu0~18.04.1
- Padoka Stable (ppa:paulo-miguel-dias/pkppa) 19.1.2-0~b~padoka0

BUT with this Mesa work Compositing enabled without crash:
- Padoka Unstable (ppa:paulo-miguel-dias/mesa) 
19.2~git190724122600.e7e31b1~b~padoka0

all test with today 18.04 Xfce 4.14 packages fro ppa:xubuntu-dev/staging
and Intel GPU...

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

Title:
  Cannot start desktop session with compositor enabled

Status in Xfwm4:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xfwm4 package in Ubuntu:
  Invalid

Bug description:
  I cannot login to the Xfce desktop session anymore. in ~/.xsession-
  errors there's the message:

  xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285:
  intel_miptree_match_image: Assertion `image->TexObject->Target ==
  mt->target' failed.

  Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0.

  I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA
  with xfwm4 4.13.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1772512] Re: Unable to install i386 and amd64 arch at the same time

[Timo Aaltonen]

ugemkow, yavn, please test this on bionic, it's been available for
almost five months now

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

Title:
  Unable to install i386 and amd64 arch at the same time

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

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

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

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1840066] Re: DELL DA300 adaptor's Ethernet port not working after update

[Olivier Tilloy]

Can you please run the following command in a terminal to attach
additional debug information to the bug report?

apport-collect 1840066

Thanks!

** Package changed: firefox (Ubuntu) => network-manager (Ubuntu)

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  DELL DA300 adaptor's Ethernet port not working after update

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  DELL DA300 adapter's Ethernet port stopped working after recent
  update. Whenever the cable is plugged in to the adapter, network
  manager would show the cable connecting icon and immediately drop the
  connection. I am able to get Ethernet connection through the DA300
  with another Ethernet-USBc adapter by plugging the cable to the
  adaptor and use DA300's USBc port though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1840066/+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 1272725] Re: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable

[Paul White]

Closing as fixed in the absence of any recent reports.

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => 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/1272725

Title:
  [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Problem description: 
  In Calc, right-clicking on any cell and then selecting Format Cells often 
produces a dialog box that is unusable as it is almost transparent. Closing and 
re-opening the dialog has no effect. Calc has to be restarted to clear the 
problem.

  Steps to reproduce:
  1. Right click on any Calc cell
  2. Select Format Cell

  Current behavior:
  Dialog is partly transparent or perhaps it would be better to say its 
contents are mostly missing.

  Expected behavior:
  Dialog allows formatting of cell with all contents visible.

  Please note:  This doesn't happen all of the time but has happened
  often enough for me to report this as a bug.

  I'm using Kubuntu 14.04, fully updated with LibreOffice loaded from PPA. The 
previous version, in the Ubuntu archive (4.1.3?) also exhibits this problem. 
KDE version is 4.12.1.
  --- 
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-01-01 (24 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140101)
  Package: libreoffice 1:4.2.0~rc2-0ubuntu1~trusty2 [origin: 
LP-PPA-libreoffice-libreoffice-prereleases]
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Tags: trusty third-party-packages
  Uname: Linux 3.13.0-5-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+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 1838919] Re: Slow and lost keyboard and mouse events

[Brian Burch]

Thank you very much for your suggestion #21, Traumflug. I read the issue
you quoted and to be honest, I was quite disappointed in the responses
so far.

The symptoms sound very similar to those I reported here. I compared the
wayland packages on my desktop (slow or lost mouse and keyboard events)
with those on my laptop (ubuntu studio), which works satisfactorily. I
will attach a file containing the two dpkg lists for comparison.

I really don't understand the wayland architecture, but was happy to use
the recommended workaround when running sudo gui programs such as
gparted.

I notice two differences and wonder whether either of them might account
for the diference between my two systems?

1. The desktop has three i386 old packages not installed on the laptop.
Perhaps I should delete them?

2. The desktop has the xwayland package installed, but the laptop does
not.

What do you think? Is this helpful in tracking down the root cause of
the problem? Is there anything I can do to assist with further
diagnosis, given I have two systems side-by-side for comparison?

** Attachment added: "dpkg list comparison for wayland"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282468/+files/2019-08-14-wayland-packages-compared

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

Title:
  Slow and lost keyboard and mouse events

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

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I 

[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/thunderbird/thunderbird.bionic

** Branch linked: lp:~mozillateam/thunderbird/thunderbird.xenial

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1839637] Re: Display driver missing

[Daniel van Vugt]

No problem. If no further comments are added here in the next 60 days
then the bug will close automatically.

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

Title:
  Display driver missing

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

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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