[Desktop-packages] [Bug 1746420] Re: I really don't know , using diagnostic app.

2020-06-23 Thread Daniel van Vugt
Please let us know if you still experience this problem, and if so
whether any processes are using high CPU or lots of memory.

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

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

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

Title:
  I really don't know , using diagnostic app.

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Machine gets slow .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan 30 23:16:28 2018
  DistUpgraded: 2018-01-10 16:36:41,763 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-annan-standard-precise-amd64-20130106-0
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   alsa-hda, 0.201212151034~precise1annan2, 3.2.0-32-generic, x86_64: installed
   asus-wmi, 1.14, 3.2.0-32-generic, x86_64: installed
   compat-wireless-3.4-rc3-1-alx-dkms, 1, 3.2.0-32-generic, x86_64: installed
   i915, 0.1, 3.2.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:115d]
  InstallationDate: Installed on 2018-10-10 (-251 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130106-02:29
  MachineType: ASUSTeK COMPUTER INC. 1015E
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=dad73f6d-4e85-4338-83b0-0e0417a13a96 ro locale=C quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-01-10 (20 days ago)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015E.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1015E
  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.:bvr1015E.302:bd03/05/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 1015E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan 30 22:37:53 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4572 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

2020-06-23 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

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

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


[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

2020-06-23 Thread AaronMa
** Tags added: oem-priority originate-from-1883198 sutton

** Tags added: originate-from-1882188

** Tags added: originate-from-1881988

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

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

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


[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

2020-06-23 Thread AaronMa
** Description changed:

  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.
  
  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313
  
  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421
+ 
+ 
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

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

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


[Desktop-packages] [Bug 1883898] Re: version 3.20.6 turns off plugin requirement for most printers

2020-06-23 Thread zdohnal
Another issue caused by the change mentioned in this issue:

https://bugs.launchpad.net/hplip/+bug/1884835

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

Title:
  version 3.20.6 turns off plugin requirement for most printers

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

Bug description:
  Hi,

  hplip-3.20.6 turns off plugin requirement for most devices which
  required the plugin at the past.

  This will make devices which really need it unable to print and most
  scanning will not work.

  Would you mind reverting the changes in models.dat?

  Thank you in advance!

  Zdenek

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

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


[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

2020-06-23 Thread AaronMa
** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

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

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


[Desktop-packages] [Bug 1871360] Re: Ubuntu Cant find keyboard layout languages

2020-06-23 Thread Launchpad Bug Tracker
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Ubuntu Cant find keyboard layout languages

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

Bug description:
  Ubuntu Cant find keyboard layout languages
  List is empty when filtering as in image: "latvian"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:13 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870515] Re: site-specific browser (SSB) does not work in Firefox

2020-06-23 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  site-specific browser (SSB) does not work in Firefox

Status in firefox package in Ubuntu:
  Expired

Bug description:
  The site-specific browser (SSB) feature does not work, e.g. running:

  firefox --ssb chat.google.com

  will just open a new empty Firefox window. "browser.ssb" is set to
  "true" in about:config.

  Affected version: Firefox 74.0+build3-0ubuntu0.19.10.1 on Ubuntu 19.10
  (eoan)

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

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


[Desktop-packages] [Bug 1874562] Re: MTP android device (usb) doesn't appear in files

2020-06-23 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  MTP android device (usb) doesn't appear in files

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Steps to recreate this:

  Connect an android phone to the computer
  enable file sharing from the notification

  Expected:
  Be able to access the phone from the file application

  Currently:
  Doesn't show up.

  This was working in 18.04. I can also see the device using lsusb as
  `Bus 003 Device 017: ID 18d1:4ee1 Google Inc. Nexus Device (MTP)`. If
  I can help debugging this further please guide me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 16:48:53 2020
  GsettingsChanges: b'org.gnome.nautilus.preferences' 
b'search-filter-time-type' b"'last_used'"
  InstallationDate: Installed on 2020-02-07 (76 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1874655] Re: After suspend / resume, WiFi does not reconnect automatically to an hidden access point

2020-06-23 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  After suspend / resume, WiFi does not reconnect automatically to an
  hidden access point

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  After letting my laptop go to sleep, the WiFi does not reconnect
  anymore to an hidden access point. I must go to the WiFi settings
  window, then go to the menu where hidden networks are... hidden, and
  force Network Manager to connect to the hidden AP. Note that I don't
  have any problem on boot. Just when resuming for suspend mode.

  This is a rather recent issue, which I never encountered before these
  past months. I cannot qualify exactly the time where the bug occurred.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 10:35:40 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-07-19 (1009 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-10-22 (549 days ago)

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

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


[Desktop-packages] [Bug 1874700] Re: file selection represents impossibly small file previews

2020-06-23 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  file selection represents impossibly small file previews

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  
  File selection shows impossibly small
  file previews.

  Can they be increased as in current
  case Nautilus is unusable to select
  files.

  
  >:]

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

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


[Desktop-packages] [Bug 1884336] Re: Erratic ethernet connectivity and icon

2020-06-23 Thread Aurosutru
Here is the result of  journalctl -b 0   while the problem is manifest.

** Attachment added: "Requested Result"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884336/+attachment/5386635/+files/journalctl%20-b%200

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

Title:
  Erratic ethernet connectivity and icon

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.4 LTS

  Installed: 1.10.6-2ubuntu1.4
Candidate: 1.10.6-2ubuntu1.4
Version table:
   *** 1.10.6-2ubuntu1.4 500

  Expected behavior is a stable high-speed internet connection when usb
  tethering with an Android phone.

  Instead, for the past three months, since covid slowed down internet
  connectivity on Jio telecom in India, my Ubuntu internet connectivity
  has become erratic.  In the early morning before 6 AM when I tether an
  Android phone to my laptop the internet connectivity indicator in the
  upper right-hand corner of the desktop shows the normal three boxes in
  a triangle and has decent speed.  As network traffic increases the
  indicator turns to three gray boxes with a question mark in the middle
  and connectivity speed remains decent for a few websites, such as
  YouTube, Google Search and some others, but connectivity stops for
  most websites.  Chromium, Vivaldi and Firefox browsers show the
  following error for such sites: “This site can’t be reached.
  askubuntu.com’s server IP address could not be found.”

  Oddly, in tri-booted Win 10 all websites open reliably 24/7, though
  sometimes at slow speeds.  In Fedora 31 on the same hardware the
  behavior is identical to Ubuntu.  I’ve tried changing the DNS settings
  in Ubuntu to use Cloud Flare, Google and even the DNS settings in
  Windows, but to no avail.  On Ask Ubuntu there were no helpful
  comments except a suggestion to file a bug report.

  Ideally, connectivity without "unable to connect" errors on most
  websites should be available always.

  BTW, when I allowed data to be collected for this bug report it was in
  the early morning, so the connection was working properly and the
  network icon was the normal three boxes in a triangle with decent
  speed.  If need be, I can send more information later when the "unable
  to connect" errors occur from Windows 10, or via email, which always
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 06:49:22 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-25 (664 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.137.129 dev enp0s20u1 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20u1 scope link metric 1000 
   192.168.137.0/24 dev enp0s20u1 proto kernel scope link src 192.168.137.9 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u1  ethernet  connected /org/freedesktop/NetworkManager/Devices/4 
 Wired connection 3  d70d6035-59a6-34c1-a00a-d222c65aef1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp2s0 wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3 
 --  ----   
  
   enp3s0f2   ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/2 
 --  ----   
  
   lo loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1 
 --  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1884860] Re: How to set default applications has changed in Ubuntu 20

2020-06-23 Thread Gunnar Hjalmarsson
Thanks for your report! I submitted an upstream merge request:

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/merge_requests/57

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Triaged

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

Title:
  How to set default applications has changed in Ubuntu 20

Status in gnome-user-docs package in Ubuntu:
  Triaged

Bug description:
  This page:

  https://help.ubuntu.com/stable/ubuntu-help/net-default-browser.html.en

  Says to Open the Activities overview and start typing Details.

  That option no longer exists. I find it now on the left hand side,
  under "Default Applications"

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

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


[Desktop-packages] [Bug 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)

2020-06-23 Thread Daniel van Vugt
I suggest trying a different desktop environment with the same apps for
a while, so we can see if MATE/Marco is the main factor.

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

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing)

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

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

  My desktop usage pattern:

  * MATE desktop
  * 4-desktop setting (standard default MATE when shipped)
  * GNUCASH
  * about 3 windows of terminal (each about 5-10 tabs)
  * XPRA running Firefox web browser (to isolate web browser pixmap memory 
usage, if that was the culprit)
  * LibreOffice (several windows open at any time)
  * using "redshift" to change the desktop color to red at night

  I have never seen this before using Ubuntu 20.04 on this machine.
  Before, when I was running Debian 8, I could run this machine for months 
literally without Xorg memory bloating rapidly like this (but then I was using 
xfce instead of MATE).
  I viewed the output of xrestop, the pixmap memory usage is 

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

2020-06-23 Thread Alex Tu
** Tags added: oem-priority originate-from-1880192

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

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

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


[Desktop-packages] [Bug 1884842] Re: mouse behavior

2020-06-23 Thread Daniel van Vugt
Your kernel log seems to be reporting that the mouse is getting
disconnected and reconnected repeatedly. Is that you unplugging the
mouse or is it doing that while still plugged in?


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  mouse behavior

Status in Ubuntu:
  Incomplete

Bug description:
  some mouse buttons &  screen behaviors related to mouse movement,
  doesnt work

  model textron scorpion 5

  i think that i have chosen to hide some error reports printing from
  the machine  to the OS.because i had some pci errors which led to
  endless reports during installation so i could not even install ubuntu
  in the first place without fixing this.there may be a relation to the
  mouse problem cause i saw that is malfunction is related to other usb
  devices

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 00:03:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8216]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8216]
  InstallationDate: Installed on 2020-02-15 (129 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 007: ID 18f8:1686  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=nomsi vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd05/02/2019:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: X9W86EA#AB7
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1884860] [NEW] How to set default applications has changed in Ubuntu 20

2020-06-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This page:

https://help.ubuntu.com/stable/ubuntu-help/net-default-browser.html.en

Says to Open the Activities overview and start typing Details.

That option no longer exists. I find it now on the left hand side, under
"Default Applications"

** Affects: gnome-user-docs (Ubuntu)
 Importance: Medium
 Status: Triaged

-- 
How to set default applications has changed in Ubuntu 20
https://bugs.launchpad.net/bugs/1884860
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1884754] Re: Fractional scaling broken in VMware Player

2020-06-23 Thread Daniel van Vugt
Sounds like there are two issues here:

> VMware Tools (open-vm-tools) appears to break, no more seamless mouse
between host and Ubuntu

> After next reboot the setting is reverted to 100%

So please choose one of those for this bug to be about. And if you like
then open a new bug for the other issue.

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

Title:
  Fractional scaling broken in VMware Player

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884754] Re: Fractional scaling broken in VMware Player

2020-06-23 Thread Daniel van Vugt
Actually three issues if you include comment #2.

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

** Tags added: xrandr-scaling

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

Title:
  Fractional scaling broken in VMware Player

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593,
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860,
  but those report the issues are fixed. They also do not mention the
  VMware specific issues.

  Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done
  automatically with Easy Install), go to settings, enable Fractional
  Scaling and select any non-integer value.

  Results:
   - The scaling is applied
   - VMware Tools (open-vm-tools) appears to break, no more seamless mouse 
