date:20190426

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

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

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

Title:
  Returned to login screen immediately after login

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Ran updates yesterday. This morning was able to login but after a bit
  I was kicked back to login screen.  Attempts to login return my back
  to the login screen.

  Previously reported this bug
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all.
  However this one is different as I'm not stuck at black screen nor do
  I seem to be able to login after multiple attempts.

  i7 7820x
  msi x299 sli plus
  32GB ram
  ubuntu 18.04
  nvidia 1050 gtx

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 25 10:14:24 2018
  InstallationDate: Installed on 2018-04-10 (44 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=screen-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-14T10:14:30.946183

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

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

[Desktop-packages] [Bug 1773386] Re: Returned to login screen immediately after login

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

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

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

Title:
  Returned to login screen immediately after login

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Ran updates yesterday. This morning was able to login but after a bit
  I was kicked back to login screen.  Attempts to login return my back
  to the login screen.

  Previously reported this bug
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all.
  However this one is different as I'm not stuck at black screen nor do
  I seem to be able to login after multiple attempts.

  i7 7820x
  msi x299 sli plus
  32GB ram
  ubuntu 18.04
  nvidia 1050 gtx

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 25 10:14:24 2018
  InstallationDate: Installed on 2018-04-10 (44 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=screen-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-14T10:14:30.946183

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

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

[Desktop-packages] [Bug 1817393] Re: Unable to view details on top panel

[Expired for gnome-shell-extension-appindicator (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unable to view details on top panel

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Expired

Bug description:
  Unable to view details on the top panel

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

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

[Desktop-packages] [Bug 1817440] Re: System freeze only with Firefox

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

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

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

Title:
  System freeze only with Firefox

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Recently my laptop freeze when Firefox 65.0 is started. However I
  fully suspect it is due some add-ons misbehaving. It seen to run
  smoothly when I disable all the add-ons

  OS: Lubuntu 18.10
  Desktop - Cinnamon
  H/W Acer C720 with (Obuntu-only)
  Bios: SeaBios from Mrchrombox

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Feb 23 15:04:29 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Haswell-ULT Integrated Graphics Controller 
[8086:0a06]
  InstallationDate: Installed on 2019-02-20 (3 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0489:e056 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Peppy
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=b2d004bf-c604-446a-b26c-364f223c9d90 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox:bd11/07/2016:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Feb 23 14:54:03 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.3-0ubuntu0.18.10.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1817216] Re: Xorg freeze

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

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

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Hi just wanted to report in addition I had two webpages open no other 
programs running.
  The webpages were youtube and msn when the page froze - the cursor/mouse did 
not respond and the keyboard was locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

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

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

[Desktop-packages] [Bug 606365]

2019-04-26 Thread Psychonaut

(In reply to Dennis Schridde from comment #14)
> Does the import work when using nmcli (`nmcli connection import type openvpn
> file $FILENAME`)?
> 
> If nmcli works, I would think this is mostly caused by Plasma NM not using
> the NetworkManager OpenVPN code to import configuration files (bug #396530),
> but implements an own buggy version.

I'm now using plasma-nm 5.12.8.  This version has the same behaviour as
described for plasma-nm 5.12.6 in Comment 13: attempting to import an
.ovpn file with inline certificates and keys results in a spurious error
dialog, but the keys and certificates get successfully copied anyway.

I also tried using nmcli.  This seems to work without any problems:

$ nmcli connection import type openvpn file ~/vpn/ukp-vpn.ovpn 
Connection 'ukp-vpn' (c6cbabfe-f117-4af9-aca5-be9e8c88595c) successfully added.

When I open the NetworkManager plasma applet after doing this, I see the
VPN connection listed there, with the keys and certificates copied into
separate files under ~/.cert/nm-openvpn.

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in plasma-nm:
  New
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

2019-04-26 Thread Rafael Lopes Conde dos Reis

I am having the same problem. Could you describe in more details what
you have done to be able to fix it?

-- 
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: xserver-xorg-core N/A
  version.xserv

[Desktop-packages] [Bug 1826617] Re: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同

2019-04-26 Thread ishland

Try to do it with:

-o Dpkg::Options::="--force-overwrite"

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

Title:
  package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的
  '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包
  libtiffxx5:amd64 中的其他实例不同

Status in tiff package in Ubuntu:
  New

Bug description:
  Synaptic cannot install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtiffxx5 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Apr 27 08:27:27 2019
  ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 
libtiffxx5:amd64 中的其他实例不同
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: tiff
  Title: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 
'/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

2019-04-26 Thread Markus Birth

I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've
also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager
still autoconnects just fine after boot. The configuration looks
identical on both machines.

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

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

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

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

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

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1826617] [NEW] package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同

2019-04-26 Thread Tessliu

Public bug reported:

Synaptic cannot install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libtiffxx5 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sat Apr 27 08:27:27 2019
ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 
libtiffxx5:amd64 中的其他实例不同
InstallationDate: Installed on 2019-04-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: tiff
Title: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 
'/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的
  '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包
  libtiffxx5:amd64 中的其他实例不同

Status in tiff package in Ubuntu:
  New

Bug description:
  Synaptic cannot install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtiffxx5 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Apr 27 08:27:27 2019
  ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 
libtiffxx5:amd64 中的其他实例不同
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: tiff
  Title: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 
'/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1818905] Re: Store screenshots to the org.gnome.gnome-screenshot auto-save-directory directory, if defined

2019-04-26 Thread Michael Aaron Murphy

Updating this to state that GNOME has yet to make a decision on how to
approach this, but whatever decision they make will not consist of
sharing an application-specific variable with GDM.

They seem to be hinting that they will create a global variable that
applications can use, but they've yet to make a decisions on where or
how they want it implemented. Still waiting for feedback on the
implementation specifics.

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Store screenshots to the org.gnome.gnome-screenshot auto-save-
  directory directory, if defined

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When the `PrintScrn` key is pressed in GNOME Shell, it takes a
  screenshot and writes it to `$HOME/Pictures`, or otherwise falling
  back to `$HOME` if that directory is not found. The `gnome-screenshot`
  tool does a similar action, but also checks for the existence of the
  `auto-save-directory` gsetting in `org.gnome.gnome-screenshot`. This
  will allow GNOME Shell to also use that key, and store screenshots in
  this location when found.

  ### Implementation Note

  I added a `CowPtr` type to make it possible for the
  `get_screenshot_directory()` function to return a `gchar*` which is
  either owned or borrowed, and to free a value when it is owned.
  `g_get_user_special_dir ()` and `g_get_home_dir ()` return `gchar*`
  values which are owned by GLib, and must not be freed, but
  `g_settings_get_string` is owned, and must be freed.

  Alternatively, I could `g_strdup()` the values to copy them onto the
  heap.

  ### Testing

  1. Before applying the patch, take a screenshot with the PrintScrn key.
  2. A screenshot should now be stored in `$HOME/Pictures`.
  3. Create the new screenshot directory, and set the value for 
gnome-screenshot:
  ```sh
  mkdir $HOME/Screenshots
  gsettings set org.gnome.gnome-screenshot auto-save-directory $HOME/Screenshots
  ```
  4. Take the screenshot again, and notice that it stores in `$HOME/Pictures` 
instead of `$HOME/Screenshots`
  5. Apply the patch, and restart `gnome-shell`, then take the screenshot again
  6. The screenshot should be written in `$HOME/Screenshots` instead of 
`$HOME/Pictures`.
  7. Delete the gsettings value, and try again, to see that it returns to 
storing screenshots in `$HOME/Pictures`
  ```sh
  gsettings reset org.gnome.gnome-screenshot auto-save-directory
  ```

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

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

[Desktop-packages] [Bug 1826616] Re: After resuming from suspend, wallpaper turns to static

2019-04-26 Thread Mike L

** Attachment added: "Static wallpaper"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+attachment/5259404/+files/Screenshot%20from%202019-04-26%2020-16-08.png

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

Title:
  After resuming from suspend, wallpaper turns to static

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As stated in the title of the bug, every time I resume from suspend,
  the wallpaper turns into a static picture. This can be somewhat
  alleviated by switching the wallpaper, but the previous wallpaper is
  unusable until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:15:54 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-11 (166 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago)

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

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

[Desktop-packages] [Bug 1826616] [NEW] After resuming from suspend, wallpaper turns to static

2019-04-26 Thread Mike L

Public bug reported:

As stated in the title of the bug, every time I resume from suspend, the
wallpaper turns into a static picture. This can be somewhat alleviated
by switching the wallpaper, but the previous wallpaper is unusable until
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 20:15:54 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-11-11 (166 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  After resuming from suspend, wallpaper turns to static

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As stated in the title of the bug, every time I resume from suspend,
  the wallpaper turns into a static picture. This can be somewhat
  alleviated by switching the wallpaper, but the previous wallpaper is
  unusable until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:15:54 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-11 (166 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-17 (9 days ago)

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-04-26 Thread Cubic PPA

I do not have this issue:

1. I am not using Workspace Grid.

2. I also removed the Ubuntu version of Dash to Dock

$ apt --yes --quiet autoremove --purge gnome-shell-extension-ubuntu-dock
Then, I downloaded and installed...

https://extensions.gnome.org/extension/307/dash-to-dock/

Since Dash to Dock options were not available in Dconf, I set the
options in...

.../dash-to-d...@micxgx.gmail.com/schemas/org.gnome.shell.extensions
.dash-to-dock.gschema.xml

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824738] Re: gvfsd-admin crashed with signal 5

** Changed in: gvfs
   Status: Unknown => New

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

Title:
  gvfsd-admin crashed with signal 5

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm afraid I have no further information on what may have caused this
  to occur.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 03:19:01 2019
  ExecutablePath: /usr/lib/gvfs/gvfsd-admin
  ProcCmdline: /usr/lib/gvfs/gvfsd-admin --help
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ()
   ()
   __libc_start_main (main=0x55cf5bb5f8d0, argc=2, argv=0x7fff172c4978, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff172c4968) at ../csu/libc-start.c:310
   ()
  Title: gvfsd-admin crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo users vboxusers

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

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

[Desktop-packages] [Bug 1824738] Re: gvfsd-admin crashed with signal 5

2019-04-26 Thread Tom Reynolds

Thanks Sebastien, I've filed it at Gnome's Gitlab and added the bug
tracker.

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #395
   https://gitlab.gnome.org/GNOME/gvfs/issues/395

** Also affects: gvfs via
   https://gitlab.gnome.org/GNOME/gvfs/issues/395
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfsd-admin crashed with signal 5

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm afraid I have no further information on what may have caused this
  to occur.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 03:19:01 2019
  ExecutablePath: /usr/lib/gvfs/gvfsd-admin
  ProcCmdline: /usr/lib/gvfs/gvfsd-admin --help
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ()
   ()
   __libc_start_main (main=0x55cf5bb5f8d0, argc=2, argv=0x7fff172c4978, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff172c4968) at ../csu/libc-start.c:310
   ()
  Title: gvfsd-admin crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo users vboxusers

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

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

[Desktop-packages] [Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade

Thanks! My searches before filing the bug suggested that the log
messages were symptoms, but I was unable to find any guideline on how to
diagnose further.

I've uninstalled gsconnect (both the Gnome extension, and the
accompanying Chrome extension), and fully rebooted. The locks still
occur.

Some extra information:

1. In trying to pin down the cause, I…
   - Uninstalled zeitgeist
   - Disabled tracker: 
https://gist.github.com/vancluever/d34b41eb77e6d077887c#non-invasive-disable-cheat-sheet

Neither of these made a difference.

2. I also identified what seems to be a separate issue:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1826604

3. Finally, I notice differences between the bug in the default 'Ubuntu' 
session and the 'Ubuntu on Wayland' session. The initial bug report, above, was 
from 'Ubuntu on Wayland'. In the default 'Ubuntu' session:
- The display and keyboard input lock, but the mouse cursor can still be moved.
- The 'Key repeat discarded' and 'libinput error' log messages do not occur.

Other symptoms (e.g. CPU usage spike for gnome-shell) are the same.

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

Title:
  Input locks frequently/high CPU usage after 18.10->19.04 upgrade

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from 18.10 to 19.04.

  What I expected to happen: same performance as before.

  What happens instead:
  - I experience frequent locks of input lasting from 0.5–5 seconds, during 
which:
    - The mouse cannot be moved or clicked.
    - Any pressed key is repeated for the duration of the lock.

  Various events seem to trigger the locks:
  - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s).
  - Changing tabs in Google Chrome (locks for 0.5 s).
  - Changing tabs in the Atom editor (locks for 1–5 s).
  - Typing in gedit with no other applications running (locks for ~0.5s).

  Accompanying symptoms:
  - CPU usage for gnome-shell is high:
    - Always around 20%
    - Appears to spike to 100% for longer locks (from eyeballing htop open in 
gnome-terminal)

  - The following appear in 'journalctl -f':

  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat 
discarded, Wayland compositor doesn't seem to be processing events fast enough!
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: last_user_time (169670562) is greater than comparison timestamp 
(169670067).  This most likely represents a buggy client sending inaccurate 
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: 0x181 appears to be one of the offending windows with a timestamp 
of 169670562.  Working around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: W1369 appears to be one of the offending windows with a timestamp of 
1798201456.  Working around...

  - The following also appear:

  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce: offset negative (-313ms)
  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce short: offset negative (-326ms)

  $ lsb_release -rd && apt-cache policy gnome-shell
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell:
    Installed: 3.32.0+git20190410-1ubuntu1
    Candidate: 3.32.0+git20190410-1ubuntu1
    Version table:
   *** 3.32.0+git20190410-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 15:52:32 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (559 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago)

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

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

[Desktop-packages] [Bug 1826606] [NEW] mouse sometimes only works after system reboot

2019-04-26 Thread andrew

Public bug reported:

mouse lights up but not move or allow right or left click . nothing
works till ubuntu operating system  is rebooted. then mouse works .

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,imgpng,move,resize,mousepoll,animation,vpswitch,snap,wall,fade,workarounds,unitymtgrabhandles,gnomecompat,session,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 16:41:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
InstallationDate: Installed on 2017-10-19 (553 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
MachineType: Dell Inc. Dell System Inspiron N7110
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-48-generic 
root=UUID=998af81c-28d1-48b8-b917-ce456c8c0b00 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0YH79Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn0YH79Y:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System Inspiron N7110
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Tue Oct 23 14:13:48 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5952 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  mouse sometimes only works after system reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  mouse lights up but not move or allow right or left click . nothing
  works till ubuntu operating system  is rebooted. then mouse works .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,place,grid,imgpng,move,resize,mousepoll,animation,vpswitch,snap,wall,fade,workarounds,unitymtgrabhandles,gnomecompat,session,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 16:41:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
  InstallationDate: Installed on 2017-10-19 (553 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Dell System Inspiron N7110
  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-48-generic 
root=UUID=998af81c-28d1-48b8-b917-ce456c8c0b00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.

[Desktop-packages] [Bug 1587550] Re: package gconf2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 failed to install/upgrade: dependency problems -
  leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Ran "update-manager -d" thinking this was an upgrade to 16.04, but I
  guess it's an upgrade to "testing".  Result is a window saying:

  Could not install 'gconf2'

  The upgrade will continue but the 'gconf2' package may not be in a
  working state. Please consider submitting a bug report about it.

  dependency problems - leaving triggers unprocessed

  [Close]

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

Confirming that this is still happening in later releases.  I just
marked these as duplicates, but we can unmark them if the same
underlying issue isn't at play here (as suggested in the above comment).

bug #1778342
bug #1791529
bug #1805051

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1778342] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Sat Jun 23 08:30:05 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-24 (699 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2018-06-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1826602] Re: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug is no longer a duplicate of bug 1805051
   package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Crash happened on upgrade from 18.04 to 18.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gconf2 3.2.6-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Fri Apr 26 14:27:27 2019
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to cosmic on 2019-04-26 (0 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2017-10-30T13:06:38.618550

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

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

[Desktop-packages] [Bug 1805051] Re: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  There seem to be fairly similar bugs already reported, but in my case,
  I was upgrading from 18.04 to 18.10 and it seems that my version is
  just slightly newer. Assuming it's related to the other similar bugs,
  then this is still an issue.

  $ lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  apt-cache policy gconf2   

 130 ↵
  gconf2:
Installed: 3.2.6-4.1ubuntu2
Candidate: 3.2.6-4.1ubuntu2
Version table:
   *** 3.2.6-4.1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status

  Now that's it's up everything seems to be fine, but I had to hit
  "close" on the error dialog many many times.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gconf2 3.2.6-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sun Nov 25 13:31:28 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-02 (1149 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to cosmic on 2018-11-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1826604] [NEW] Extension causes saving files to desktop to be slow

Public bug reported:

To reproduce:
1. Create a text file (foo.txt) on the desktop and open in gedit.
2. Type a few lines in the file and save it.

Expected: the file saves more or less instantly.

Observed:
- The file takes several seconds to save.
- The following lines appear in the journal:

Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: fileItem 
is null
 
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17
  
 
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89


Notes:
- Repeating #1 and #2 with a file that is in another folder (i.e., not on the 
desktop), the file saves instantly, and the log messages do not appear.
- This might be a duplicate/alternate description of #1816205.
- Discovered while trying to diagnose #1826219.


$ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons 
Description:Ubuntu 19.04
Release:19.04
gnome-shell-extension-desktop-icons:
  Installed: 19.01.1-1
  Candidate: 19.01.1-1
  Version table:
 *** 19.01.1-1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-desktop-icons 19.01.1-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 22:24:04 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-11 (562 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Extension causes saving files to desktop to be slow

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

Bug description:
  To reproduce:
  1. Create a text file (foo.txt) on the desktop and open in gedit.
  2. Type a few lines in the file and save it.

  Expected: the file saves more or less instantly.

  Observed:
  - The file takes several seconds to save.
  - The following lines appear in the journal:

  Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: 
fileItem is null
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17
  
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89

  
  Notes:
  - Repeating #1 and #2 with a file that is in another folder (i.e., not on the 
desktop), the file saves instantly, and the log messages do not appear.
  - This might be a duplicate/alternate description of #1816205.
  - Discovered while trying to diagnose #1826219.

  
  $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons 
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell-extension-desktop-icons:
Installed: 19.01.1-1
Candidate: 19.01.1-1
Version table:
   *** 19.01.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 22:24:04 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (562 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1791529] Re: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I was upgrading Lubuntu...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic i686
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  Date: Sun Sep  9 12:44:00 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-08-22 (18 days ago)
  InstallationMedia: Linux Lite 3.8 - Release i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2018-09-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90

2019-04-26 Thread DooMMasteR

als also still experiencing this behaviour

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

Title:
  Media, brightness and volume keys don't work with GNOME 3.15.90

Status in GNOME Settings Daemon:
  Unknown
Status in GNOME Shell:
  Invalid
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using
  gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness
  and volume keys from my laptop keyboard stop to work after working
  some time in a session or after suspending the computer.

  If I restart my computer media keys work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  3 23:07:33 2015
  InstallationDate: Installed on 2014-10-22 (132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking

2019-04-26 Thread DooMMasteR

on 19.04 the issue still exists.
gsd-media-keys seems to be the problem after all...

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

Title:
  gsd-media-keys fails to adjust the screen brightness after unlocking

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Whne my machine sat for some time (laptop, screen off) it is not possible to 
change the screen brighness of the display for some time after unlocking.
  After 3-5 minutes it will eventually just work again.

  journalctl logs the following

  är 30 01:17:02 dbus-daemon[975]: [system] Activating via systemd: service 
name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.212' 
(uid=1000 pid=14229 comm="/usr/bin/gnome-shell " label="uncon
  Mär 30 01:17:02 systemd[1]: Starting Fingerprint Authentication Daemon...
  Mär 30 01:17:02 dbus-daemon[975]: [system] Successfully activated service 
'net.reactivated.Fprint'
  Mär 30 01:17:02 systemd[1]: Started Fingerprint Authentication Daemon.
  Mär 30 01:17:06 gdm-password][605]: gkr-pam: unlocked login keyring
  Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Activating 
via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=808 
comm="/usr/
  Mär 30 01:17:45 systemd[14145]: Starting GNOME Terminal Server...
  Mär 30 01:17:45 gnome-terminal-server[813]: Display does not support 
owner-change; copy/paste will be broken!
  Mär 30 01:17:45 dbus-daemon[14209]: [session uid=1000 pid=14209] Successfully 
activated service 'org.gnome.Terminal'
  Mär 30 01:17:45 systemd[14145]: Started GNOME Terminal Server.
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, 
active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, 
active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/desktop/interface/" (establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" 
(establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/desktop/sound/" (establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/desktop/privacy/" (establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" 
(establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/desktop/a11y/" (establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
  Mär 30 01:17:45 org.gnome.SettingsDaemon.MediaKeys.desktop[14428]: # 
watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
  Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: 
Timeout was reached
  Mär 30 01:17:54 gsd-media-keys[14428]: Failed to set new screen percentage: 
Timeout was reached
  Mär 30 01:17:55 pkexec[845]: pam_unix(polkit-1:session): session opened for 
user root by (uid=1000)
  Mär 30 01:17:55 pkexec[845]: doommaster: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/doommaster] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
93]
  Mär 30 01:17:55 pkexec[851]: pam_unix(polkit-1:session): session opened for 
user root by (uid=1000)
  Mär 30 01:17:55 pkexec[851]: doommaster: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/doommaster] 
[COMMAND=/usr/lib/

[Desktop-packages] [Bug 1805051] Re: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

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

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

Title:
  package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  There seem to be fairly similar bugs already reported, but in my case,
  I was upgrading from 18.04 to 18.10 and it seems that my version is
  just slightly newer. Assuming it's related to the other similar bugs,
  then this is still an issue.

  $ lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  apt-cache policy gconf2   

 130 ↵
  gconf2:
Installed: 3.2.6-4.1ubuntu2
Candidate: 3.2.6-4.1ubuntu2
Version table:
   *** 3.2.6-4.1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status

  Now that's it's up everything seems to be fine, but I had to hit
  "close" on the error dialog many many times.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gconf2 3.2.6-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Sun Nov 25 13:31:28 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-02 (1149 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to cosmic on 2018-11-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1826602] Re: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-04-26 Thread Apport retracing service

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1805051
   package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Crash happened on upgrade from 18.04 to 18.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gconf2 3.2.6-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Fri Apr 26 14:27:27 2019
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to cosmic on 2019-04-26 (0 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2017-10-30T13:06:38.618550

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

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

[Desktop-packages] [Bug 1826602] [NEW] package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

Public bug reported:

Crash happened on upgrade from 18.04 to 18.10.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: gconf2 3.2.6-4.1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Fri Apr 26 14:27:27 2019
ErrorMessage: dependency problems - leaving triggers unprocessed
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.4
SourcePackage: gconf
Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to cosmic on 2019-04-26 (0 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2017-10-30T13:06:38.618550

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


** Tags: amd64 apport-package cosmic

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

Title:
  package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Crash happened on upgrade from 18.04 to 18.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gconf2 3.2.6-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Fri Apr 26 14:27:27 2019
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to cosmic on 2019-04-26 (0 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2017-10-30T13:06:38.618550

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

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

[Desktop-packages] [Bug 1826549] Re: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0

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

Title:
  Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with
  Linux kernel 5.0

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
  wheel does not work any more. My mouse is Microsoft Wireless Optical
  Mouse 2000. The mouse is connected to USB port via wireless receiver
  (Microsoft Wireless Mouse Receiver v1.0).

  
  I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

  The problem is reproducible with xorg and with wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:23:34 2019
  DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2017-09-12 (591 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
   Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z270 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1826549] Re: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0

2019-04-26 Thread Jean

Have the same issue with a Microsoft Corp. Wireless Optical Mouse 3.0

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

Title:
  Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with
  Linux kernel 5.0

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
  wheel does not work any more. My mouse is Microsoft Wireless Optical
  Mouse 2000. The mouse is connected to USB port via wireless receiver
  (Microsoft Wireless Mouse Receiver v1.0).

  
  I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

  The problem is reproducible with xorg and with wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:23:34 2019
  DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2017-09-12 (591 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
   Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z270 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

Oh, and forgot to mention that an external optical usb mouse works just
fine.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade

** Attachment added: "glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+attachment/5259337/+files/glxinfo.txt

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

Title:
  Input locks frequently/high CPU usage after 18.10->19.04 upgrade

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from 18.10 to 19.04.

  What I expected to happen: same performance as before.

  What happens instead:
  - I experience frequent locks of input lasting from 0.5–5 seconds, during 
which:
    - The mouse cannot be moved or clicked.
    - Any pressed key is repeated for the duration of the lock.

  Various events seem to trigger the locks:
  - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s).
  - Changing tabs in Google Chrome (locks for 0.5 s).
  - Changing tabs in the Atom editor (locks for 1–5 s).
  - Typing in gedit with no other applications running (locks for ~0.5s).

  Accompanying symptoms:
  - CPU usage for gnome-shell is high:
    - Always around 20%
    - Appears to spike to 100% for longer locks (from eyeballing htop open in 
gnome-terminal)

  - The following appear in 'journalctl -f':

  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat 
discarded, Wayland compositor doesn't seem to be processing events fast enough!
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: last_user_time (169670562) is greater than comparison timestamp 
(169670067).  This most likely represents a buggy client sending inaccurate 
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: 0x181 appears to be one of the offending windows with a timestamp 
of 169670562.  Working around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: W1369 appears to be one of the offending windows with a timestamp of 
1798201456.  Working around...

  - The following also appear:

  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce: offset negative (-313ms)
  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce short: offset negative (-326ms)

  $ lsb_release -rd && apt-cache policy gnome-shell
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell:
    Installed: 3.32.0+git20190410-1ubuntu1
    Candidate: 3.32.0+git20190410-1ubuntu1
    Version table:
   *** 3.32.0+git20190410-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 15:52:32 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (559 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago)

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

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

[Desktop-packages] [Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade

** Attachment added: "lspci-k.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+attachment/5259336/+files/lspci-k.txt

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

Title:
  Input locks frequently/high CPU usage after 18.10->19.04 upgrade

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from 18.10 to 19.04.

  What I expected to happen: same performance as before.

  What happens instead:
  - I experience frequent locks of input lasting from 0.5–5 seconds, during 
which:
    - The mouse cannot be moved or clicked.
    - Any pressed key is repeated for the duration of the lock.

  Various events seem to trigger the locks:
  - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s).
  - Changing tabs in Google Chrome (locks for 0.5 s).
  - Changing tabs in the Atom editor (locks for 1–5 s).
  - Typing in gedit with no other applications running (locks for ~0.5s).

  Accompanying symptoms:
  - CPU usage for gnome-shell is high:
    - Always around 20%
    - Appears to spike to 100% for longer locks (from eyeballing htop open in 
gnome-terminal)

  - The following appear in 'journalctl -f':

  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat 
discarded, Wayland compositor doesn't seem to be processing events fast enough!
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: last_user_time (169670562) is greater than comparison timestamp 
(169670067).  This most likely represents a buggy client sending inaccurate 
timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: 0x181 appears to be one of the offending windows with a timestamp 
of 169670562.  Working around...
  Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager 
warning: W1369 appears to be one of the offending windows with a timestamp of 
1798201456.  Working around...

  - The following also appear:

  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce: offset negative (-313ms)
  Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: 
client bug: timer event20 debounce short: offset negative (-326ms)

  $ lsb_release -rd && apt-cache policy gnome-shell
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell:
    Installed: 3.32.0+git20190410-1ubuntu1
    Candidate: 3.32.0+git20190410-1ubuntu1
    Version table:
   *** 3.32.0+git20190410-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 15:52:32 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (559 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago)

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

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

Btw adding synaptic_intertouch=0 to the parameters at boot doesn't
change anything.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+attachment/5259335/+files/Xorg.0.log

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

** Attachment added: "devices"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+attachment/5259332/+files/devices

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

** Attachment added: "nvidia-bug-report.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+attachment/5259334/+files/nvidia-bug-report.log

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

** Attachment added: "evtest"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+attachment/5259333/+files/evtest

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1826597] [NEW] Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

Public bug reported:


On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

The same machine has been working fine with ubuntu 16.04 and 18.10. To
be more correct it is still working in 16.04 hwe which I'm dual booting.

If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
replace with noveau drivers it works just fine (by the way there seems
to be no other issues with the nvidia driver as of yet).

I have also the nvidia-driver-390 also suggested in the graphical
software updates tool, to no avail.

I will attach relevant logs. Please let me know if there is more I should 
supply.
And thanks for all your hard (and brilliant) work.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-input-libinput 0.28.2-2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 20:36:18 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
InstallationDate: Installed on 2019-04-26 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20EQS0PQ00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
SourcePackage: xserver-xorg-input-libinput
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET83W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS0PQ00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EQS0PQ00
dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco ubuntu

** Attachment added: "xinput"
   https://bugs.launchpad.net/bugs/1826597/+attachment/5259319/+files/xinput

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNO

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

This bug was fixed in the package ibus - 1.5.19-1ubuntu3

---
ibus (1.5.19-1ubuntu3) eoan; urgency=medium

  * ubuntu-use-distinguishable-abstract-address.patch:
Change the default address of ibus daemon to 'unix:tmpdir=/tmp/ibus'
so it has a mediatable abstract socket path (LP: #1580463)

 -- Gunnar Hjalmarsson   Thu, 25 Apr 2019 19:01:00
+0200

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The p

[Desktop-packages] [Bug 1507676] Re: Nvidia-Prime not switching from intel to nvidia leading to a black screen

2019-04-26 Thread Artyom

** Also affects: nvidia-prime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia-Prime not switching from intel to nvidia leading to a black
  screen

Status in nvidia-prime package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install 15.10 on a laptop that supports optimus nvidia/intel hybrid 
graphics
  2. Install nvidia and nvidia-prime
  3. Open nvidia settings
  4. Switch to nvidia
  5. Log out
  6. Hear the login drums

  EXPECTED:
  I expect to see the lightdm login page

  ACTUAL:
  You are presented with a black page

  TEMP WORKAROUND:
  1. Tap ctrl-alt-f1
  2. login
  3. run sudo prime-select intel
  4. run sudo service lightdm restart
  5. System is back running on the intel stack alone.

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

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

[Desktop-packages] [Bug 1816308] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed() when changing workspace after several minutes of work in one workspace

2019-04-26 Thread Tomas

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

Happens to me also when using Skype or Slack video calls and switching
workspaces. I turned off animations and see how it goes, but it's
definitely a bug. It crashes your Gnome session in worst case or freezes
for a few seconds and start flickering the screen.

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

Title:
gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed()
when changing workspace after several minutes of work in one workspace

Status in gnome-shell package in Ubuntu:
Confirmed

Bug description:
After some recent update, I face the following issue:
Working on a workspace for some time (cannot say how much time), with or
without lots of windows open, the workspace takes 2-3 minutes to recover, shows
a crash dialog and restarts gnome.

In fewer cases, after days of not rebooting, the gnome-shell dies
instead of restarting, killing the session.

I normally click to submit the bug reports, which should be in:

https://errors.ubuntu.com/user/b56fc2894b10f99f5b9629befd4030528cf0fe943fd6d376f53b724791abcc83b582e15ae82346f04a637b2c7be643f2749a1bdec23b9bc4b9d8cd4c4aa1070e

There are both created the /var/lib/whoopsie/whoopsie-id and
/var/crash/_usr_bin_gnome-shell.1000.crash .
The ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash does not work.
Seems like apport-gtk is frozen.

The next updates did not fix it.

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

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

[Desktop-packages] [Bug 1825758] Re: search button does nothing

2019-04-26 Thread Stuardo -StR- Rodríguez

Here the video showing the issue

** Attachment added: "Here the video showing the issue"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825758/+attachment/5259315/+files/gnome-software-issue.mp4

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

Title:
  search button does nothing

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  When I click the search button, nothing happens. If then I go to the
  "Installed" tab, and go back to the "All" tab, and click the search
  button again, the search field is shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 17:16:37 2019
  InstallationDate: Installed on 2019-04-21 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files

2019-04-26 Thread teo1978

How is this importance low???

The Nautilus UI remains unusable while this happens, which may take
several seconds.

Also, when a user sees this happen after deleting some files (which
clearly means Nautilus is "doing something" related to deleting the
files), one can't be sure whether it's safe to go on doing other stuff
(e.g. copying folders or uploading them somewhere) before the flickering
ends, i.e. before nautilus is done doing whatever it's doing. I always
wait just in case. Which again may be several seconds.

This is a huge usability issue.

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

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

Title:
  Left panel flickers like crazy during several seconds after deleting a
  bunch of files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have no idea if there are some requirements to trigger this issue,
  so I don't know whether you'll be able to reproduce it by just
  following my steps.

  Anyway, I can reproduce it 100% of the times:

  1. Open some folder in Nautilus
  2. Select a few files. Make sure you select quite a few
  3. Delete them by pressing the DEL key

  Expected:
  Nothing, a part from the files being deleted and disappearing from the 
displayed folder contents.

  Observed:
  During a few seconds after you hit Delete (I guess the time it takes to move 
the files to Trash and do some associated action, which by the way I don't know 
what it is that can take so long when deleting just a handful of files), the 
items in the list of shortcuts in the left panel (see screenshot) start 
flickering frantically, like crazy. It's pathetic.

  It looks like the item called "Networks", just below "Trash",
  disappears and reappears several times very quickly, causing all the
  items below it to move down and up, hence the flickering.

  Obviously it makes no sense.

  Note: there's nothing wrong to be appreciated in my screenshot, it
  just indicates where the flickering happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 19:24:36 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1797 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files

2019-04-26 Thread teo1978

> This is a huge usability issue.

and until we know exactly what is going on when the flickering happens,
we don't know for sure whether it's more than a  mere usability issue.
So until that's known for sure, this should have importance high or
critical.

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

Title:
  Left panel flickers like crazy during several seconds after deleting a
  bunch of files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have no idea if there are some requirements to trigger this issue,
  so I don't know whether you'll be able to reproduce it by just
  following my steps.

  Anyway, I can reproduce it 100% of the times:

  1. Open some folder in Nautilus
  2. Select a few files. Make sure you select quite a few
  3. Delete them by pressing the DEL key

  Expected:
  Nothing, a part from the files being deleted and disappearing from the 
displayed folder contents.

  Observed:
  During a few seconds after you hit Delete (I guess the time it takes to move 
the files to Trash and do some associated action, which by the way I don't know 
what it is that can take so long when deleting just a handful of files), the 
items in the list of shortcuts in the left panel (see screenshot) start 
flickering frantically, like crazy. It's pathetic.

  It looks like the item called "Networks", just below "Trash",
  disappears and reappears several times very quickly, causing all the
  items below it to move down and up, hence the flickering.

  Obviously it makes no sense.

  Note: there's nothing wrong to be appreciated in my screenshot, it
  just indicates where the flickering happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 19:24:36 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1797 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1826544] Re: media button to disable touchpad not working

2019-04-26 Thread Tim Tisdall

I really have no idea what package to file this against because I don't
know where the disconnect lies nor how to determine that.  Please let me
know what additional information is needed.

** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)

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

Title:
  media button to disable touchpad not working

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I have an ASUS UX305CA laptop and after upgrading to 18.04 I am no
  longer able to disable the touchpad by hitting Fn+F9 .  When I hit
  Fn+F9 it shows the graphic indicating that it's disabling the
  touchpad, but the touchpad continues to work.  I tried using a LiveUSB
  copy of 18.04 and it the button works fine, so there seems to be
  something related to upgrading.  I upgrading from 16.04 where it
  worked fine before.

  I'm not sure which package to file this bug against, sorry.

  Here are some details:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  $ lsmod | grep asus
  asus_nb_wmi28672  0
  asus_wmi   28672  1 asus_nb_wmi
  sparse_keymap  16384  1 asus_wmi
  wmi24576  1 asus_wmi
  video  45056  2 asus_wmi,i915
  asus_wireless  16384  0
  $ dconf read /org/gnome/desktop/peripherals/touchpad/send-events
  'enabled'
   
  I also went through a diff between gsettings on the LiveUSB and my current 
install and nothing stood out to me as being related.  I do have 
`org.gnome.desktop.interface gtk-im-module 'ibus'` which differs from LiveUSB 
which is set to 'gtk-im-context-simple', but I don't know if it's related.

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

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

[Desktop-packages] [Bug 1826544] [NEW] media button to disable touchpad not working

You have been subscribed to a public bug:

I have an ASUS UX305CA laptop and after upgrading to 18.04 I am no
longer able to disable the touchpad by hitting Fn+F9 .  When I hit Fn+F9
it shows the graphic indicating that it's disabling the touchpad, but
the touchpad continues to work.  I tried using a LiveUSB copy of 18.04
and it the button works fine, so there seems to be something related to
upgrading.  I upgrading from 16.04 where it worked fine before.

I'm not sure which package to file this bug against, sorry.

Here are some details:

$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ lsmod | grep asus
asus_nb_wmi28672  0
asus_wmi   28672  1 asus_nb_wmi
sparse_keymap  16384  1 asus_wmi
wmi24576  1 asus_wmi
video  45056  2 asus_wmi,i915
asus_wireless  16384  0
$ dconf read /org/gnome/desktop/peripherals/touchpad/send-events
'enabled'
 
I also went through a diff between gsettings on the LiveUSB and my current 
install and nothing stood out to me as being related.  I do have 
`org.gnome.desktop.interface gtk-im-module 'ibus'` which differs from LiveUSB 
which is set to 'gtk-im-context-simple', but I don't know if it's related.

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


** Tags: bot-comment
-- 
media button to disable touchpad not working
https://bugs.launchpad.net/bugs/1826544
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1826468] Re: [upstream] Libreoffice Calc cannot export PDF to a network drive

Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=124985.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-04-26T15:52:34+00:00 Jarosław Pióro wrote:

Description:
After upgrading from Ubuntu 18.10 to 19.04 Libreoffice lost its ability to 
write to network drives. In my case it's a DAVS system, which I connect to 
using Nautilus. I access the file on the drive with Nautilus, open a file by 
double-clicking it, it opes without problems, I can change it and save it, but 
I cannot export the document as PDF or "Save As" another document at the same 
location. I get one popup window saying: "Error saving the document : Nonexistent file" and after closing it another one opens with "Error 
saving the document : General error. General input/output error".

The problem seems to emerge from time to time, as this example shows:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757

Steps to Reproduce:
1. Map a network drive through Nautilus
2. Access a LibreOffice document on this drive, open it by double-clicking it
3. Try to export the document as PDF to the same location or try to save it 
under another name without changing the location of the file

Actual Results:
one popup window saying: "Error saving the document : 
Nonexistent file" apperars and after closing it another one opens with "Error 
saving the document : General error. General input/output error".

Expected Results:
The software should export a file or write it down under a new name.


Reproducible: Always


User Profile Reset: No


Additional Info:
Version: 6.2.2.2
Build ID: 1:6.2.2-0ubuntu2
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: pl-PL (pl_PL.UTF-8); UI-Language: en-US
Calc: threaded

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826468/comments/6


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => 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/1826468

Title:
  [upstream] Libreoffice Calc cannot export PDF to a network drive

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

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1826468/+subscriptions

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

[Desktop-packages] [Bug 1826586] [NEW] Unable to drag Nautilus tab to new window

2019-04-26 Thread Norbert

Public bug reported:

Steps to reproduce:
1. Install Ubuntu 19.04
2. Open Nautilus (Files) application
3. Open new tab with any way (Ctrl+T, Ctrl+Enter for some folder - does not 
really matter)
4. Try to drag the opened Tab out the current window to create new window from 
this tab

Expected results:
* user is able to drag tab to new window (as in previous 18.10 - see screencast)

Actual results:
* user is unable to drag tab to new window

Note:
first seen on AskUbuntu ( https://askubuntu.com/q/1137967/66509 )

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 19:11:42 2019
GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: apport-bug disco eoan

** Attachment added: "1810.gif"
   https://bugs.launchpad.net/bugs/1826586/+attachment/5259311/+files/1810.gif

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

Title:
  Unable to drag Nautilus tab to new window

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.04
  2. Open Nautilus (Files) application
  3. Open new tab with any way (Ctrl+T, Ctrl+Enter for some folder - does not 
really matter)
  4. Try to drag the opened Tab out the current window to create new window 
from this tab

  Expected results:
  * user is able to drag tab to new window (as in previous 18.10 - see 
screencast)

  Actual results:
  * user is unable to drag tab to new window

  Note:
  first seen on AskUbuntu ( https://askubuntu.com/q/1137967/66509 )

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 19:11:42 2019
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-04-26 Thread Misha Nasledov

This bug has been driving me crazy for a while. I've spent a lot of my
time investigating it. I don't use laptops much, so the primary issue I
run into is that none of my screens go into suspend, so sometimes I'll
find all my screens were on for hours without me realizing it. This
wastes a lot of power and is not good for my screens.

There are definitely certain sites that are more aggressive than others.

HomeDepot.com is one that'll open WebRTC workers that will inhibit PM,
even with the latest Chromium WebRTC PM policy changes.

Facebook may or may not inhibit power management -- it depends on what
is displayed in the tab and (fortunately) whether the tab is in the
foreground or background of the Chrome/Chromium window. However, it
often does not care if you are on a different desktop. Videos and
animated GIFs are two of the major culprits.

Sometimes Google Hangouts on the GMail page decides to launch some
WebRTC stuff and totally inhibit PM as well. The only fix for this is to
just close the tab -- for WebRTC it doesn't seem to matter if it's in
the foreground or not.

I can go on, but it's lame that web developers are so easily able to
screw with our power management. And I guarantee you that this is not
something that is typically tested in web development. I don't believe
Firefox has these issues.

The funny thing is that, years ago, I did wish web browsers inhibited
the screensaver while I was watching videos. Now they've gone way too
far. Without the "Inhibit" applet showing me a red "X", I have no idea
if my screens are going to go to sleep or not. I often just run `xset
dpms force suspend && cinnamon-screensaver-command -l` when walking away
to be safe.

One solution that kind of sucks but works 100% of the time is just to
killall chrome before walking away. You'll have to go through and
restore all your windows, but at least it's something.

Something to simply block an application from inhibiting power
management would be a nice first step. If it were a panel applet or
something, one could easily re-enable power management inhibition for
watching videos.

I think that Chromium needs to do better, but I think that it exposes an
obvious weakness that should be resolved in the GNOME end as well.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object

[Desktop-packages] [Bug 1826468] Re: [upstream] Libreoffice Calc cannot export PDF to a network drive

Thank you Jarosław.

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=124985
   Importance: Unknown
   Status: Unknown

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

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

Title:
  [upstream] Libreoffice Calc cannot export PDF to a network drive

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

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1826468/+subscriptions

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

[Desktop-packages] [Bug 1826468] Re: [upstream] Libreoffice Calc cannot export PDF to a network drive

2019-04-26 Thread Jarosław Pióro

I have reported the bug there, here is the link:

https://bugs.documentfoundation.org/show_bug.cgi?id=124985

** Bug watch added: Document Foundation Bugzilla #124985
   https://bugs.documentfoundation.org/show_bug.cgi?id=124985

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

Title:
  [upstream] Libreoffice Calc cannot export PDF to a network drive

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1812407] Re: Dock resize on hover and on window focus

2019-04-26 Thread Alex Pertu

** Tags added: disco

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

Title:
  Dock resize on hover and on window focus

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

Bug description:
  Dock resize on hover and on window focus.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  gnome-shell-extension-ubuntu-dock:
    Installed: 0.9.1ubuntu18.04.1
    Candidate: 0.9.1ubuntu18.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 16:15:18 2019
  InstallationDate: Installed on 2018-09-17 (123 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium

2019-04-26 Thread Bruno F

Thank José M.

I can confirm the --disable-seccomp-filter-sandbox works on Chromium (version 
73.0.3683.103-0ubuntu1)
on my fresh Lubuntu 19.04 amd64 install.


However, I am wondering if it would be dangerous from a security point of view ?
Does it expose the system or are there other sandboxing mechanism protecting it 
instead of seccomp ?

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)

2019-04-26 Thread Jeremy Soller

You can download the Pop!_OS gnome-shell packages here:

https://launchpad.net/~system76/+archive/ubuntu/pop/+packages

We added the commit that fixed this on top of the current Ubuntu
version. You will probably only need to install these two deb files:

https://launchpad.net/~system76/+archive/ubuntu/pop/+files/gnome-shell-common_3.32.0+git20190410-1ubuntu1pop0~1555607389~19.04~56282e6_all.deb
https://launchpad.net/~system76/+archive/ubuntu/pop/+files/gnome-shell_3.32.0+git20190410-1ubuntu1pop0~1555607389~19.04~56282e6_amd64.deb

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

Title:
  Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not
  the ubuntu-dock)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  From time to time, my chrome icon disappears in gnome shell 3.32,
  leaving only the "open window indicator" below it. It's the first of
  my icons, and this is running a vanilla gnome session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  2 17:44:52 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (383 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago)

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

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

[Desktop-packages] [Bug 1826560] [NEW] [SRU] libreoffice 6.2.3 for disco

Public bug reported:

[Impact]

 * LibreOffice 6.2.3 is in its third bugfix release of the 6.2 line. Version 
6.2.3 is currently in eoan.
   For a list of fixed bugs compared to 6.2.2 see the list of bugs fixed in the 
two release candidates:
 https://wiki.documentfoundation.org/Releases/6.2.3/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/6.2.3/RC2#List_of_fixed_bugs
   (that's a total of 92 bugs)

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

[Test Case]

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

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

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

[Regression Potential]

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

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

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

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

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

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

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

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

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

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

Title:
  [SRU] libreoffice 6.2.3 for disco

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libreoffice source package in Disco:
  New
Status in libreoffice-l10n source package in Disco:
  New

Bug description:
  [Impact]

   * LibreOffice 6.2.3 is in its third bugfix release of the 6.2 line. Version 
6.2.3 is currently in eoan.
     For a list of fixed bugs compared to 6.2.2 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.2.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.2.3/RC2#List_of_fixed_bugs
     (that's a total of 92 bugs)

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium

2019-04-26 Thread rui romo

@Olivier Tilloy: Thank you for your comment and i was not paying attention to 
thread #7. I see this is also happening in other distros,and Kernel might not 
be direct related on this because i had run Fedora 29 lxqt with Kernel 5, and 
things were working well. And also Xubuntu 19.04, except for Nvidia driver has 
strange behaviour and flash on "Chromes", all is working well, but i had 
installation errors, so clean install might clean up things a bit(for my 
experience 2 leaps in distro upgrade might give you some errors). Please ignore 
some of my feedback to this has it is very particular to my installation and 
ignorance :D. Regarding this also and more, i know Flash will be ignored from 
2020 on. I only use it for some Facebook games. Still, on LTS Ubuntu and 
derivates flavours/other distros, it is working well on Chromium and family. 
@José M. : It did not worked for me, but you will still have to start it all 
over from command line every time, right? We will wait for new version. 
TX! Regards to all.

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

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

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

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

** Changed in: ibus
   Status: Unknown => New

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are included above under 'Extended test case'.

  = SRU apparmor =
  [Impact]

[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium

2019-04-26 Thread José M .

It seems to be a bug related to the latest version of glibc. A small
workaround is to add this flag to the command to run Chromium and all
derived browsers (Opera, Vivaldi, etc). It worked for me:

--disable-seccomp-filter-sandbox

In Chrome it doesn't seem to work, we have to wait for a new version.

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1826550] Re: Fractional scaling options do not appear with multiple monitors

** Attachment added: "Screenshot with external monitor connected. Only whole 
number scaling available."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png

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

Title:
  Fractional scaling options do not appear with multiple monitors

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor.

  I have enabled the experimental fractional scaling support.

  When no external monitor is connected, the fractional scaling options
  are displayed as expected. When the external monitor is connected,
  only the old whole number scaling options are displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:32:55 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1826550] [NEW] Fractional scaling options do not appear with multiple monitors

Public bug reported:

Using 19.04 disco with Wayland.

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.

I have enabled the experimental fractional scaling support.

When no external monitor is connected, the fractional scaling options
are displayed as expected. When the external monitor is connected, only
the old whole number scaling options are displayed.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 14:32:55 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-04 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages wayland-session

** Attachment added: "With no external monitor. Fractional scaling options 
shown."
   
https://bugs.launchpad.net/bugs/1826550/+attachment/5259299/+files/Screenshot%20from%202019-04-26%2014-32-37.png

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

Title:
  Fractional scaling options do not appear with multiple monitors

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor.

  I have enabled the experimental fractional scaling support.

  When no external monitor is connected, the fractional scaling options
  are displayed as expected. When the external monitor is connected,
  only the old whole number scaling options are displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:32:55 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1784349] Re: SEGV during startup on Power 8 system

2019-04-26 Thread Paul White

Thanks for confirming. Closing as fixed.

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

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

Title:
  SEGV during startup on Power 8 system

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Trying to start Firefox 61 on Power 8 terminates with the segmentation
  fault below.

  firefox[155767]: unhandled signal 11 at 7402b3100060 nip 090b2d83e9ec 
lr 090b2d83ed1c code 2
  0x0001e96c in arena_t::SplitRun (this=0x7770, 
aRun=0x74a1, aSize=1048576, aLarge=false, aZero=false)
  at 
/build/firefox-aPxmMP/firefox-61.0.1+build1/memory/build/mozjemalloc.cpp

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

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

[Desktop-packages] [Bug 1826549] [NEW] Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0

2019-04-26 Thread Vladimir Kondratyev

Public bug reported:

I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
wheel does not work any more. My mouse is Microsoft Wireless Optical
Mouse 2000. The mouse is connected to USB port via wireless receiver
(Microsoft Wireless Mouse Receiver v1.0).


I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

The problem is reproducible with xorg and with wayland.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 15:23:34 2019
DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
InstallationDate: Installed on 2017-09-12 (591 days ago)
InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
 Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago)
dmi.bios.date: 07/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: Z270 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with
  Linux kernel 5.0

Status in xorg package in Ubuntu:
  New

Bug description:
  I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
  wheel does not work any more. My mouse is Microsoft Wireless Optical
  Mouse 2000. The mouse is connected to USB port via wireless receiver
  (Microsoft Wireless Mouse Receiver v1.0).

  
  I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

  The problem is reproducible with xorg and with wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:23:34 2019
  DistUpgraded: 2019-04-26 14:07:47,232 ERR

[Desktop-packages] [Bug 1826547] [NEW] [Wayland] Display change "Revert Settings" window uses primary screen scaling factor

Public bug reported:

Using 19.04 disco with Wayland.

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.

If I set the primary display to the built-in display but have the
display settings window open on the external screen, then when I change
the scaling factor of the built-in display to e.g. 300% and click Apply,
the "Do you want to keep these settings" confirmation window appears on
the external screen, scaled by 300%. If the external monitor is the
primary display, it is always scaled normally at 100%.

Conversely, if the external monitor is set as the primary display, but
the settings window is on the built-in display, then when I change the
scaling factor of the external monitor to 100%, then this "Do you want
to keep these settings" dialog appears incorrectly scaled at 100%
instead of 200%.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 14:16:23 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-04 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages wayland-session

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

Title:
  [Wayland] Display change "Revert Settings" window uses primary screen
  scaling factor

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Using 19.04 disco with Wayland.

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor. I have the laptop screen set to 200% and the external screen
  set to 100%.

  If I set the primary display to the built-in display but have the
  display settings window open on the external screen, then when I
  change the scaling factor of the built-in display to e.g. 300% and
  click Apply, the "Do you want to keep these settings" confirmation
  window appears on the external screen, scaled by 300%. If the external
  monitor is the primary display, it is always scaled normally at 100%.

  Conversely, if the external monitor is set as the primary display, but
  the settings window is on the built-in display, then when I change the
  scaling factor of the external monitor to 100%, then this "Do you want
  to keep these settings" dialog appears incorrectly scaled at 100%
  instead of 200%.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 14:16:23 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-04 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)

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

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

[Desktop-packages] [Bug 1784349] Re: SEGV during startup on Power 8 system

2019-04-26 Thread Paul Menzel

I tested this yesterday with Ubuntu 18.10, and Firefox did crash
anymore. So this can be tagged as solved. I do not know the first fixed
version though.

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

Title:
  SEGV during startup on Power 8 system

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Trying to start Firefox 61 on Power 8 terminates with the segmentation
  fault below.

  firefox[155767]: unhandled signal 11 at 7402b3100060 nip 090b2d83e9ec 
lr 090b2d83ed1c code 2
  0x0001e96c in arena_t::SplitRun (this=0x7770, 
aRun=0x74a1, aSize=1048576, aLarge=false, aZero=false)
  at 
/build/firefox-aPxmMP/firefox-61.0.1+build1/memory/build/mozjemalloc.cpp

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

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

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2019-04-26 Thread Gunnar Hjalmarsson

** Bug watch added: github.com/ibus/ibus/issues #2095
   https://github.com/ibus/ibus/issues/2095

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2095
   Importance: Unknown
   Status: Unknown

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Unknown
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config

[Desktop-packages] [Bug 1825741] Re: [upstream] Multiple instances of global menu entries

Launchpad has imported 5 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=124391.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-03-28T11:17:28+00:00 Константин wrote:

Description:
We have double menus in GTK3 VCL, if it is used with Unity-style globalmenu - 
vala-panel-appmenu, or with GTK3 Backend on KDE (via 
https://github.com/KDE/plasma-workspace/tree/master/gmenu-dbusmenu-proxy)

Package version: 6.2.2-2
Distribution: ArchLinux.

Steps to Reproduce:
1. Install and configure vala-panel-appmenu 
(https://gitlab.com/vala-panel-project/vala-panel-appmenu)
2. Open any LibreOffice app
3. Bug happens

Actual Results:
We see double menus, as in screenshots in bug on vala-panel-appmenu GitLab 
(https://gitlab.com/vala-panel-project/vala-panel-appmenu/issues/286)

Expected Results:
We should see only single menu, no double menus.


Reproducible: Always


User Profile Reset: Yes


Additional Info:
Related to:

1. https://bugs.documentfoundation.org/show_bug.cgi?id=123416 - similar
(now seems fixed) bug for KDE on 6.2.0 and Qt VCL

2. https://bugs.documentfoundation.org/show_bug.cgi?id=122619 - this bug
calls to remove menu export in GTK3 at all, because it is rarely needed.
I am strongly against this decision.

3. https://gitlab.com/vala-panel-project/vala-panel-appmenu/issues/286 -
Issue on vala-panel-appmenu end, confirmed by me and by some of my
users.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/comments/0


On 2019-03-28T11:19:02+00:00 Константин wrote:

Created attachment 150350
Double menus in GTK3 VCL

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/comments/1


On 2019-03-28T11:20:23+00:00 Константин wrote:

About attachment - there is just no place for double menu in panel,
vala-panel-appmenu made next menu entries scrollable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/comments/2


On 2019-03-28T11:21:42+00:00 Константин wrote:

Created attachment 150351
Double menus in GTK3 in English (we see, than all menu entries are doubled)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/comments/3


On 2019-03-29T00:13:29+00:00 Xiscofauli wrote:

@Caolán, I thought you might be interested in this issue...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/comments/4


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Medium

** Bug watch added: gitlab.com/vala-panel-project/vala-panel-appmenu/issues #286
   https://gitlab.com/vala-panel-project/vala-panel-appmenu/issues/286

** Bug watch added: Document Foundation Bugzilla #123416
   https://bugs.documentfoundation.org/show_bug.cgi?id=123416

** Bug watch added: Document Foundation Bugzilla #122619
   https://bugs.documentfoundation.org/show_bug.cgi?id=122619

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

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

[Desktop-packages] [Bug 1826543] [NEW] [Wayland] Support multiple monitors with different scaling factors

Public bug reported:

Running 19.04 Disco with Wayland
Version 64ubuntu7

I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.

When running the display solely on my built-in monitor, the dock is
correctly scaled to 200%. When running the display is running solely on
the external monitor, the dock is scaled to 100%.

When running both monitors at the same time, the scaling factor used for
the docks on both monitors is the scaling factor of the primary monitor:
so if that is the external screen is primary then the laptop screen
version of the dock is tiny; and if the built-in screen is primary then
the external monitor dock is huge.

I would expect the dock scaling factor to always match the scaling
factor of the screen that the dock is displayed on.

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

** Summary changed:

- [Wayland] Scale the dock based on the scaling factor for that monitor
+ [Wayland] Support multiple monitors with different scaling factors

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

Title:
  [Wayland] Support multiple monitors with different scaling factors

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

Bug description:
  Running 19.04 Disco with Wayland
  Version 64ubuntu7

  I have a HiDPI laptop screen (XPS13) and a normal DPI external
  monitor. I have the laptop screen set to 200% and the external screen
  set to 100%.

  When running the display solely on my built-in monitor, the dock is
  correctly scaled to 200%. When running the display is running solely
  on the external monitor, the dock is scaled to 100%.

  When running both monitors at the same time, the scaling factor used
  for the docks on both monitors is the scaling factor of the primary
  monitor: so if that is the external screen is primary then the laptop
  screen version of the dock is tiny; and if the built-in screen is
  primary then the external monitor dock is huge.

  I would expect the dock scaling factor to always match the scaling
  factor of the screen that the dock is displayed on.

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

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

[Desktop-packages] [Bug 1823303] Re: error in 10_ubuntu-dock.gschema.override

2019-04-26 Thread Laurent Bonnaud

Thanks a lot!

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

Title:
  error in 10_ubuntu-dock.gschema.override

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  here is the problem:

  # apt upgrade
  [...]
  Processing triggers for libglib2.0-0:amd64 (2.60.0-1) ...
  override for key “transparency-mode” in schema 
“org.gnome.shell.extensions.dash-to-dock” in override file 
“/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the 
list of valid choices; ignoring override for this key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-ubuntu-dock 64ubuntu5
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  5 10:22:46 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1826468] Re: Libreoffice Calc cannot export PDF to a network drive

You're right, this does seem to be the same upstream issue popping up
again.

Would you mind filing an upstream bug report for this at
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided
and sharing the link to that bug here?

** Summary changed:

- Libreoffice Calc cannot export PDF to a network drive
+ [upstream] Libreoffice Calc cannot export PDF to a network drive

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

Title:
  [upstream] Libreoffice Calc cannot export PDF to a network drive

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1825741] Re: Multiple instances of global menu entries

This seems to be an upstream bug. It was resolved in 6.2.2 for some
toolkits but not GTK3.

** Bug watch added: Document Foundation Bugzilla #124391
   https://bugs.documentfoundation.org/show_bug.cgi?id=124391

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=124391
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Multiple instances  of global menu entries
+ [upstream] Multiple instances  of global menu entries

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+subscriptions

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

** Changed in: lmodern (Debian)
   Status: Fix Committed => New

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

Title:
  [gsfonts] Fonts include copyrighted adobe fragment all right reserved

Status in lmodern package in Ubuntu:
  Invalid
Status in lmodern package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/694323:

  Package: lmodern
  Version: 2.004.2-1
  Severity: serious
  control: block -1 by 694308

  This package include copyrighted font hinting from adobe.

  
  t1disasm /usr/share/fonts/X11/Type1/lmr10.pfb | grep -i -A 10 adobe 
  %!PS-AdobeFont-1.0: LMRoman10-Regular 2.004
  %%CreationDate: 7th October 2009
  % Generated by MetaType1 (a MetaPost-based engine)
  % Copyright 2003--2009 by B. Jackowski and J.M. Nowacki (on behalf of TeX 
USERS GROUPS).
  % Supported by CSTUG, DANTE eV, GUST, GUTenberg, NTG, and TUG.
  % METATYPE1/Type 1 version by B. Jackowski & J. M. Nowacki
  % from GUST (http://www.gust.org.pl).
  % This work is released under the GUST Font License.
  % For the most recent version of this license see
  % This work has the LPPL maintenance status `maintained'.
  % The Current Maintainer of this work is Bogus\l{}aw Jackowski and Janusz M. 
Nowacki.
  --
  % Copyright (c) 1987-1990 Adobe Systems Incorporated
  % All Rights Reserved.
  % This code to be used for hint replacement only
  /OtherSubrs
  [ { } { } { }
  {
  systemdict /internaldict known not
  { pop 3 }
  { 1183615869 systemdict /internaldict get exec
  dup /startlock known
  { /startlock get exec }

  
  Thanks

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

I can confirm that Benjamin has solved the issue for us with comment
#89. I too was a user of the Workspace Grid extension. It doesn't start
at all in Dingo, and is greyed out in gnome-tweaks. I removed the plugin
through extensions.gnome.org and restarted, and now everything is
working.

Thank you Benjamin, you have my heartfelt thanks. :)

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

Hi again folks, sadly, in comment #93 I was mistaken. Reverting gnome-
shell-extension-ubuntu-dock does not fix the issue. It appeared to work
on one machine, once, and in my haste I reported the downgrade as a
possible workaround. This is not correct, and I apologise if I got your
hopes up.

I have subsequently downgraded gnome-shell-extension-appindicator, and
gnome-initial-setup (with the --force-confmiss option), but without
success.

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1770629] Re: Keyboard and mouse lockup when using media keys to adjust volume

2019-04-26 Thread Martin Brook

Still an issue in 19.04.

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

Title:
Keyboard and mouse lockup when using media keys to adjust volume

Status in gnome-settings-daemon package in Ubuntu:
New

Bug description:
Ubuntu 18.04 LTS
gnome-settings-daemon 3.28.1-0ubuntu1

Summary:

When I press any of my keyboard's volume up/down/mute keys, my
keyboard and mouse lock up completely. (Mouse pointer frozen and no
keypresses have any effect). The rest of the system continues to
function normally. The on-screen volume notification appears
repeatedly every few seconds.

Variations:
---

Occasionally, I can press the buttons a few times with no effect,
before the lock-up eventually happens.

Also occasionally, my Gnome session may crash completely to a black
screen a few seconds after the input devices lock up.

I haven't been able to discern a pattern to when these different
effects occur.

Troubleshooting attempted:
--

I can reproduce this when running from a Live USB on the same system.

Disabling the keyboard shortcuts for volume up/down and mute in the
keyboard settings GUI does not prevent this issue.

If I set different keys for these shortcuts, they work fine - the
problem is specific to my keyboard's special media keys.

The other (non-audio-related) media keys on my keyboard work fine.

I have gone through the suggested "Useful Information" steps at
https://wiki.ubuntu.com/Hotkeys/Troubleshooting and will attach the
output files to this report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 12:30:24 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-12-14 (147 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/zsh
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to bionic on 2018-04-27 (13 days ago)

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

[Desktop-packages] [Bug 1826468] Re: Libreoffice Calc cannot export PDF to a network drive

2019-04-26 Thread Jarosław Pióro

I have the same version of LibreOffice installed. The problem is not
only with exporting PDF to a network drive, but also with trying to
"Save As" to the same drive. If I change the document and simply "Save"
it, it works well.

I do not use the Libreoffice dialog box to access the network drive, I
connect to it through Nautilus "Connect to server: davs://<>" etc. and
then access it through Nautilus and open the document by double-
clicking.

I had similar problem once after distro upgrade, I believe this bug is related 
to it:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1069757

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

Title:
  Libreoffice Calc cannot export PDF to a network drive

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

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

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

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

This bug was fixed in the package software-properties - 0.98.0

---
software-properties (0.98.0) eoan; urgency=medium

  * Port to PackageKit (LP: #1673258); thanks to  Matthias Klumpp for the
initial work on this in Debian.
  * Run wrap-and-sort
  * Import patches from Debian to minimize delta:
- Have AppStream ignore software-properties-drivers.desktop
- Hack around test suite expecting Ubuntu
- Machine-readable debian/copyright

 -- Julian Andres Klode   Thu, 18 Apr 2019 10:51:45
+0200

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted

2019-04-26 Thread Hui Wang

Please install and test this deb under 4.18 kernel:

sudo dpkg -i oem-.deb
reboot
do the test to see if there is noise or not.

After testing, if want to uninstall the deb:
sudo dpkg -P oem-audio-hda-daily-dkms
reboot


** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+attachment/5259273/+files/oem-audio-hda-daily-dkms_0.1_all.deb

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

Title:
  [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric
  background noise when volume is not muted

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start 
hearing a static/electric (some internal?) sound if the volume isn't muted. 
Something similar occurs with my other earbuds with mic, just much quieter and 
less noticable. It works fine on Windows 10 running on the same machine, and on 
my Android phone. I don't notice is when something is playing, but the 
frequency of the sound changes when I play something, then pause it, the 
background noise will sound slightly different.
  This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB 
and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with 
alsamixer and pavucontrol settings, and nothing fixed this background noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidkoplik   1891 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 20:17:59 2018
  InstallationDate: Installed on 2018-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

I can say with reasonable confidence that this bug is introduced by
gnome-shell-extension-ubuntu-dock_64ubuntu7_all.deb. I downgraded by
downloading gnome-shell-extension-ubuntu-dock_64ubuntu6_all.deb from
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3701.1-deletedppa/+build/16616785 and installing
with dpkg. No dependency issues or conflicts were identified and the
package installed without issue. I restarted my test system and the
problem appears fixed.

I'll report back if this is a red herring, but I thought I should report
as soon as possible so that other's might benefit.

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files from desktop into applications

2019-04-26 Thread Panoramix

nautilus is the problem. when I replaced nautilus with nemo everything
works correctly

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

Title:
  Can no longer drag and drop files from desktop into applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

I can reliably reproduce this issue by clicking either Activities on the
top bar, or by clicking "Show Applications" on the dock.

With the latter, the Applications Search dialogue comes up, but no icons
are shown for recent applications. All applications are shown as
expected.

Once the Search dialogue is displayed, I cannot close it. I can launch a
program from the All page, and the application starts, but I cannot
interact with it. If I switch into a console and kill the application,
the search dialogue is still present.

Like with other users, once the bug is triggered I cannot interact with
anything on the screen except for items on the top bar situated on the
right side of the screen (including the date and time at the center).

To work around I have to switch to a console (Ctrl-Alt-F3), and 'pkill
-9 gnome-shell', followed by 'DISPLAY=":0" gnome-shell'. I can then
switch back to the graphical interface with Ctrl-Alt-F2. This *usually*
works for me, but of course YMMV.

I only noticed this bug when I upgraded my main machine today. I have
another similar system which I updated a few weeks ago. In using that I
experienced none of these issues. That system was updated today and it
now shows the same behaviour, so whatever the bug is, it was introduced
very recently.

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-26 Thread Christian Ehrhardt 

FYI:
I was affected by the issue, but there must be another way to trigger than the 
(re)install of console-setup and/or keyboard-configuration as those actions 
were not triggering the issue for me after I rebooted.
OTOH the time it started to happen perfectly matches a background update to 
those packages:
2019-04-24 01:00:50 configure console-setup:all 1.178ubuntu2.8 

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

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

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

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

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

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

[Desktop-packages] [Bug 1825408] Re: drag/drop to desktop fails

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

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

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

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

Title:
  drag/drop to desktop fails

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Workaround: drag/drop to desktop entirely within Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 13:54:44 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-04-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)

2019-04-26 Thread Giacomo Graziosi

Does anyone know a workaround for this bug?

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

Title:
  Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not
  the ubuntu-dock)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  From time to time, my chrome icon disappears in gnome shell 3.32,
  leaving only the "open window indicator" below it. It's the first of
  my icons, and this is running a vanilla gnome session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  2 17:44:52 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (383 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago)

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

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

Re: [Desktop-packages] [Bug 1826468] [NEW] Libreoffice Calc cannot export PDF to a network drive

Hi Jarosław, please could you confirm which version of LibreOffice-Calc
you’re using.

I’ve just tried this on 19.04 using 1:6.2.2-0ubuntu2 and seems to work
alright for me at least (see screenshots).

Thank you!


** Attachment added: "Screenshot 2019-04-26 at 11.00.34.png"
   
https://bugs.launchpad.net/bugs/1826468/+attachment/5259249/+files/Screenshot%202019-04-26%20at%2011.00.34.png

** Attachment added: "Screenshot 2019-04-26 at 11.01.02.png"
   
https://bugs.launchpad.net/bugs/1826468/+attachment/5259250/+files/Screenshot%202019-04-26%20at%2011.01.02.png

** Attachment added: "Screenshot 2019-04-26 at 11.01.59.png"
   
https://bugs.launchpad.net/bugs/1826468/+attachment/5259251/+files/Screenshot%202019-04-26%20at%2011.01.59.png

** Attachment added: "Screenshot 2019-04-26 at 11.02.12.png"
   
https://bugs.launchpad.net/bugs/1826468/+attachment/5259252/+files/Screenshot%202019-04-26%20at%2011.02.12.png

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

Title:
  Libreoffice Calc cannot export PDF to a network drive

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 18.10 to 19.04 I lost possibility to export a
  document to PDF, if a document is on a network drive (it's a DAVS
  network folder in my case). I receive a pop-up windows about general
  I/O error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 23:35:20 2019
  InstallationDate: Installed on 2018-05-05 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium

2019-04-26 Thread Olivier Tilloy

@ruiromo: no need to reinstall, the problem won't magically go away.
This is an upstream bug (see comment #7).

The snap package isn't affected, but for it to work you will need to
manually copy libpepflashplayer.so to
$HOME/chromium/current/.local/lib/.

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

Title:
  flash player does not work in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  after you allow it to run it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 73.0.3683.103-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU=
   modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 
800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Apr 19 04:29:19 2019
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-20 (729 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Load-Avg-1min: 1.18
  Load-Processes-Running-Percent:   0.4%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 02/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4202
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1826468] Re: Libreoffice Calc cannot export PDF to a network drive