between host and Ubuntu
   - After next reboot the setting is reverted to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 04:30:21 2020
  InstallationDate: Installed on 2020-06-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884863] Re: nautilus ignores actual mount name

2020-06-23 Thread Humphrey van Polanen Petel
** Attachment added: "shows sidebar"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1884863/+attachment/5386631/+files/USB-A_048.jpg

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

Title:
  nautilus ignores actual mount name

Status in nautilus package in Ubuntu:
  New

Bug description:
  insert USB-drive with name "USB-A"
  nautilus shows "USB-A" in the sidebar
  insert another USB-drive with the same name "USB-A"
  nautilus shows another "USB-A" in the sidebar (see attached)
  however
  /media/ shows "USB-A" and "USB-A1" (see attached)

  nautilus should show "USB-A" and "USB-A1" in the sidebar

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 24 11:58:26 2020
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2020-05-31 (23 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  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/1884863/+subscriptions

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


[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)

2020-06-23 Thread Daniel van Vugt
In the past I've noticed this problem on some machine(s) with a built-in
stylus too.

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

Title:
  Wacom stylus not identified/available (ACER SPIN 5)

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

Bug description:
  There is "No stylus found" in the Settings. Stylus itself is working
  flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu
  20.04 (GNOME)?

  Here is the xsetwacom output:

  xsetwacom --list
  Wacom HID 495F Pen stylus id: 9   type: STYLUS
  Wacom HID 495F Finger touch   id: 10  type: TOUCH 
  Wacom HID 495F Pen eraser id: 18  type: ERASER

  
  PS: I am currently forced to use these kernel boot parameters:

  i8042.nopnp=1 pci=nocrs

  (because of this bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 )

  Many Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 12:43:21 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-19 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884863] [NEW] nautilus ignores actual mount name

2020-06-23 Thread Humphrey van Polanen Petel
Public bug reported:

insert USB-drive with name "USB-A"
nautilus shows "USB-A" in the sidebar
insert another USB-drive with the same name "USB-A"
nautilus shows another "USB-A" in the sidebar (see attached)
however
/media/ shows "USB-A" and "USB-A1" (see attached)

nautilus should show "USB-A" and "USB-A1" in the sidebar

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-106-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 24 11:58:26 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2020-05-31 (23 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "shows /dev/"
   
https://bugs.launchpad.net/bugs/1884863/+attachment/5386623/+files/humphrey_047.jpg

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

Title:
  nautilus ignores actual mount name

Status in nautilus package in Ubuntu:
  New

Bug description:
  insert USB-drive with name "USB-A"
  nautilus shows "USB-A" in the sidebar
  insert another USB-drive with the same name "USB-A"
  nautilus shows another "USB-A" in the sidebar (see attached)
  however
  /media/ shows "USB-A" and "USB-A1" (see attached)

  nautilus should show "USB-A" and "USB-A1" in the sidebar

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-106-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 24 11:58:26 2020
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2020-05-31 (23 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  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/1884863/+subscriptions

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


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

2020-06-23 Thread Daniel van Vugt
Please:

1. Launch the 'Extensions' app and verify you only have the 3 default
Ubuntu extensions. If you have any others then please disable them.

2. If you only have the 3 default Ubuntu extensions then please provide
a screenshot of your desktop here, and then try disabling 'Ubuntu
AppIndicators'.

3. If you have completed steps 1 and 2 and the problem still occurs then
please check for crashes using these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

** Summary changed:

- Xorg freeze
+ The screen freezes every now and then

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

Title:
  The screen freezes every now and then

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen freezes every now and then.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44
  Uname: Linux 5.4.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 15:36:58 2020
  DistUpgraded: 2020-06-23 14:24:21,927 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:802d]
  InstallationDate: Installed on 2020-04-25 (58 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP Spectre Pro x360 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-38-generic 
root=UUID=079528a8-d4db-4fc9-b519-73521b170d15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-06-23 (0 days ago)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 802D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd12/17/2015:svnHewlett-Packard:pnHPSpectreProx360G1:pvr:rvnHewlett-Packard:rn802D:rvr58.51:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Pro x360 G1
  dmi.product.sku: P7Q68PA#ABG
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2006181830.f44908~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2006230730.3fec2f~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2006230730.3fec2f~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/gnome-shell/+bug/1884732/+subscriptions

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


[Desktop-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-23 Thread Daniel van Vugt
If you can provide a full list of processes running before 'zfs-
mount.service' then I might recognise something that could cause it.

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

Title:
  pulseaudio creates /root/.config/pulse/ before zfs-mount.service can
  mount the /root dataset

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use 'zfs' and have /root as its own dataset which is mounted during
  startup by 'zfs-mount.service'.

  At one of the latest upgrades, the 'zfsutils-linux' package failed to
  update because the service 'zfs-mount' service had an issue and could
  not mount the '/root' dataset because the '/root' directory was not
  empty (temporary solution was to rename /root and call 'zfs mount'
  again).

  Further investigation shows that everytime at startup, the /root
  directory is created before the 'zfs-mount.service' has a chance to
  mount the 'root' dataset.

  The culprit seems to be something pulseaudio related: the content of /root 
folder after startup is as follows:
  -
  root@minighost:~# tree -a /root
  .
  ├── .cache
  └── .config
  └── pulse
  └── fe1417537ae0451abdb60c5df28fe825-runtime -> 
/tmp/pulse-PKdhtXMmr18n

  4 directories, 0 files
  root@minighost:~#
  -  


  Extra details:

  - Ubuntu release:
  -
  root@minighost:~# lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  -

  
  - status of 'zfs-mount.service' is the following:
  -  
  root@minighost:~# systemctl status zfs-mount
  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 
6h ago
 Docs: man:zfs(8)
  Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
 Main PID: 2062 (code=exited, status=1/FAILURE)

  Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems...
  Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not 
empty
  Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems.
  root@minighost:~#
  -  


  - software versions:
  -
  root@minighost:~# apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.3
Candidate: 1:13.99.1-1ubuntu3.3
Version table:
   *** 1:13.99.1-1ubuntu3.3 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  root@minighost:~# apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.1
Candidate: 0.8.3-1ubuntu12.1
Version table:
   *** 0.8.3-1ubuntu12.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dumi   2419 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jun 21 19:17:20 2020
  InstallationDate: Installed on 2018-09-08 (651 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-24 (57 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  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.12.1:bd12/11/2019: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:

[Desktop-packages] [Bug 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded

2020-06-23 Thread Daniel van Vugt
I'm thinking if this is a general problem with animated indicators then
bug 784055 might cover it. If however it's due to lots of logging then
bug 1849142 might cover it. Until we know which this bug is incomplete.
If you don't care to investigate further then I understand, and this bug
will auto-close after 60 days.

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

Title:
  Ubuntu freezing intermittently when the mega.nz appindicator is loaded

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

Bug description:
  I had similar issues when 20.04 was released, then it disappeared with
  an upgrade - but sadly it's back. I have short intermittent freezings
  of the OS. About every 15-30 seconds Ubunut freezes for a second or
  two. Eg when writing this description, the OS freezes every second
  word. When the freeze goes away the OS is snappy. I have tried
  switching between Wayland and Xorg - but the problem persists. If I
  write something when it freezes up the last
  character will be replicated many times -
  like what happened jut now. This
  problem did not show up in ubuntu 18.04 through 19.10. Hope U can
  fix this soon - using my laptop in unbearable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 23:54:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
  InstallationDate: Installed on 2020-05-12 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M13
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C189
  dmi.product.version: M13
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/gnome-shell-extension-appindicator/+bug/1884396/+subscriptions

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


[Desktop-packages] [Bug 1884384] Re: in high contrast mode the calendar display uncomfortable

2020-06-23 Thread Daniel van Vugt
That looks like a bug in your custom theme. It doesn't happen in the
regular Ubuntu themes.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1884384

Title:
  in high contrast mode the calendar display uncomfortable

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  in high contrast mode the calendar display uncomfortable

  i.e. the weekends and the column with the number of week are very hard
  to comprehend :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 21:33:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 174f:241a Syntek EasyCamera
   Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash 
resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-17ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:svnLENOVO:pn81FL:pvrLenovoideapad330-17ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-17ICH:
  dmi.product.family: ideapad 330-17ICH
  dmi.product.name: 81FL
  dmi.product.sku: LENOVO_MT_81FL_BU_idea_FM_ideapad 330-17ICH
  dmi.product.version: Lenovo ideapad 330-17ICH
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/gnome-shell/+bug/1884384/+subscriptions

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


[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled

2020-06-23 Thread Daniel van Vugt
> I believe the app is designed to work on per user extensions only.

That's incorrect. The 'Extensions' app displays those from /usr/share
/gnome-shell/extensions/ as "Built-in" and you can toggle them via the
GUI (I just checked again on 20.04). An extension can be installed
system-wide and manually disabled per-user, via the GUI. If that's not
working for you then please log a new bug about the Extensions app by
running:

  ubuntu-bug gnome-shell

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

Title:
  gnome-shell animations are noticeably stuttery when the Ubuntu
  extensions are enabled

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

Bug description:
  I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running 
Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this 
is not always the case.
  The applications animation (the icons coming from the bottom left) is 
specially stuttery most of the time. Sometimes it is buttery smooth, but most 
of the times it is not. It is difficult to pinpoint when.

  Some exploration that may help to find the issue:
  * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much 
smoother. This seems to indicate that the problem is somehow related to the 
Intel iGPU.
  * Animations seem smoother under Wayland. But, because of other limitations, 
I am staying on Xorg for now.
  * The application animation is super stuttery the first time it is opened in 
a session. It gets slowly better with subsequent uses, although never totally 
smooth.
  " The animation is noticeably more stuttery if it opens the “All” 
applications tab instead of “Frequent” apps. Maybe the number of apps (icons) 
is a factor?
  * Vanilla gnome-session seems to be smoother. Maybe the problem is related to 
Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default 
extensions are enabled).

  These datapoints are mainly subjective as I have no means of properly
  measure animations performance.

  Don't get my wrong, 20.04 is a clear improvement over 18.04. But it
  seems there is some room for improvement at least in this hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 15:23:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-23 (780 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566

2020-06-23 Thread Daniel van Vugt
^^^
I very much doubt that is Mesa's fault...

autopkgtest [12:39:33]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 139
autopkgtest [12:39:33]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
Segmentation fault (core dumped)

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

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Invalid
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, 

[Desktop-packages] [Bug 1884856] [NEW] Chromium-browser is built with NEON on armhf (SIGILL, Illegal instruction)

2020-06-23 Thread Dmitry Osipenko
Public bug reported:

Chromium-browser stopped working on NVIDIA Tegra20 devices since the
time it was switched to the snap packaging.

# gdb /snap/bin/chromium
...
Thread 11 "chrome" received signal SIGILL, Illegal instruction.
0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
(gdb) bt
#0  0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#1  0xb6b509c8 in std::__1::locale::__global() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#2  0xb6b50a32 in std::__1::locale::locale() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#3  0xb6b3e7d0 in std::__1::basic_streambuf 
>::basic_streambuf() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#4  0xb6b3ede6 in std::__1::DoIOSInit::DoIOSInit() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#5  0xb6b3f9b2 in _GLOBAL__sub_I_iostream.cpp () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
#6  0xb6f215c0 in ?? () from target:/lib/ld-linux-armhf.so.3

(gdb) layout asm
│  >0xb6b4ee9a <_ZNSt3__16locale5__impC2Ej+10>  vmov.i32q8, #0  ; 
0x  

│   0xb6b4ee9e <_ZNSt3__16locale5__impC2Ej+14>  mov r9, r0  

  
│   0xb6b4eea0 <_ZNSt3__16locale5__impC2Ej+16>  add.w   r3, r9, #40 ; 
0x28



NVIDIA Tegra20 is one of ARMv7 CPUs which do not support NEON instructions, 
"vmov.i32 q8" is the ARM NEON instruction because q8 is the NEON register. Will 
be great if the compiler flags could be changed back to what was used for the 
deb packaging, thanks in advance!

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Chromium-browser is built with NEON on armhf (SIGILL, Illegal
  instruction)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium-browser stopped working on NVIDIA Tegra20 devices since the
  time it was switched to the snap packaging.

  # gdb /snap/bin/chromium
  ...
  Thread 11 "chrome" received signal SIGILL, Illegal instruction.
  0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  (gdb) bt
  #0  0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #1  0xb6b509c8 in std::__1::locale::__global() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #2  0xb6b50a32 in std::__1::locale::locale() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #3  0xb6b3e7d0 in std::__1::basic_streambuf 
>::basic_streambuf() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #4  0xb6b3ede6 in std::__1::DoIOSInit::DoIOSInit() () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #5  0xb6b3f9b2 in _GLOBAL__sub_I_iostream.cpp () from 
target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so
  #6  0xb6f215c0 in ?? () from target:/lib/ld-linux-armhf.so.3

  (gdb) layout asm
  │  >0xb6b4ee9a <_ZNSt3__16locale5__impC2Ej+10>  vmov.i32q8, #0  ; 
0x  

  │   0xb6b4ee9e <_ZNSt3__16locale5__impC2Ej+14>  mov r9, r0


  │   0xb6b4eea0 <_ZNSt3__16locale5__impC2Ej+16>  add.w   r3, r9, #40 ; 
0x28


  
  NVIDIA Tegra20 is one of ARMv7 CPUs which do not support NEON instructions, 
"vmov.i32 q8" is the ARM NEON instruction because q8 is the NEON register. Will 
be great if the compiler flags could be changed back to what was used for the 
deb packaging, thanks in advance!

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

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


[Desktop-packages] [Bug 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs

2020-06-23 Thread Brian Murray
** Tags added: rls-gg-incoming

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

Title:
  ubuntu-desktop-minimal should not depend on mysql libs

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 20.04 I decided to remove packages that I don't
  need or use.

  I was surprised to find that mysql client, server and common packages
  were installed, as I could not remember having installed mysql -- I
  don't use it or develop for it...

  When I removed them, ubuntu-desktop-minimal went along for the ride:

  c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common 
mysql-server-core-5.7 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'mysql-client-core-5.7' is not installed, so not removed
  Package 'mysql-server-core-5.7' is not installed, so not removed
  The following package was automatically installed and is no longer required:
libgsound0
  Use 'sudo apt autoremove' to remove it.
  The following packages will be REMOVED:
colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* 
mysql-common* ubuntu-desktop-minimal*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 28.4 MB disk space will be freed.
  (Reading database ... 381127 files and directories currently installed.)
  Removing ubuntu-desktop-minimal (1.443) ...
  Removing gnome-control-center (1:3.34.1-1ubuntu3) ...
  Removing colord (1.4.4-1ubuntu1) ...
  Removing libsane:amd64 (1.0.27-3.2ubuntu3) ...
  Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ...
  Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ...
  Removing mysql-common (5.8+1.0.5ubuntu2) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ...
  Processing triggers for libc-bin (2.30-0ubuntu3) ...
  Processing triggers for man-db (2.9.0-2) ...
  Processing triggers for dbus (1.12.16-2ubuntu2) ...
  Processing triggers for udev (244-3ubuntu1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
  (Reading database ... 380812 files and directories currently installed.)
  Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ...
  Purging configuration files for colord (1.4.4-1ubuntu1) ...

  And, reinstalling ubuntu-desktop-minimal wants to brings them back,
  even with recommends and suggests turned off:

  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-
  --no-install-recommends  --no-install-suggests
  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-suggests 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common
  Suggested packages:
colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip
  Recommended packages:
gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker 
sane-utils firefox hplip
  The following NEW packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common 
ubuntu-desktop-minimal
  0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/6,114 kB of archives.
  After this operation, 28.4 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 

  This seems really wrong... and looks like a transitive dependency, as
  I don't see it in apt-get showpkg ubuntu-desktop-minimal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop-minimal 1.443
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux 
ashmem_linux
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 19:26:53 2020
  InstallationDate: Installed on 2018-08-26 (514 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago)

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

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


[Desktop-packages] [Bug 1883705] Autopkgtest regression report (libgphoto2/2.5.25-0ubuntu0.1)

2020-06-23 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libgphoto2 (2.5.25-0ubuntu0.1) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.44.1-1ubuntu1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#libgphoto2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  SRU the current 2.5.25 stable update

Status in libgphoto2 package in Ubuntu:
  Fix Released
Status in libgphoto2 source package in Focal:
  Fix Committed
Status in libgphoto2 package in Debian:
  Fix Released

Bug description:
  * Impact

  That's a stable update including bugfixes and support for newer
  cameras

  The list of changes is available there:
  https://sourceforge.net/projects/gphoto/files/libgphoto/2.5.25/

  * Test case

  Connect a camera and check that the desktop correctly see it and
  prompt for an action. Check that the content can be browsed from
  nautilus and the photos imported from shotwell (unmount the device
  from nautilus first if needed)

  * Regression potential

  Nothing specific to check, the fixes are mostly for hardware that was
  not working and the change devices specific

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

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


[Desktop-packages] [Bug 1884850] [NEW] Xorg server uses unacceptably large amounts of memory (and keep growing)

2020-06-23 Thread Wirawan Purwanto
Public bug reported:

Description: Xorg server uses unacceptably large amounts of memory (and
keep growing)

Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my laptop
(Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I have been
troubled by the way Xorg process uses memory.

Here is an example of memory usage of Xorg as a function of time. I
rebooted the laptop on June 17:

Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

The filename indicates the date the "ps fuxa" command was run.
Contrast this against the memory usage of another Xorg process run for XPRA:

Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

My desktop usage pattern:

* MATE desktop
* 4-desktop setting (standard default MATE when shipped)
* GNUCASH
* about 3 windows of terminal (each about 5-10 tabs)
* XPRA running Firefox web browser (to isolate web browser pixmap memory usage, 
if that was the culprit)
* LibreOffice (several windows open at any time)
* using "redshift" to change the desktop color to red at night

I have never seen this before using Ubuntu 20.04 on this machine.
Before, when I was running Debian 8, I could run this machine for months 
literally without Xorg memory bloating rapidly like this (but then I was using 
xfce instead of MATE).
I viewed the output of xrestop, the pixmap memory usage is dominated by marco 
and wnck-applet:

xrestop - Display: localhost
  Monitoring 36 clients. XErrors: 0
  Pixmaps:  110748K total, Other:  84K total, All:  110833K 
total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier 
   
1002052   27 170170198K 42K  70241K  2585 marco
1c0 9409   5630428K  1K  30430K  2612 
wnck-applet
140 841   21  116 3134K  4K   3138K  2603 Desktop
000 2020  178 2700K  6K   2706K   ?   
3e0 0 

[Desktop-packages] [Bug 1884846] [NEW] Can't connect to internet if second user session

2020-06-23 Thread Facundo Batista
Public bug reported:

My kid was using the laptop, connected to internet in his user session.

I switched to my user (but his session was still active), and
NetworkManager couldn't connect to internet.

Error from syslog:

Jun 23 19:30:15 tanquita NetworkManager[854]:   [1592951415.1979]
audit: op="connection-activate" uuid="a52379fa-
0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000
result="fail" reason="Private connection already active on the device:
uid 1000 has no permission to perform this operation"

(uid 1000 is myself)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Tue Jun 23 19:40:19 2020
InstallationDate: Installed on 2020-06-20 (3 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp4s0 scope link metric 1000 
 192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 metric 
600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Can't connect to internet if second user session

Status in network-manager package in Ubuntu:
  New

Bug description:
  My kid was using the laptop, connected to internet in his user
  session.

  I switched to my user (but his session was still active), and
  NetworkManager couldn't connect to internet.

  Error from syslog:

  Jun 23 19:30:15 tanquita NetworkManager[854]: 
  [1592951415.1979] audit: op="connection-activate" uuid="a52379fa-
  0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000
  result="fail" reason="Private connection already active on the device:
  uid 1000 has no permission to perform this operation"

  (uid 1000 is myself)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Jun 23 19:40:19 2020
  InstallationDate: Installed on 2020-06-20 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 
metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal

2020-06-23 Thread Brian Murray
I don't see gnome-software version 3.36.1 in Groovy yet...

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gnome-software.

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  [ Regression Potential ]

  Changes could cause issues in GNOME Software, which might make it hard
  to install or remove software. Default store in Ubuntu is snap-store,
  so this doesn't affect the majority of users.

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

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


[Desktop-packages] [Bug 1883705] Re: SRU the current 2.5.25 stable update

2020-06-23 Thread Brian Murray
Hello Sebastien, or anyone else affected,

Accepted libgphoto2 into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libgphoto2/2.5.25-0ubuntu0.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libgphoto2 (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 2.5.25 stable update

Status in libgphoto2 package in Ubuntu:
  Fix Released
Status in libgphoto2 source package in Focal:
  Fix Committed
Status in libgphoto2 package in Debian:
  Fix Released

Bug description:
  * Impact

  That's a stable update including bugfixes and support for newer
  cameras

  The list of changes is available there:
  https://sourceforge.net/projects/gphoto/files/libgphoto/2.5.25/

  * Test case

  Connect a camera and check that the desktop correctly see it and
  prompt for an action. Check that the content can be browsed from
  nautilus and the photos imported from shotwell (unmount the device
  from nautilus first if needed)

  * Regression potential

  Nothing specific to check, the fixes are mostly for hardware that was
  not working and the change devices specific

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

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


[Desktop-packages] [Bug 1883694] Re: [SRU] New upstream release 2.64.3

2020-06-23 Thread Brian Murray
Hello Iain, or anyone else affected,

Accepted glib2.0 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.64.3-1~ubuntu20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glib2.0 (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] New upstream release 2.64.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
   - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
   - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

  * Translation updates:
   - Chinese (Taiwan)
   - German

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.
  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+subscriptions

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


[Desktop-packages] [Bug 1872026] Re: App icon aspect ratio in the panel is broken

2020-06-23 Thread Alexey Kulik
It fixes the issue for me after update of gnome-shell package with 
focal-proposed enabled.
gnome-shell version is 3.36.3-1ubuntu1~20.04.2
Tested using winecfg.

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

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

Title:
  App icon aspect ratio in the panel is broken

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  The aspect ratio of the icon on the top left of the screen (Activites
  bar?) is broken so it looks taller and thinner than normal.

  See attached screenshot.

  [ Test case ]

  - Run an application such as update-manager
  - The application icon on the top panel should have correct propotions

  [ Regression potential ]

  Icons may have wrong vertical aligment

  -

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:10:09 2020
  InstallationDate: Installed on 2020-01-24 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-04-10 09:03:51.154471
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2020-04-03T20:22:43.358127

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

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


[Desktop-packages] [Bug 1884101] Re: [SRU] jackdbus produces high cpu load

2020-06-23 Thread Brian Murray
Assignment isn't really an important part of the SRU process from the
SRU team's perspective. If there is some documentation that indicates it
is please let me know.

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  Fix Committed
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1876882] Autopkgtest regression report (mesa/20.0.8-0ubuntu1~18.04.1)

2020-06-23 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (20.0.8-0ubuntu1~18.04.1) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

pymol/1.8.4.0+dfsg-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Invalid
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-10 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: more or less just adds support for new llvm

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

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


[Desktop-packages] [Bug 1868520] Autopkgtest regression report (mesa/20.0.8-0ubuntu1~18.04.1)

2020-06-23 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (20.0.8-0ubuntu1~18.04.1) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

pymol/1.8.4.0+dfsg-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Invalid
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, 

[Desktop-packages] [Bug 1882901] Autopkgtest regression report (mesa/20.0.8-0ubuntu1~18.04.1)

2020-06-23 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (20.0.8-0ubuntu1~18.04.1) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

pymol/1.8.4.0+dfsg-1build1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Migrate mesa to llvm 10

Status in libclc package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libclc source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in libclc source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Mesa should migrate to llvm 10. Focal didn't migrate to it before
  release, because there was a build issue on ppc64el, which has since
  been fixed.

  [Test case]

  Test AMD graphics after installing migrated packages.

  [Regression potential]

  This has been in Debian for a month now without issues.

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

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


[Desktop-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

2020-06-23 Thread Erich Eickmeyer
** Changed in: jack-mixer (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Committed
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Confirmed

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

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

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


[Desktop-packages] [Bug 1884101] Re: [SRU] jackdbus produces high cpu load

2020-06-23 Thread Erich Eickmeyer
Sebastien, yeah, it's uploaded. Except proper SRU procedure is that,
once I have it done, I unassign myself and let the SRU team set it as
"Fix Commited", afaik. Hence, I unassigned myself and didn't change the
status.

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  Fix Committed
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1884842] [NEW] mouse behavior

2020-06-23 Thread sciamanocaotico
Public bug reported:

some mouse buttons &  screen behaviors related to mouse movement, doesnt
work

model textron scorpion 5

i think that i have chosen to hide some error reports printing from the
machine  to the OS.because i had some pci errors which led to endless
reports during installation so i could not even install ubuntu in the
first place without fixing this.there may be a relation to the mouse
problem cause i saw that is malfunction is related to other usb devices

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 24 00:03:04 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: anbox, 1: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8216]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8216]
InstallationDate: Installed on 2020-02-15 (129 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 007: ID 18f8:1686  
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=nomsi vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.52
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8216
dmi.board.vendor: HP
dmi.board.version: 83.18
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd05/02/2019:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.18:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: X9W86EA#AB7
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  mouse behavior

Status in xorg package in Ubuntu:
  New

Bug description:
  some mouse buttons &  screen behaviors related to mouse movement,
  doesnt work

  model textron scorpion 5

  i think that i have chosen to hide some error reports printing from
  the machine  to the OS.because i had some pci errors which led to
  endless reports during installation so i could not even install ubuntu
  in the first place without fixing this.there may be a relation to the
  mouse problem cause i saw that is malfunction is related to other usb
  devices

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 00:03:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: anbox, 1: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8216]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8216]
  InstallationDate: Installed on 2020-02-15 (129 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
  

[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules

2020-06-23 Thread J. Snow
I'm facing the exact same problem on Ubuntu 20.04. Is there any
workaround?

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

Title:
  [cosmic+] error booting with prime-select intel: prime-select does not
  update initramfs to blacklist nvidia modules

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in nvidia-prime source package in Eoan:
  Triaged
Status in ubuntu-drivers-common source package in Eoan:
  Triaged

Bug description:
  when I try to boot with the iGPU selected, DE won't boot, with nvidia 
selected, everithing is fine.
  I tried uninstalling nvidia driver and it allowed my to access without any 
problems and intel is working fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-prime 0.8.13
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 16 12:41:26 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-25 (20 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884838] [NEW] woops-logout white page after installation from scratch on old crappy hp

2020-06-23 Thread Louis-Gabriel Thibault
Public bug reported:

Happened while doing upgrade post vanilla installation from scratch
(20.04 desktop).

I got a white page that said something went wrong "logout". Could not
get back into interactive graphics mode (had to ctrl alt f3 to issue a
reboot command)

package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade:
installed orca package post-installation script subprocess returned
error exit status 1

lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

$ apt-cache policy orca
orca:
  Installed: 3.36.2-1ubuntu1~20.04.1
  Candidate: 3.36.2-1ubuntu1~20.04.1
  Version table:
 *** 3.36.2-1ubuntu1~20.04.1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
100 /var/lib/dpkg/status
 3.36.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: orca 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 23 16:37:11 2020
ErrorMessage: installed orca package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-06-23 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: orca
Title: package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: 
installed orca package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  woops-logout white page after installation from scratch on old crappy
  hp

Status in orca package in Ubuntu:
  New

Bug description:
  Happened while doing upgrade post vanilla installation from scratch
  (20.04 desktop).

  I got a white page that said something went wrong "logout". Could not
  get back into interactive graphics mode (had to ctrl alt f3 to issue a
  reboot command)

  package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade:
  installed orca package post-installation script subprocess returned
  error exit status 1

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy orca
  orca:
Installed: 3.36.2-1ubuntu1~20.04.1
Candidate: 3.36.2-1ubuntu1~20.04.1
Version table:
   *** 3.36.2-1ubuntu1~20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   3.36.1-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: orca 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 23 16:37:11 2020
  ErrorMessage: installed orca package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-06-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: orca
  Title: package orca 3.36.2-1ubuntu1~20.04.1 failed to install/upgrade: 
installed orca package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1882885] Re: FP Auth enroll for Multi user Scenario

2020-06-23 Thread Juan Martinez
Added screenshot

** Attachment added: "noMultipleUsers.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+attachment/5386553/+files/noMultipleUsers.jpg

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

Title:
  FP Auth  enroll for Multi user Scenario

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

Bug description:
  It is observed 'Couldn't access any fingerprint reader message' while trying 
to enroll FP's for the first time for a newly created user.
  Looks like fprintd daemon is not responding for any new user other than root?

  Ubuntu version : 20.04 LTS

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

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


[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-23 Thread mastorak
@3v1n0
It is desktop GPU.
I tried the new mutter package. It doesn't fix the problem.
The behavior now is the following:
-enable fractional scaling
-select and apply 125%
-goes to 200%
-select to go back to to 100%
-things are tiny again but the desktop pixels have increased beyond the borders 
of the screen so you have to scroll  to view the rest of the desktop.
When going from 100% to 200% and back to 100% -without- enabling fractional 
scaling going back to 100%  behaves correctly.
Please find attached the log.


** Attachment added: "mutter.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5386552/+files/mutter.log

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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


[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues

2020-06-23 Thread Michael Johnson
I was unable to get driverless printing working from local machine.

I was able to get driverless printing working from Network, but to
configure this printer on a WiFi network I required a different computer
with working software (was able to borrow a Windows system with working
software).

Once the printer was on the network (WiFi in this case) I was able to
get basic driverless printing working.

HP software still not working, and USB printing still not working.

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

Title:
  Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip
  issues

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

Bug description:
  Hi,
   
  I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04,
  Spent some time troubleshooting with the default (previously current) drivers 
hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially 
due to missing dependencies. Errors about missing pyqt4 dependencies among 
others.

  When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found
  but fails to print.

  Just noticed similar bug filed, 690720 , and saw note that new hplip
  ver. 3.20.5 was just released and supports Ubuntu 20.04

  When trying to install new package hplip ver. 3.20.5 with the .run
  script provided by HP I am unable to complete installatoin as it
  reports unmet dependency of pyqt5 , even though package python3-pyqt5
  is installed on system.

  https://developers.hp.com/hp-linux-imaging-and-printing/gethplip

  Maybe the repo just needs to be updated with a newer build (3.20.5) to
  install on my system, or is there something that can be done in the
  meantime.

  Below hp-check -t when using the repo hplip ver. 3.20.3 ,

  ==
  Saving output in log file: /root/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1

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

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are installed to successfully compile
  HPLIP.

 
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the proper dependencies installed to
  successfully run. 

 
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
  

  Check types:  

 
  a. EXTERNALDEP - External Dependencies

 
  b. GENERALDEP - General Dependencies (required both at compile and run time)  

 
  c. COMPILEDEP - Compile time Dependencies 

 
  d. [All are run-time checks]  

 
  PYEXT SCANCONF QUEUES PERMISSION  

 

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10
  versions dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed 

[Desktop-packages] [Bug 1884823] [NEW] gnome-disks: missing "x" in windowbar to close gnome-disks

2020-06-23 Thread Matthias Sprau
Public bug reported:

There are only buttons to minimize or maximize the window of gnome-
disks, but no button to close that window as usual.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-disk-utility 3.36.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 23 21:10:23 2020
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2020-05-23 (31 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-disks: missing "x" in windowbar to close gnome-disks

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  There are only buttons to minimize or maximize the window of gnome-
  disks, but no button to close that window as usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-disk-utility 3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 21:10:23 2020
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2020-05-23 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=de_DE.UTF-8
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1884822] [NEW] nautilus search bar generates high cpu usage - no reaction on 1st double-click

2020-06-23 Thread Matthias Sprau
Public bug reported:

If I try to find e.g. a certain music file, I browse in nautilus to the folder 
"music" and start  typing "mo":
- cpu usage is prompt very high although the correct folder is shown immediatly
- mouse pointer shows activity (circle rotates constantly)
- if I use a double-click on the requested folder, nothing happens; only on the 
second try the double-click opens that folder

Goal:
- the first double-click should open the requested folder
- cpu usage shouldn't be so high

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 23 20:58:45 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2020-05-23 (31 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  nautilus search bar generates high cpu usage - no reaction on 1st
  double-click

Status in nautilus package in Ubuntu:
  New

Bug description:
  If I try to find e.g. a certain music file, I browse in nautilus to the 
folder "music" and start  typing "mo":
  - cpu usage is prompt very high although the correct folder is shown 
immediatly
  - mouse pointer shows activity (circle rotates constantly)
  - if I use a double-click on the requested folder, nothing happens; only on 
the second try the double-click opens that folder

  Goal:
  - the first double-click should open the requested folder
  - cpu usage shouldn't be so high

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 20:58:45 2020
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2020-05-23 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=de_DE.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/1884822/+subscriptions

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


[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2020-06-23 Thread Rohit Vashisht
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

I use debootstrap and chroot to install. Just migrated from Debian where
this issue doesn't exist on any branch. Installed Ubuntu 20.04 and the
bug is still there. I was able to fix it using the instructions given in
post #6.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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


[Desktop-packages] [Bug 1877401] Re: The Italian translation is not complete

2020-06-23 Thread Gunnar Hjalmarsson
Checked the amd64 buildlog for
.
evince.pot was updated successfully.

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

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

Title:
  The Italian translation is not complete

Status in Ubuntu Translations:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Focal:
  Fix Committed

Bug description:
  The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is
  not complete. Some items in the menu are shown in English, like "Right
  to Left Document" and "Properties".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1877401/+subscriptions

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


[Desktop-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-23 Thread Dumitru Sipos
I *never* logged in graphically as root. I also do not use the root account: at 
most some 'sudo' commands from time to time. In the previous comments I had the 
root shell because I wanted to show as easy as possible that the whole content 
of the '/root' is only one symbolic link 
(fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n) in the 
.config/pulse.
And this link is created before the zfs-mount service has a chance to mount the 
'real' root folder.

OK, nevermind that, do you know any good way how to find out which process 
might be the culprit?
Is there some place where I can look? or some pulseaudio related debug config 
that I can enable somewhere to trace what happens during system startup?
Any hint or suggestion is greatly appreciated.

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

Title:
  pulseaudio creates /root/.config/pulse/ before zfs-mount.service can
  mount the /root dataset

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use 'zfs' and have /root as its own dataset which is mounted during
  startup by 'zfs-mount.service'.

  At one of the latest upgrades, the 'zfsutils-linux' package failed to
  update because the service 'zfs-mount' service had an issue and could
  not mount the '/root' dataset because the '/root' directory was not
  empty (temporary solution was to rename /root and call 'zfs mount'
  again).

  Further investigation shows that everytime at startup, the /root
  directory is created before the 'zfs-mount.service' has a chance to
  mount the 'root' dataset.

  The culprit seems to be something pulseaudio related: the content of /root 
folder after startup is as follows:
  -
  root@minighost:~# tree -a /root
  .
  ├── .cache
  └── .config
  └── pulse
  └── fe1417537ae0451abdb60c5df28fe825-runtime -> 
/tmp/pulse-PKdhtXMmr18n

  4 directories, 0 files
  root@minighost:~#
  -  


  Extra details:

  - Ubuntu release:
  -
  root@minighost:~# lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  -

  
  - status of 'zfs-mount.service' is the following:
  -  
  root@minighost:~# systemctl status zfs-mount
  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 
6h ago
 Docs: man:zfs(8)
  Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
 Main PID: 2062 (code=exited, status=1/FAILURE)

  Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems...
  Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not 
empty
  Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems.
  root@minighost:~#
  -  


  - software versions:
  -
  root@minighost:~# apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.3
Candidate: 1:13.99.1-1ubuntu3.3
Version table:
   *** 1:13.99.1-1ubuntu3.3 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  root@minighost:~# apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.1
Candidate: 0.8.3-1ubuntu12.1
Version table:
   *** 0.8.3-1ubuntu12.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dumi   2419 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jun 21 19:17:20 2020
  InstallationDate: Installed on 2018-09-08 (651 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: 

[Desktop-packages] [Bug 1884393] Re: With Auto-hide dock enabled, icons get hidden behind dock & dock does not hide untill there's an app near it

2020-06-23 Thread Nakshatra Nag
maybe take a feature request to hide the dock on desktop if user is not
pointing to it.

So that all icons can be placed on left side too & can be accessed
without any overlays interfering over them.

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

Title:
  With Auto-hide dock enabled, icons get hidden behind dock & dock does
  not hide untill there's an app near it

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  Gnome Settings>Appearance> auto hide dock //enable it

  automatically you might see icons getting hidden behind dock (keep
  windows away from dock).

  Not only desktop getting hidden under dock looks unaesthetic,
  But don't you think dock should remain hidden till the user points mouse at 
it?

  Other wise we won't be able to use left side of the desktop to keep
  icons.

  Dock never hides till an app is near it, so desktop icons may get
  under it.

  So that we can use the entire left side of desktop to keep icons, with
  the auto hide dock option enabled, don't you think dock should remain
  hidden until user points mouse near it?

  //probably a logical error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 02:14:32 2020
  DistUpgraded: 2020-05-10 12:37:12,893 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: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2019-12-13 (190 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210)
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.4.0
  dmi.board.name: 0880CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: NN_PC_NB0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0794
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/gnome-shell-extension-ubuntu-dock/+bug/1884393/+subscriptions

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


[Desktop-packages] [Bug 1877401] Re: The Italian translation is not complete

2020-06-23 Thread Brian Murray
Hello Marco, or anyone else affected,

Accepted evince into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/3.36.5-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: evince (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  The Italian translation is not complete

Status in Ubuntu Translations:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Focal:
  Fix Committed

Bug description:
  The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is
  not complete. Some items in the menu are shown in English, like "Right
  to Left Document" and "Properties".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1877401/+subscriptions

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


[Desktop-packages] [Bug 1879475] Re: SRU the current 3.36.5 stable update

2020-06-23 Thread Brian Murray
Hello Sebastien, or anyone else affected,

Accepted evince into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/3.36.5-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: evince (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.5 stable update

Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evince/-/blob/master/NEWS

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Open some pdf and ps documents, check that they render properly

  
  * Regression potential

  There is no specific change or feature to test in this update

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

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


[Desktop-packages] [Bug 1884813] [NEW] gvfs truncates files in ftp and ftps

2020-06-23 Thread Nathan Baumann
Public bug reported:

Xubuntu 20.04 LTS
Kernel linux: 5.4.0-37-generic
gvfs version: 1.44.1-1ubuntu1

This bug occurs when I connect to a ftp server through the files manager
(test with thunar and pcmanFM) and I open a file with a text editor
(test with sublime text 3 and Mousepad).

Sometimes when I save the file, it is send truncated to the server (ex:
4KiB instead of 6KiB or 160KiB instead of 235KiB). Save again the file
(even after a change) don't fix it. I must copy my file content, close
the file, re-open it from the file manager, paste content and try again
to save.

It seems don't have problem with SFTP (ssh) protocol. Just the FTP and
FTPS ones.

It isn't a server problem because there is no problem with other FTP
client like Filezilla.

** Affects: gvfs (Ubuntu)
 Importance: Undecided
 Status: 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/1884813

Title:
  gvfs truncates files in ftp and ftps

Status in gvfs package in Ubuntu:
  New

Bug description:
  Xubuntu 20.04 LTS
  Kernel linux: 5.4.0-37-generic
  gvfs version: 1.44.1-1ubuntu1

  This bug occurs when I connect to a ftp server through the files
  manager (test with thunar and pcmanFM) and I open a file with a text
  editor (test with sublime text 3 and Mousepad).

  Sometimes when I save the file, it is send truncated to the server
  (ex: 4KiB instead of 6KiB or 160KiB instead of 235KiB). Save again the
  file (even after a change) don't fix it. I must copy my file content,
  close the file, re-open it from the file manager, paste content and
  try again to save.

  It seems don't have problem with SFTP (ssh) protocol. Just the FTP and
  FTPS ones.

  It isn't a server problem because there is no problem with other FTP
  client like Filezilla.

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

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


[Desktop-packages] [Bug 1884800] Re: /usr/libexec/xdg-desktop-portal-gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

2020-06-23 Thread Sergio Schvezov
This works fine if I move to -kde

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

Title:
  /usr/libexec/xdg-desktop-portal-
  
gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1884800/+subscriptions

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


[Desktop-packages] [Bug 1884800] Re: /usr/libexec/xdg-desktop-portal-gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

2020-06-23 Thread Sergio Schvezov
In my case I have:

- snap install firefox (with https://github.com/sprig/org-capture-extension)
- snap install emacs --beta
- org-protocol on emacs (attached desktop file)
- ran "xdg-mime default org-protocol.desktop x-scheme-handler/org-protocol"

Using the extension from firefox makes it crash

** Attachment added: "org-protocol.desktop"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1884800/+attachment/5386528/+files/org-protocol.desktop

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

Title:
  /usr/libexec/xdg-desktop-portal-
  
gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1884800/+subscriptions

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


[Desktop-packages] [Bug 1884428] Re: calculater not open

2020-06-23 Thread Abir
Please see #11 images.

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

Title:
  calculater not open

Status in gnome-calculator package in Ubuntu:
  Incomplete

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1881586] Re: Add support for the new NVIDIA -server driver series

2020-06-23 Thread Alberto Milone
** Description changed:

- Add support for the new NVIDIA -server series to the ubuntu-drivers
- tool.
+ SRU Request:
+ 
+ [Test Case]
+ 
+ 1) Enable the -proposed repository, and install the new ubuntu-drivers-
+ common (0.8.4~0.20.04.1).
+ 
+ 2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
+ drivers install nvidia:440", if your card is supported by the driver)
+ 
+ 3) Restart your computer, and see if everything works correctly when
+ accessing the desktop.
+ 
+ 4) Remove all the nvidia drivers:
+ sudo apt-get --purge remove '*nvidia*'
+ 
+ 5) Test the auto-detection:
+ ubuntu-drivers install
+ 
+ 6) Restart your computer, and see if everything works correctly when
+ accessing the desktop.
+ 
+ 7) Check that the correct driver was installed for your card:
+ ubuntu-drivers debug
+ 
+ [Regression Potential]
+ Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.
+ 
+ __
+ Add support for the new NVIDIA -server series to the ubuntu-drivers tool.
  
  Also add support for specifying a driver series (as already possible
  with the --gpgpu argument, for computing use cases).

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In Progress

Bug description:
  SRU Request:

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

  __
  Add support for the new NVIDIA -server series to the ubuntu-drivers tool.

  Also add support for specifying a driver series (as already possible
  with the --gpgpu argument, for computing use cases).

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

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


[Desktop-packages] [Bug 1884428] Re: calculater not open

2020-06-23 Thread Ken VanDine
Please check which interfaces are connected and paste the output of:

snap connections gnome-calculator

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

Title:
  calculater not open

Status in gnome-calculator package in Ubuntu:
  Incomplete

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems

2020-06-23 Thread Alberto Milone
** Description changed:

- In bug 1875339, a depends on dpkg-dev was added. This is pulling in all
- of build-essential on upgrades (or just binutils and make and patch if
- you pass --no-install-recommends).
+ SRU Request:
+ 
+ [Test Case]
+ 
+ 1) Uninstall the dpkg-dev package.
+ 
+ 2) Enable the -proposed repository, and install the new ubuntu-drivers-
+ common (0.8.4~0.20.04.1).
+ 
+ 3) Check that the dpkg-dev package was not installed.
+ 
+ 3) Restart your computer, and see if everything works correctly when
+ accessing the desktop.
+ 
+ [Regression Potential]
+ Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
+ ___
+ In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).
  
  This needs to be reverted and fixed differently.

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Triaged

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

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

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


[Desktop-packages] [Bug 1871864] Re: Toggle "Fractional Scaling" does nothing on wayland

2020-06-23 Thread Sebastien Bacher
** Description changed:

- System: Ubuntu Focal Fossa (Development Branch) 20.04
+ * Impact 
+ In the setting there is option called "Fractional Scaling" but this option 
only works for X11.
  
- Version of "gnome-control-center": 1:3.36.1-1ubuntu4
+ * Test Case
+ Enable the experimental scaling option in settings and verify that non 
integer values are listed in the choices
  
- In the setting there is option called "Fractional Scaling" but this
- option only works for X11.
- 
- What is the problem:
- Enabling "Fractional Scaling" adds only ['x11-randr-fractional-scaling'] but 
['scale-monitor-framebuffer']
- 
- What it should be:
- Enabling "Fractional Scaling" in the setting adds parameter for both X11 and 
wayland:
- ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: gnome-control-center 1:3.36.1-1ubuntu4
- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
- Uname: Linux 5.4.0-21-generic x86_64
- ApportVersion: 2.20.11-0ubuntu25
- Architecture: amd64
- CurrentDesktop: ubuntu:GNOME
- Date: Thu Apr  9 23:43:57 2020
- InstallationDate: Installed on 2020-04-04 (5 days ago)
- InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
- SourcePackage: gnome-control-center
- UpgradeStatus: No upgrade log present (probably fresh install)
+ * Regression potential
+ Check that turning the option on and off works in xorg and wayland

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

Title:
  Toggle "Fractional Scaling" does nothing on wayland

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  * Impact 
  In the setting there is option called "Fractional Scaling" but this option 
only works for X11.

  * Test Case
  Enable the experimental scaling option in settings and verify that non 
integer values are listed in the choices

  * Regression potential
  Check that turning the option on and off works in xorg and wayland

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

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


[Desktop-packages] [Bug 1876937] Re: Dock location reversed in RTL

2020-06-23 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
  he dock location is horizontally reversed, selecting left puts the dock
  to the right and vice versa.
+ 
+ 
+ * Test Case
  
  Steps to reproduce (Ubuntu 20.04):
  
  1. Switch to an RTL language of your choice
  
  2. Open GNOME Settings
  
  3. Observe the Appearance icon (The default dock location is to the
  right while the icon shows as if it's to the left)
  
  4. The selection says "Left" (שמאל in Hebrew) yet the dock is aligned to
  the right, selecting the opposite option moves the dock to the left
  although I selected "Right" (ימין in Hebrew).
+ 
+ 
+ * Regression potential
+ 
+ Check that the position setting does match what the dock is doing

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

Title:
  Dock location reversed in RTL

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  * Impact

  he dock location is horizontally reversed, selecting left puts the
  dock to the right and vice versa.

  
  * Test Case

  Steps to reproduce (Ubuntu 20.04):

  1. Switch to an RTL language of your choice

  2. Open GNOME Settings

  3. Observe the Appearance icon (The default dock location is to the
  right while the icon shows as if it's to the left)

  4. The selection says "Left" (שמאל in Hebrew) yet the dock is aligned
  to the right, selecting the opposite option moves the dock to the left
  although I selected "Right" (ימין in Hebrew).

  
  * Regression potential

  Check that the position setting does match what the dock is doing

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

-- 
Mailing list: https://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 1884384] Re: in high contrast mode the calendar display uncomfortable

2020-06-23 Thread Talgat
Hi!
[image: image.png]

you see that is very hard to see weekend days as well as weeks name first
letters and the number of weeks

пн, 22 июн. 2020 г. в 08:55, Daniel van Vugt
<1884...@bugs.launchpad.net>:

> I can't see a problem on my machine. Can you attach a screenshot or
> photo showing what you mean?
>
> ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1884384
>
> Title:
>   in high contrast mode the calendar display uncomfortable
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   in high contrast mode the calendar display uncomfortable
>
>   i.e. the weekends and the column with the number of week are very hard
>   to comprehend :(
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.3
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Jun 20 21:33:05 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
> [VGA controller])
>  Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb]
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 174f:241a Syntek EasyCamera
>Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications
>Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: LENOVO 81FL
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic
> root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash
> resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/24/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7ZCN29WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: NO DPK
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo ideapad 330-17ICH
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:svnLENOVO:pn81FL:pvrLenovoideapad330-17ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-17ICH:
>   dmi.product.family: ideapad 330-17ICH
>   dmi.product.name: 81FL
>   dmi.product.sku: LENOVO_MT_81FL_BU_idea_FM_ideapad 330-17ICH
>   dmi.product.version: Lenovo ideapad 330-17ICH
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   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/gnome-shell/+bug/1884384/+subscriptions
>


-- 


С уважением,
Хаиров Талгат!


** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/1884384/+attachment/5386524/+files/image.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/1884384

Title:
  in high contrast mode the calendar display uncomfortable

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  in high contrast mode the calendar display uncomfortable

  i.e. the weekends and the column with the number of week are very hard
  to comprehend :(

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 21:33:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 

[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling

2020-06-23 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ Scaling is not reverted properly (appears shrunk) when disabling
+ fractional scaling
+ 
+ 
+ * Test Case
+ 
  Do this in an Ubuntu/Xorg session:
  
  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle
  
  Now everything is shrunk - it's not been returned to 100% properly. See
  the attached screenshot where the text is tiny instead of regular 100%
  size. If you do this instead of step 5:
  
  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle
  
  Then everything returns to the normal size.
  
  I'm on nvidia(-440), but Séb said that he saw this on his Intel machine
  too.
  
+ 
+ * Regression potential
+ 
+ Verify that scaling changes are correctly applied on different setup
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  * Impact

  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

  
  * Test Case

  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  
  * Regression potential

  Verify that scaling changes are correctly applied on different setup

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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


[Desktop-packages] [Bug 1877108] Re: Ubuntu Dock appears on the display opposite to that indicated on Appearance tab

2020-06-23 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu Focal)
   Importance: Undecided => Low

** Description changed:

- I am unable to use ubuntu-bug to raise this report as I have upgraded to
- a new version in -proposed to test bug 1866088. This issue was not
- addressed in that bug fix.
+ * Impact
  
- paul@n1644:~$ apt policy gnome-control-center
- gnome-control-center:
-   Installed: 1:3.36.2-0ubuntu1
-   Candidate: 1:3.36.2-0ubuntu1
-   Version table:
-  *** 1:3.36.2-0ubuntu1 100
- 100 /var/lib/dpkg/status
-  1:3.36.1-1ubuntu5 500
- 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ The screen labels displayed when settigns are open are inverted
  
- I am using a a laptop with an external monitor set up as follows:
+ * Test Case
  
  Display 1 is the laptop's built-in monitor
  Display 2 is the external monitor set as being the primary display
  
  To reproduce:
  
  1) Go to the Appearance tab
  2) "Show on" will indicate on which display the dock is being shown
  3) In my case it is set to "1. Built in display" but it appears on the second 
or primary display
  4) Change the setting and the dock will move but...
  5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears 
on the built-in display.
+ 
+ 
+ * Regression potential
+ 
+ Checking that in settings -> display the screen labels are correct

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

Title:
  Ubuntu Dock appears on the display opposite to that indicated on
  Appearance tab

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  * Impact

  The screen labels displayed when settigns are open are inverted

  * Test Case

  Display 1 is the laptop's built-in monitor
  Display 2 is the external monitor set as being the primary display

  To reproduce:

  1) Go to the Appearance tab
  2) "Show on" will indicate on which display the dock is being shown
  3) In my case it is set to "1. Built in display" but it appears on the second 
or primary display
  4) Change the setting and the dock will move but...
  5) In my case if I change to "2. GKE 24 (Primary display)" the dock appears 
on the built-in display.

  
  * Regression potential

  Checking that in settings -> display the screen labels are correct

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

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


[Desktop-packages] [Bug 1876891] Re: The fractional scaling toggle applies instantly and not when "Apply" is pressed

2020-06-23 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ The fractional scaling toggle applies instantly and not when "Apply" is
+ pressed
+ 
+ * Test Case
+ 
  Do this when in an Xorg/Ubuntu session:
  
  0. Have fractional scaling disabled and set to 100%
  1. Go to gnome-control-center -> displays
  2. Turn on the fractional scaling toggle
  3. Select 125%
  4. Press apply (the scaling should apply correctly)
  5. Turn off the toggle
  6. Turn the toggle back on
  
  At 5 and 6, the scaling changes. It shouldn't - this should only happen
  when you press 'Apply'. The toggle needs to not be directly connected to
  GSettings.
+ 
+ * Regression potential
+ 
+ Check that screen settings changed are correctly applied and only when
+ clicking the corresponding button
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:35:48 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

Title:
  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress

Bug description:
  * Impact

  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

  * Test Case

  Do this when in an Xorg/Ubuntu session:

  0. Have fractional scaling disabled and set to 100%
  1. Go to gnome-control-center -> displays
  2. Turn on the fractional scaling toggle
  3. Select 125%
  4. Press apply (the scaling should apply correctly)
  5. Turn off the toggle
  6. Turn the toggle back on

  At 5 and 6, the scaling changes. It shouldn't - this should only
  happen when you press 'Apply'. The toggle needs to not be directly
  connected to GSettings.

  * Regression potential

  Check that screen settings changed are correctly applied and only when
  clicking the corresponding button

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:35:48 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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


[Desktop-packages] [Bug 1884803] [NEW] SRU the current 3.36.2 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that calendar editing works. Add an online account (google for
example) is settings and see that the local calendar is correctly
listing the events. Check that events are listed in the GNOME indicator

* Regression potential

The are some changes are start of week and event time calculation, make
sure all day events are on right days and that timed events are
correctly displayed

** Affects: gnome-calendar (Ubuntu)
 Importance: Low
 Status: Fix Released

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  SRU the current 3.36.2 stable update

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that calendar editing works. Add an online account (google for
  example) is settings and see that the local calendar is correctly
  listing the events. Check that events are listed in the GNOME
  indicator

  * Regression potential

  The are some changes are start of week and event time calculation,
  make sure all day events are on right days and that timed events are
  correctly displayed

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

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


[Desktop-packages] [Bug 1884682] Re: gtk_range_expose can set height/width < -1 when trough-under-steppers is enabled

2020-06-23 Thread Sebastien Bacher
Thank you for your bug report and patch, has that been submitted
upstream? If not could you do that and share the url?

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

Title:
  gtk_range_expose can set height/width < -1 when trough-under-steppers
  is enabled

Status in light-themes:
  New
Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The root cause of https://github.com/mate-desktop/mate-themes/issues/57 and 
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/538541 
(murrine_style_draw_box: assertion `height >= -1' failed) is gtk_range_expose 
not clamping height and width to a sane value if trough-under-steppers is 
enabled, the window is very small (like in init), and the theme has non-zero 
offsets.
  The attached patch should solve the problem (based on 2.24.32-1ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-themes/+bug/1884682/+subscriptions

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


[Desktop-packages] [Bug 1884801] [NEW] SRU the current 2.56.1 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some build and test fixes
https://gitlab.gnome.org/GNOME/glib-networking/-/blob/glib-2-56/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that the glib networking still works correctly by using epiphany
browser and visit some website and set up evolution to check an email
account

* Regression potential

The update is mostly intended to fix the autopkgtest that started
failing with gnults28 security updates, we are going to block in
proposed since there is no real change benefiting users

** Affects: glib-networking (Ubuntu)
 Importance: Low
 Status: Fix Released


** Tags: block-proposed-bionic

** Changed in: glib-networking (Ubuntu)
   Status: New => Fix Released

** Changed in: glib-networking (Ubuntu)
   Importance: Undecided => Low

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

Title:
  SRU the current 2.56.1 stable update

Status in glib-networking package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some build and test fixes
  https://gitlab.gnome.org/GNOME/glib-networking/-/blob/glib-2-56/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the glib networking still works correctly by using epiphany
  browser and visit some website and set up evolution to check an email
  account

  * Regression potential

  The update is mostly intended to fix the autopkgtest that started
  failing with gnults28 security updates, we are going to block in
  proposed since there is no real change benefiting users

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

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


[Desktop-packages] [Bug 1884800] [NEW] /usr/libexec/xdg-desktop-portal-gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

2020-06-23 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy

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

Title:
  /usr/libexec/xdg-desktop-portal-
  
gtk:11:__strcmp_avx2:ensure_default_is_below:app_chooser_dialog_new:handle_choose_application:ffi_call_unix64

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1884800/+subscriptions

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


[Desktop-packages] [Bug 1884536] Re: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04

2020-06-23 Thread Charles Brittain
** Package changed: ubuntu => gpm (Ubuntu)

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

Title:
  Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04

Status in gpm package in Ubuntu:
  New

Bug description:
  I have relatively recently loaded Ubuntu 20.04 to dual-boot on a
  Packard Bell with Windows 10 Home 64-bit already installed. The mouse-
  pointer moves and clicks perfectly when the PC has a single-monitor.
  However, for work as a developer, I should like to use a dual-monitor
  setup.

  The problem I have is, if I plug in to the PC tower a second monitor
  and follow the steps to Connect Another Monitor To My Computer
  (https://help.ubuntu.com/stable/ubuntu-help/display-dual-
  monitors.html), and after I confirm "join Display", the mouse-pointer
  jumps about and a second stationary mouse-pointer appears in the
  bottom right of my primary screen. This behaviour stops immediately I
  confirm "Single Display", but now the second screen is now turned
  blank.

  $ xinput
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ USB Wired Keyboard Consumer Control   id=12   [slave  pointer  (2)]
  ⎜   ↳ PixArt USB Optical Mouse  id=13   [slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Power Button  id=8[slave  keyboard (3)]
  ↳ Sleep Button  id=9[slave  keyboard (3)]
  ↳ USB Wired Keyboardid=10   [slave  keyboard (3)]
  ↳ USB Wired Keyboard System Control id=11   [slave  keyboard (3)]
  ↳ USB Wired Keyboard Consumer Control   id=14   [slave  keyboard (3)]

  $ sudo dmidecode -t 1
  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Packard Bell
  Product Name: iMedia S2984
  Version: 
  Serial Number: DTU96EK00360103D0F3000
  UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd
  Wake-up Type: Power Switch
  SKU Number:  
  Family: Packard Bell Desktop

  $ lsb_release -a; uname -a; lsusb
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal
  Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 
18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 
(SD/SDHC/SDXC) Card Reader
  Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard 
Model KBAY211
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I am reporting this as a bug because I am unable to fix it and I have
  asked around, but no joy. I do need a dual-monitor set p for work.
  Currently, I can use Windows10 with dual-monitors, on the same
  machine, without a glitch.

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

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


[Desktop-packages] [Bug 1884799] [NEW] SRU the current 3.36.2 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that calendar editing works. Add an online account (google for
example) is settings and see that the local calendar is correctly
listing the events. Check that events are listed in the GNOME indicator

* Regression potential

The are some changes are start of week and event time calculation, make
sure all day events are on right days and that timed events are
correctly displayed

** Affects: gnome-calendar (Ubuntu)
 Importance: Low
 Status: Fix Released

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

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

Title:
  SRU the current 3.36.2 stable update

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that calendar editing works. Add an online account (google for
  example) is settings and see that the local calendar is correctly
  listing the events. Check that events are listed in the GNOME
  indicator

  * Regression potential

  The are some changes are start of week and event time calculation,
  make sure all day events are on right days and that timed events are
  correctly displayed

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

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


[Desktop-packages] [Bug 1884536] [NEW] Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04

2020-06-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have relatively recently loaded Ubuntu 20.04 to dual-boot on a Packard
Bell with Windows 10 Home 64-bit already installed. The mouse-pointer
moves and clicks perfectly when the PC has a single-monitor. However,
for work as a developer, I should like to use a dual-monitor setup.

The problem I have is, if I plug in to the PC tower a second monitor and
follow the steps to Connect Another Monitor To My Computer
(https://help.ubuntu.com/stable/ubuntu-help/display-dual-monitors.html),
and after I confirm "join Display", the mouse-pointer jumps about and a
second stationary mouse-pointer appears in the bottom right of my
primary screen. This behaviour stops immediately I confirm "Single
Display", but now the second screen is now turned blank.

$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ USB Wired Keyboard Consumer Control   id=12   [slave  pointer  (2)]
⎜   ↳ PixArt USB Optical Mouse  id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ USB Wired Keyboardid=10   [slave  keyboard (3)]
↳ USB Wired Keyboard System Control id=11   [slave  keyboard (3)]
↳ USB Wired Keyboard Consumer Control   id=14   [slave  keyboard (3)]

$ sudo dmidecode -t 1
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Packard Bell
Product Name: iMedia S2984
Version: 
Serial Number: DTU96EK00360103D0F3000
UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd
Wake-up Type: Power Switch
SKU Number:  
Family: Packard Bell Desktop

$ lsb_release -a; uname -a; lsusb
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal
Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 
18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 
(SD/SDHC/SDXC) Card Reader
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard 
Model KBAY211
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I am reporting this as a bug because I am unable to fix it and I have
asked around, but no joy. I do need a dual-monitor set p for work.
Currently, I can use Windows10 with dual-monitors, on the same machine,
without a glitch.

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


** Tags: bot-comment
-- 
Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
https://bugs.launchpad.net/bugs/1884536
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gpm 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 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin

2020-06-23 Thread Sebastien Bacher
@it has been moved back to universe in focal, eoan isn't supported
anymore and it's not a component desktop is using or interested in, I'm
unsubscribing desktop-packages now. If it's promoted back one of the
teams looking after rsync should subscribe

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

Title:
  [MIR] teckit & xxhash, new rdeps of texlive-bin

Status in teckit package in Ubuntu:
  Fix Released
Status in xxhash package in Ubuntu:
  Incomplete

Bug description:
  teckit & xxhash, new rdeps of texlive-bin

  teckit was formerly bundled in texlive-bin (I believe)

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

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


[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)

2020-06-23 Thread Zygmunt Krynicki
I'm marking this as medium as we should handle ipv6 better and this may
help to determine if there's a broad issue in the base snaps, either on
the configuration side or in the set of packages contained.

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  chromium snap from focal fails DNS lookups, or delays them (ipv6)

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When working with the chromium snap included in focal, it sometimes
  takes a few seconds to lookup an URL, sometimes it cannot resolve the
  hostname of the URL at all.

  Doing the same browsing using firefox doesn't show such behavior, no
  timeouts, no failed lookups, no delays.

  Any way how to debug that?  That is using IPv6 only.

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

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


[Desktop-packages] [Bug 1884101] Re: [SRU] jackdbus produces high cpu load

2020-06-23 Thread Sebastien Bacher
Oh, I see it's in the review queue so I'm going to set as fix commited
and reassign

** Changed in: jackd2 (Ubuntu Focal)
 Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)

** Changed in: jackd2 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  Fix Committed
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1884792] [NEW] SRU the current 3.36.2 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that calendar editing works. Add an online account (google for
example) is settings and see that the local calendar is correctly
listing the events. Check that events are listed in the GNOME indicator

* Regression potential

The are some changes are start of week and event time calculation, make
sure all day events are on right days and that timed events are
correctly displayed

** Affects: gnome-calendar (Ubuntu)
 Importance: Low
 Status: Fix Released

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  SRU the current 3.36.2 stable update

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that calendar editing works. Add an online account (google for
  example) is settings and see that the local calendar is correctly
  listing the events. Check that events are listed in the GNOME
  indicator

  * Regression potential

  The are some changes are start of week and event time calculation,
  make sure all day events are on right days and that timed events are
  correctly displayed

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

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


[Desktop-packages] [Bug 1884428] Re: calculater not open

2020-06-23 Thread Abir
I open terminal and type gnome-calculator
Then show error massage

** Attachment added: "15929215513745778646801554491876.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+attachment/5386467/+files/15929215513745778646801554491876.jpg

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

Title:
  calculater not open

Status in gnome-calculator package in Ubuntu:
  Incomplete

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-23 Thread ThOR27
Hi, tried the new package, it didn't fixed, changed 100% to 125% and it
scaled to 200%. The output of the mentioned command:

jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 
0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@59.972618103027344', 
{'underscanning': })])]
jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 
0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@59.972618103027344', 
{'underscanning': })])]
jun 23 10:17:15 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 
0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@59.972618103027344', 
{'underscanning': })])]
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: GOt configuration change [(0, 
0, 1.25, uint32 0, true, [('HDMI-0', '3440x1440@59.972618103027344', 
{'underscanning': })])]
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Crtc at 0,00x0,00 size 
2752,00x1152,00 (@ 1,25 - adapted 2,00) considering it of 
5504,00x2304,00
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size 5504x2304
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size to 5504x2304
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Scaling at 0,625000 
(transformation matrix is 104857 = 1,51) using filter good
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Configuring CRTC 633 with mode 
640 (3440 x 1440 @ 59,972618) at position 0, 0 and transform 0
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting UBUNTU crtc config crtc 
633, timestamp 0 (config timestamp 319695), x: 0, y: 0, mode: 640, rotation 1, 
n_outputs 1: RETURN reply 0x5650ad5b5ea0, error: (nil)
jun 23 10:17:18 Z68MA-D2H-B3 gnome-shell[5236]: Setting screen size 5504x2304
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
jun 23 10:17:19 Z68MA-D2H-B3 gnome-shell[5236]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-23 Thread Vitaly Sulimov
@3v1n0 
xrandr also command doesn't work for me (laptop with GeForce MX250 and Intel 
GPU). Getting extended desktop instead of scaling as you mention in #119

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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


[Desktop-packages] [Bug 177929] Re: Should autodetect filename character encoding in zip files

2020-06-23 Thread Unxed
*** This bug is a duplicate of bug 580961 ***
https://bugs.launchpad.net/bugs/580961

Wrote a patch for unzip fixing this issue:
https://sourceforge.net/p/infozip/patches/29/

The same patch for p7zip:
https://sourceforge.net/p/p7zip/bugs/187/

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

Title:
  Should autodetect filename character encoding in zip files

Status in file-roller package in Ubuntu:
  Triaged
Status in xarchiver package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: file-roller

  Many compressed file such as zip don't specify filename encoding. But
  file-roller read every file as UTF-8, so it sometimes makes encoding
  problem.

  I think may be, you could think that it's not a big problem or it's
  not a bug or we don't need those feature. If you deal with only
  English it's not a problem at all. But it's a big problem for East
  Asian people such as Chinese, Japanese and Korean. Because zip file is
  still popular. And many people compress zip file in Windows, and share
  the zip files. Windows don't use UTF-8.

  Many CJK people want to uncompress these zip files. There are some way
  to solve this problem (by another software). But all are too complex
  to Ubuntu newbies. I wish file-roller support encoding select
  function.

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

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


[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-23 Thread se4n
@3v1n0

That worked for me...

- Ubuntu 20.04 
- NVIDIA driver 440
- NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)

jun 23 10:37:54 se4n-lx gnome-shell[2514]: GNOME Shell started at Tue Jun 23 
2020 10:37:50 GMT-0300 (-03)
jun 23 10:37:54 se4n-lx gnome-shell[2514]: Registering session with GDM
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Received error from D-Bus search 
provider org.gnome.seahorse.Application.desktop during GetResultMetas: 
Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Wrong number of result metas 
returned by search provider org.gnome.seahorse.Application.desktop: expected 1 
but got 0
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Received error from D-Bus search 
provider org.gnome.seahorse.Application.desktop during GetResultMetas: 
Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface “org.gnome.Shell.SearchProvider2” on object at path 
/org/gnome/seahorse/Application
jun 23 10:38:16 se4n-lx gnome-shell[2514]: Wrong number of result metas 
returned by search provider org.gnome.seahorse.Application.desktop: expected 1 
but got 0
jun 23 10:38:18 se4n-lx gnome-shell[2514]: Received error from D-Bus search 
provider org.gnome.seahorse.Application.desktop during GetResultMetas: 
Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface “org.gnome.Shell.SearchProvider2” on object at path 
/org/gnome/seahorse/Application
jun 23 10:38:18 se4n-lx gnome-shell[2514]: Wrong number of result metas 
returned by search provider org.gnome.seahorse.Application.desktop: expected 1 
but got 0
jun 23 10:38:30 se4n-lx gnome-shell[2514]: Enabling experimental feature 
'x11-randr-fractional-scaling'
jun 23 10:38:30 se4n-lx gnome-shell[2514]: Setting screen size 3840x2160
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 
1.25, uint32 0, true, [('DP-2', '3840x2160@59.996623992919922', 
{'underscanning': })])]
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 
1.25, uint32 0, true, [('DP-2', '3840x2160@59.996623992919922', 
{'underscanning': })])]
jun 23 10:38:31 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 
1.25, uint32 0, true, [('DP-2', '3840x2160@59.996623992919922', 
{'underscanning': })])]
jun 23 10:38:38 se4n-lx gnome-shell[2514]: GOt configuration change [(0, 0, 
1.25, uint32 0, true, [('DP-2', '3840x2160@59.996623992919922', 
{'underscanning': })])]
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Crtc at 0,00x0,00 size 
3072,00x1728,00 (@ 1,25 - adapted 2,00) considering it of 
6144,00x3456,00
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size 6144x3456
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size to 6144x3456
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Scaling at 0,625000 (transformation 
matrix is 104857 = 1,51) using filter good
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Configuring CRTC 441 with mode 450 
(3840 x 2160 @ 59,996624) at position 0, 0 and transform 0
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting UBUNTU crtc config crtc 441, 
timestamp 0 (config timestamp 3934331), x: 0, y: 0, mode: 450, rotation 1, 
n_outputs 1: RETURN reply 0x5652266ca5c0, error: (nil)
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size 6144x3456
jun 23 10:38:38 se4n-lx gnome-shell[2514]: Setting screen size 6144x3456

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Desktop-packages] [Bug 1881699] Re: No analog output

2020-06-23 Thread Sebastien Bacher
@jibel said he would test the newest pulseaudio to see if that fix his
issue

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

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

Title:
  No analog output

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Desktop-packages] [Bug 1863282] Re: libreoffice menu bar disappeared

2020-06-23 Thread Sebastien Bacher
while it sounds like worth fixing it's not impacting our default desktop
and didn't get lot of reports or activity so we aren't going to consider
it as a rls issue

** Tags removed: rls-gg-incoming
** Tags added: rls-gg-notfixing

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

Title:
  libreoffice  menu bar disappeared

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
  KDE neon User Edition 5.18 18.04
  libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
  libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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


[Desktop-packages] [Bug 1884101] Re: [SRU] jackdbus produces high cpu load

2020-06-23 Thread Sebastien Bacher
Erich, you unassigned yourself, do you plan to work on that fix for
focal?

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  In Progress
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Desktop-packages] [Bug 1883920] Re: ubuntu logo in wslfetch needs update

2020-06-23 Thread Sebastien Bacher
** Changed in: wslu (Ubuntu Focal)
 Assignee: (unassigned) => Patrick Wu (callmepk)

** Changed in: wslu (Ubuntu Bionic)
 Assignee: (unassigned) => Patrick Wu (callmepk)

** Changed in: wslu (Ubuntu Xenial)
 Assignee: (unassigned) => Patrick Wu (callmepk)

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

Title:
  ubuntu logo in wslfetch needs update

Status in wslu package in Ubuntu:
  Fix Committed
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Focal:
  New
Status in wslu source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  This affects all wslu tools on all releases. The Ubuntu branding is
  the outdated version:
  https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png

  [Test Case]

   * Install Ubuntu WSL and install this fix.
   * run wslfetch command.
   * new logo should be shown like the following: 
https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png

  [Regression Potential]

  * None for now.

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

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


[Desktop-packages] [Bug 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed

2020-06-23 Thread Sebastien Bacher
** Changed in: wslu (Ubuntu Focal)
 Assignee: (unassigned) => Patrick Wu (callmepk)

** Changed in: wslu (Ubuntu Bionic)
 Assignee: (unassigned) => Patrick Wu (callmepk)

** Changed in: wslu (Ubuntu Xenial)
 Assignee: (unassigned) => Patrick Wu (callmepk)

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

Title:
  Ubuntu.exe will not be detected properly if other LTS version is
  installed

Status in wslu package in Ubuntu:
  Fix Committed
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Focal:
  New
Status in wslu source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  This affects all wslu tools on all releases when using from the Ubuntu
  app from Microsoft Store. When other LTS version of app is installed
  from Microsoft Store, baseexec generated by wslu on Ubuntu app will
  not be using ubuntu.exe but other LTS release apps (such as
  ubuntu1804.exe)

  [Test Case]

   * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store.
   * run any wslu tools (like wslfetch --help)
   * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe

  [Regression Potential]

  * None for now.

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

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


[Desktop-packages] [Bug 1884772] [NEW] SRU the current 3.36.3.1 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some translation updates
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that a GNOME session still works correctly, including changing the
background image, locale and screen settings. The GNOME version in
setting should also be 3.36.3

* Regression potential

The update has some test and translations fixes and a change to the
thumbnailing, check that nautilus still previews images correctly

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

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

Title:
  SRU the current 3.36.3.1 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.3

  * Regression potential

  The update has some test and translations fixes and a change to the
  thumbnailing, check that nautilus still previews images correctly

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

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


[Desktop-packages] [Bug 1884774] [NEW] SRU the current 3.36.3.1 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some translation updates
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that a GNOME session still works correctly, including changing the
background image, locale and screen settings. The GNOME version in
setting should also be 3.36.3

* Regression potential

The update has some test and translations fixes and a change to the
thumbnailing, check that nautilus still previews images correctly

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

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

Title:
  SRU the current 3.36.3.1 stable update

Status in gnome-desktop3 package in Ubuntu:
  Invalid

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.3

  * Regression potential

  The update has some test and translations fixes and a change to the
  thumbnailing, check that nautilus still previews images correctly

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

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


[Desktop-packages] [Bug 1884775] [NEW] SRU the current 3.36.3.1 stable update

2020-06-23 Thread Sebastien Bacher
Public bug reported:

* Impact
That's the current GNOME stable update, including some translation updates
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that a GNOME session still works correctly, including changing the
background image, locale and screen settings. The GNOME version in
setting should also be 3.36.3

* Regression potential

The update has some test and translations fixes and a change to the
thumbnailing, check that nautilus still previews images correctly

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Low
 Status: Fix Released

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  SRU the current 3.36.3.1 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.3

  * Regression potential

  The update has some test and translations fixes and a change to the
  thumbnailing, check that nautilus still previews images correctly

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

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


[Desktop-packages] [Bug 1688592]

2020-06-23 Thread Stransky
This needs to be closed to claim the bounty at
https://www.bountysource.com/issues/55506502-meta-add-va-api-hardware-
decoding-support-on-linux so closing this one.

Wayland va-api decoding was implemented by Bug 1616185
X11 variant is pending at Bug 1619523

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


[Desktop-packages] [Bug 1688592]

2020-06-23 Thread Stransky
(In reply to Robert Mader [:rmader] from comment #35)
> (In reply to eric.riese from comment #34)
> > 
> > In my opinion the bounty was already earned when this issue was resolved 
> > but I don't know who gets to be the arbiter.
> 
> That would certainly be Martin Stránský :)
> Martin, do you want to claim the bounty? If you don't care about it / don't 
> need it yourself, you could donate it or so.

Okay, I'll try to claim it and send it to a charity.

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


[Desktop-packages] [Bug 1688592]

2020-06-23 Thread Mathew Hodson
This should depend on bug 1616185 and bug 1619523 so it's easier to find
where the work happened.

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


[Desktop-packages] [Bug 1688592]

2020-06-23 Thread Eric Riese
Reminder that there is still a bounty for this issue at BountySource

https://www.bountysource.com/issues/55506502-add-va-api-hardware-
decoding-support-on-linux

I got an email from BountySource that they're going to start taking old
bounties for themselves starting *2020-07-1* (reproduced below)

In my opinion the bounty was already earned when this issue was resolved
but I don't know who gets to be the arbiter.

```
Hi, 
You are receiving this email because we are updating the Bountysource Terms of 
Service, effective 1st July 2020.

What's changing?
We have added a Time-Out clause to the Bounties section of the agreement:

2.13 Bounty Time-Out. 
If no Solution is accepted within two years after a Bounty is posted, then the 
Bounty will be withdrawn and the amount posted for the Bounty will be retained 
by Bountysource. For Bounties posted before June 30, 2018, the Backer may 
redeploy their Bounty to a new Issue by contacting supp...@bountysource.com 
before July 1, 2020. If the Backer does not redeploy their Bounty by the 
deadline, the Bounty will be withdrawn and the amount posted for the Bounty 
will be retained by Bountysource.

You can read the full Terms of Service here

What do I need to do?
If you agree to the new terms, you don't have to do anything.  

If you have a bounty posted prior to June 30, 2018 that is not currently
being solved, email us at supp...@bountysource.com to redeploy your
bounty.  Or, if you do not agree with the new terms, please discontinue
using Bountysource.

Thanks for reading

Bountysource Team
```

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


[Desktop-packages] [Bug 1688592] Re: Missing VA-API hardware decoding support drains battery

2020-06-23 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => 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/1688592

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


[Desktop-packages] [Bug 1688592]

2020-06-23 Thread Robert Mader
(In reply to eric.riese from comment #34)
> 
> In my opinion the bounty was already earned when this issue was resolved but 
> I don't know who gets to be the arbiter.

That would certainly be Martin Stránský :)
Martin, do you want to claim the bounty? If you don't care about it / don't 
need it yourself, you could donate it or so.

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

Title:
  Missing VA-API hardware decoding support drains battery

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

Bug description:
  Current devices ship with graphics devices supporting hardware
  decoding of certain video formats. While doing that, energy can be
  saved, as the main processor can go to sleep, and the graphics devices
  do their jobs more efficiently saving energy.

  Today, the browser is used a lot to watch movies. Unfortunately, the
  Firefox browser does not support VA-API hardware decoding, which is
  the interface to be used for Intel graphics device, which are included
  in current Intel processors.

  The issue in the Mozilla bug tracker [1] is open for over two years.

  Currently, this missing feature is a major show stopper for people
  using Ubuntu GNU/Linux on their laptops, as compared to Microsoft
  Windows one battery charge(?) lasts noticeably less time.

  [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

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

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


  1   2   >