[Desktop-packages] [Bug 1852172] [NEW] Battery history and statistics graphs markings are unreadable on a dark theme

[Rahul Jaisheel]

Public bug reported:

1 - Use a dark theme using Gnome Tweaks.
2 - Open Power Statistics
3 - Click on Laptop battery -> History or Statistics tab.

The markings on the X and Y axes are not readable since the text colour
does not adapt to the dark theme.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-power-manager 3.32.0-1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 12 12:25:29 2019
ExecutablePath: /usr/bin/gnome-power-statistics
InstallationDate: Installed on 2019-10-19 (23 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Screenshot of the graph."
   
https://bugs.launchpad.net/bugs/1852172/+attachment/5304705/+files/Power%20Statistics.png

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

Title:
  Battery history and statistics graphs markings are unreadable on a
  dark theme

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  1 - Use a dark theme using Gnome Tweaks.
  2 - Open Power Statistics
  3 - Click on Laptop battery -> History or Statistics tab.

  The markings on the X and Y axes are not readable since the text
  colour does not adapt to the dark theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-power-manager 3.32.0-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 12:25:29 2019
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2019-10-19 (23 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850893] Re: chromium-browser does not resolve any names

[Sachin Garg]

Just ran a "sudo apt update" followed by "sudo apt list --upgradable"
...

chromium-browser/xenial-updates 78.0.3904.70-0ubuntu0.16.04.2 amd64
[upgradable from: 77.0.3865.120-0ubuntu1~snap1]

So, it seems that upstream has reverted to an DPKG instead of snap.

$ $ snap list
Name Version  Rev   Tracking  Publisher   Notes
chromium 78.0.3904.97 937   stablecanonical*  -

Using the snap version [Version 78.0.3904.97 (Official Build) snap
(64-bit)], I continue to get the DNS error.

However, on using the installed DPKG version [Version 78.0.3904.70
(Official Build) Built on Ubuntu , running on Ubuntu 19.10 (64-bit)],
DNS works fine.

So, this is an issue with how the SNAP packaging works.

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

Title:
  chromium-browser does not resolve any names

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  OS:
  ===
  Description:  Ubuntu 19.10
  Release:  19.10

  Chromium Browser:
  =
  Version 78.0.3904.70 (Official Build) snap (64-bit)

  
  DNS resolution does not work in Chromium Browser since Ubuntu updated from 
18.04 -> 19.10 and chromium moved from package to SNAP.

  DNS works in Mozilla Firefox (being used to submit this bug report) as
  well as in Google Chrome (Version 78.0.3904.87 (Official Build)
  (64-bit))

  See attached screenshots.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLSwNV1BaQhYdAQOANB14KlKVpVZUnSUOUFS7jACzAIHAgQCBgJUAqcABAQEBAjqAGHE4LUBYLEUACSUhAAAe/QAySB5REQAKICAgICAg/ABDMjRGMzkwCiAgICAg/wBINFpNNTAwMTE1CiAgAVMCAxrxRpAEHxMSAyMJBweDAQAAZgMMABAAgAEdALxS0B4guChVQAklIQAAHowK0JAgQDEgDEBVAAklIQAAGIwK0Iog4C0QED6WAAklIQAAGAAAyQ==
   modes: 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 
1440x900 1280x800 1280x720 1280x720 1280x720 1280x720 1280x720 1024x768 
1024x768 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5fgGAAEaAQSlHRB4AviQnllVnCYaUFQBAQEBAQEBAQEBAQEBAQEBPhxWoFAAFjAwIDYAJaUQAAAanhZWoFAAFjAwIDYAJaUQAAAaAgARQ/8PPOZBRjrmAAM=
   modes: 1366x768 1366x768
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/mapper/shoor-home xfs194G  171G   24G  88% /home
   tmpfs  tmpfs  7.8G  186M  7.6G   3% /dev/shm
   /dev/mapper/shoor-home xfs194G  171G   24G  88% /home
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-05-02 (558 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: HP HP ProBook 430 G5
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=2dbdc9ef-f608-4d62-83ff-348f47118c15 ro 
resume=UUID=ff6eebb5-8c92-4fad-af15-00ccb0e08484
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.97 
(021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859})
  Snap.ChromiumVersion: Chromium 78.0.3904.97 snap
  Tags:  eoan snap
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
tty vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 8377
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD750DHFQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook430G5:pvr:rvnHP:rn8377:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G5
  dmi.product.sku: 3EB74PA#ACJ
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852170] [NEW] Severe screen corruption

[Joseph]

Public bug reported:

Screen occasionally shows strange distortions and corruptions during almost any 
activity. Static or bars of colour appear in unusual places along the screen.
Corruptions are often (though not always) removed in some sections of the 
screen by the appearance of other display elements (windows, tooltip, 
mouse-over, etc.)

Description:Ubuntu 19.10
Release:19.10
xorg:
  Installed: 1:7.7+19ubuntu12
  Candidate: 1:7.7+19ubuntu12
  Version table:
 *** 1:7.7+19ubuntu12 500
500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 12 16:13:38 2019
DistUpgraded: 2019-11-07 18:03:17,611 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: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
InstallationDate: Installed on 2018-09-07 (430 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20KUCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro radeon.modeset=0 ivrs_ioapic[32]=00:14.0
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-11-07 (4 days ago)
dmi.bios.date: 07/16/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0UET47W (1.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KUCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET47W(1.27):bd07/16/2018:svnLENOVO:pn20KUCTO1WW:pvrThinkPadE485:rvnLENOVO:rn20KUCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E485
dmi.product.name: 20KUCTO1WW
dmi.product.sku: LENOVO_MT_20KU_BU_Think_FM_ThinkPad E485
dmi.product.version: ThinkPad E485
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption eoan ubuntu

** Attachment added: "An instance of this bug"
   
https://bugs.launchpad.net/bugs/1852170/+attachment/5304685/+files/IMG_20191110_074039.jpg

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

Title:
  Severe screen corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  Screen occasionally shows strange distortions and corruptions during almost 
any activity. Static or bars of colour appear in unusual places along the 
screen.
  Corruptions are often (though not always) removed in some sections of the 
screen by the appearance of other display elements (windows, tooltip, 
mouse-over, etc.)

  Description:  Ubuntu 19.10
  Release:  19.10
  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 16:13:38 2019
  DistUpgraded: 2019-11-07 18:03:17,611 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: eoan
  DistroVariant: 

[Desktop-packages] [Bug 1851964] Re: Volume indicator lags behind scroll action to change volume

[florin]

Actually I have found 2 reports:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1720
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1821


** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1720
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1720

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1821
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1821

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

Title:
  Volume indicator lags behind scroll action to change volume

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume with the help of the mouse/touchpad, scrolling on
  top of the sound icon used to work fine in the older versions of gnome
  shell. In Ubuntu 19.10, it does not. I scroll, but the graphic
  indicator that shows on the screen lags behind, even jumps. If needed,
  I could try to record it as video. There is definitely some
  performance issue over there.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc6-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 23:50:04 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (21 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825741] Re: [upstream] Multiple instances of global menu entries

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Fix Released => Confirmed

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

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

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

[Desktop-packages] [Bug 1825741]

[Michael Krahl]

Created attachment 155715
Screenshot ot Help screen

Here are screenshots of the Help screen and also the troublesome LO
components.

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

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

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

[Desktop-packages] [Bug 1825741]

[Michael Krahl]

Created attachment 155708
Double menus in LO ver. 6.3.3.2

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

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

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

[Desktop-packages] [Bug 1825741]

[Xiscofauli]

(In reply to the_cleaner from comment #32)
> Created attachment 155708 [details]
> Double menus in LO ver. 6.3.3.2

Could you please paste the info from Help - about LibreOffice ?

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

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

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

[Desktop-packages] [Bug 1825741]

[Michael Krahl]

Problem still appears on my system in following LO-components:
- LO manager screen 
- LO Base
- LO Math
All other components are OK
I use LO version 6.3.3.2.0, Linux kernel 5.3.10

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

Title:
  [upstream] Multiple instances  of global menu entries

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

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

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

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

[Desktop-packages] [Bug 1740180]

[Sebastian-padilla]

This is still happening on latest Nightly 72.0a1 on Ubuntu 18.04

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

Title:
  Firefox stops loading Farmville 2 and hangs.

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. 
   Farmville 2 hangs while loading. Never plays. 

  The Adobe Flash Player is properly installed. Has also been re-
  installed. Ditto for FireFox.

  Does not matter if using Ubuntu 16.04 or 17.10.

  Farmville 2 via Facebook in Firefox hangs. Also will not work if run
  from the Zynga URL (the makers of Farmville 2. Other Facebook games
  work well. Try "Pearl's Perils."

  Happy to help with testing if you like. This has been tested on both
  desktops and laptops.

  Thanks,

  Ken Wagner

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Dec 26 15:59:05 2017
  InstallationDate: Installed on 2017-03-06 (295 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ken2466 F pulseaudio
   /dev/snd/pcmC0D0p:   ken2466 F...m pulseaudio
   /dev/snd/controlC0:  ken2466 F pulseaudio
   /dev/snd/controlC2:  ken2466 F pulseaudio
  BuildID: 20180614184508
  Channel: beta
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-28 (94 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   default via 192.168.1.1 dev wlx7cdd908b43ea  proto static  metric 600 
   169.254.0.0/16 dev wlx7cdd908b43ea  scope link  metric 1000 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.10  
metric 100 
   192.168.1.0/24 dev wlx7cdd908b43ea  proto kernel  scope link  src 
192.168.1.2  metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530
  Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use)
  RunningIncompatibleAddons: False
  SubmittedCrashIDs:
   bp-61ed5f93-fc76-48cc-8c5e-05d080180530
   bp-481cf9ec-efcd-4900-93aa-4e8940180512
   bp-ad49167e-7776-4ff5-8acc-5adb50180421
   bp-08f026d0-e273-45fb-b355-c70ae0180402
  Tags: xenial third-party-packages beta-channel
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID 

[Desktop-packages] [Bug 1852166] Re: Pixel pattern error in over

[Shahar Or]

Here's a photo of the incorrect pixel pattern. From normal viewing
distance it's barely usable. Certainly not tolerable.

** Attachment added: "Greater than 60 Hz incorrect"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852166/+attachment/5304676/+files/IMG_20191112_122017.jpg

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

Title:
  Pixel pattern error in over

Status in xorg package in Ubuntu:
  New

Bug description:
  The primary monitor, Microstep 24", is capable of 144 Hz refresh rate
  and I do use that regularly in Windows 10.

  When I set the rate to anything higher than 60 Hz (120 or 144) I get a
  wrong pixel pattern. See attached photos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 12:06:45 2019
  DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390]
  InstallationDate: Installed on 2010-10-12 (3317 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root 
ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun May 13 18:05:25 2018
  xserver.configfile: default
  xserver.errors:
   [drm] Failed to open DRM device for pci::03:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1852166] [NEW] Pixel pattern error in over

[Shahar Or]

Public bug reported:

The primary monitor, Microstep 24", is capable of 144 Hz refresh rate
and I do use that regularly in Windows 10.

When I set the rate to anything higher than 60 Hz (120 or 144) I get a
wrong pixel pattern. See attached photos.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 12 12:06:45 2019
DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390]
InstallationDate: Installed on 2010-10-12 (3317 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Supermicro X10SRA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root 
ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago)
dmi.bios.date: 06/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0a
dmi.board.asset.tag: Default string
dmi.board.name: X10SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: X10SRA
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun May 13 18:05:25 2018
xserver.configfile: default
xserver.errors:
 [drm] Failed to open DRM device for pci::03:00.0: -19
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug eoan ubuntu

** Attachment added: "60 Hz correct"
   
https://bugs.launchpad.net/bugs/1852166/+attachment/5304656/+files/IMG_20191112_121838.jpg

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

Title:
  Pixel pattern error in over

Status in xorg package in Ubuntu:
  New

Bug description:
  The primary monitor, Microstep 24", is capable of 144 Hz refresh rate
  and I do use that regularly in Windows 10.

  When I set the rate to anything higher than 60 Hz (120 or 144) I get a
  wrong pixel pattern. See attached photos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 12:06:45 2019
  DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390]
  InstallationDate: Installed on 2010-10-12 (3317 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root 
ro 

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Alkis Georgopoulos]

** No longer affects: epoptes (Ubuntu)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc7/

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Martin S]

FYI: I just re-tested with model=mono-speakers, and there the headhpone
output likewise does not change for any of the above settings: it works
great the entire time.

Thanks,
Martin

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Martin S]

Hi,
I was surprised, but none of these settings helped. Mode was set originally to 
options snd-hda-intel model=headset-mode-no-hp-mic


sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20
//check if headphone can output sound normally?

Running speaker-test:
very very quiet

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317
//check if headphone can output sound normally?

same result

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110
//check if headphone can output sound normally?

same result

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429
//check if headphone can output sound normally?

same result

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: 

[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

[Joe Barnett]

3.34.1+git20191107-1ubuntu1~19.10.1 appears to fix the issue here.

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

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Committed
Status in gnome-shell source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

[Desktop-packages] [Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
  and segfault

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I was trying to bring my Firefox window to front by pressing Super+2
  (it's my second pinned launcher), and gnome-shell crashed.

  journalctl shows this:

  lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed 
UTF-8 character sequence at offset 0
   
_filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43
  lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 
11
  lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 
0x56068fb2e3e0 ==

  I have a crash dump in /var/crash/, but apport thinks it's
  unreportable because my rygel was out of date.

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

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

[Desktop-packages] [Bug 1843793] Re: wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion to 2.6-21ubuntu3.2 fixes.

[Launchpad Bug Tracker]

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

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

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

Title:
  wpasupplicant 2.9 on eoan breaks wifi connections on arm64, reversion
  to 2.6-21ubuntu3.2 fixes.

Status in wpa package in Ubuntu:
  Expired

Bug description:
  Summary: Connecting from a RPI4 running on arm64 eoan-server-
  preinstalled image with current "upstream" raspberry pi foundation
  kernel 4.19.71 to a WPA2 protected access point (Unifi nanoHD). The
  wifi connection drops out after ~ ten minutes. Reverting wpasupplicant
  to disco version keeps that from happening.

  Running on arm64 eoan build with kernel from raspberry pi folks ( 
4.19.71-v8-g6de367fd7 ) on a rpi4.
  lsb_release -rd
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  With wpasupplicant 2.9, wifi comes up on boot, but then drops out
  shortly thereafter.

  Reverting wpasupplicant to 2.6-21ubuntu3.2 keeps the wifi connection
  from dropping out.

  wireless driver:
  [41385.982747] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43455-sdio for chip BCM4345/6
  [41386.000633] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  
1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  Logs using journalctl -xe NM_CONNECTION=f7f9f91f-001a-46b5-9acc-
  038db489a0c8 + NM_DEVICE=wlan0

  This is what I get with wpasupplicant 2.9:

  Sep 12 12:09:49 rpi4 NetworkManager[25218]:   [1568304589.2749] 
manager: (wlan0): new 802.11 Wi-Fi device 
(/org/freedesktop/NetworkManager/Devices/7)
  Sep 12 12:09:49 rpi4 NetworkManager[25218]:   [1568304589.3032] device 
(wlan0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'ex
  Sep 12 12:09:49 rpi4 NetworkManager[25218]:   [1568304589.3937] 
sup-iface[0x55b0b8faf0,wlan0]: supports 5 scan SSIDs
  Sep 12 12:09:49 rpi4 NetworkManager[25218]:   [1568304589.3957] device 
(wlan0): supplicant interface state: starting -> ready
  Sep 12 12:09:49 rpi4 NetworkManager[25218]:   [1568304589.3974] device 
(wlan0): state change: unavailable -> disconnected (reason 
'supplicant-available', sys-
  Sep 12 12:09:55 rpi4 NetworkManager[25218]:   [1568304595.9790] device 
(wlan0): supplicant interface state: ready -> scanning
  Sep 12 12:09:58 rpi4 NetworkManager[25218]:   [1568304598.7770] device 
(wlan0): supplicant interface state: scanning -> inactive
  Sep 12 12:10:01 rpi4 NetworkManager[25218]:   [1568304601.9310] device 
(wlan0): supplicant interface state: inactive -> scanning
  Sep 12 12:10:04 rpi4 NetworkManager[25218]:   [1568304604.7332] device 
(wlan0): supplicant interface state: scanning -> inactive
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.5964] device 
(wlan0): Activation: starting connection 'Manhattan' 
(f7f9f91f-001a-46b5-9acc-038db489a
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.5975] device 
(wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'manage
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6018] device 
(wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6027] device 
(wlan0): Activation: (wifi) access point 'Manhattan' has security, but secrets 
are requ
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6028] device 
(wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 
'managed')
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6115] device 
(wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 
'managed')
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6126] device 
(wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6139] device 
(wlan0): Activation: (wifi) connection 'Manhattan' has security, and secrets 
exist.  No
  Sep 12 12:10:15 rpi4 NetworkManager[25218]:   [1568304615.6690] device 
(wlan0): supplicant interface state: inactive -> scanning
  Sep 12 12:10:18 rpi4 NetworkManager[25218]:   [1568304618.4907] device 
(wlan0): supplicant interface state: scanning -> disconnected
  Sep 12 12:10:18 rpi4 NetworkManager[25218]:   [1568304618.6313] device 
(wlan0): supplicant interface state: disconnected -> scanning
  Sep 12 12:10:21 rpi4 NetworkManager[25218]:   [1568304621.4490] device 
(wlan0): supplicant interface state: scanning -> disconnected
  Sep 12 12:10:21 rpi4 NetworkManager[25218]:   [1568304621.9910] device 
(wlan0): supplicant interface state: disconnected -> scanning
  Sep 12 12:10:24 rpi4 NetworkManager[25218]:   [1568304624.8102] device 
(wlan0): supplicant interface state: scanning -> disconnected
  Sep 12 12:10:25 rpi4 

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

[MrTux]

I confirmed problem fixed after upgrade to mutter / libmutter-5-0
3.34.1+git20191107-1ubuntu1~19.10.1.

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

[darkrain42]

I can also confirm this is fixed after upgrading mutter / libmutter-5-0
to 3.34.1+git20191107-1ubuntu1~19.10.1.

Thank you!

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

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1852158] [NEW] Xorg black screen on resume, and VT switch crashes with "EnterVT failed for screen 0"

[Akkana Peck]

Public bug reported:

Every now and then, maybe one time out of 8, resuming from suspend gives
me a black screen, no X.

If I try ctrl-alt-F7, I see a VT with a _ on it, no X or login prompt.
If I try ctrl-alt-F1, F2, F2 or F4, X crashes, every time.

I've collected X logs from the last two times this has happened; both times, 
there's a message near the end:
EnterVT failed for screen 0

I found a similar but not identical upstream bug: that might be related:
https://bugs.freedesktop.org/show_bug.cgi?id=109668
There's also a Redhat bug that looks related and might have helpful info:
https://bugzilla.redhat.com/show_bug.cgi?id=1662057

Machine is a Levono Carbon X1 with Intel graphics (hopefully ubuntu-bug
attached the relevant info).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
Date: Mon Nov 11 19:51:13 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2019-10-10 (32 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
MachineType: LENOVO 20QDCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET30W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash eoan 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/1852158

Title:
  Xorg black screen on resume, and VT switch crashes with "EnterVT
  failed for screen 0"

Status in xorg package in Ubuntu:
  New

Bug description:
  Every now and then, maybe one time out of 8, resuming from suspend
  gives me a black screen, no X.

  If I try ctrl-alt-F7, I see a VT with a _ on it, no X or login prompt.
  If I try ctrl-alt-F1, F2, F2 or F4, X crashes, every time.

  I've collected X logs from the last two times this has happened; both times, 
there's a message near the end:
  EnterVT failed for screen 0

  I found a similar but not identical upstream bug: that might be related:
  https://bugs.freedesktop.org/show_bug.cgi?id=109668
  There's also a Redhat bug that looks related and might have helpful info:
  https://bugzilla.redhat.com/show_bug.cgi?id=1662057

  Machine is a Levono Carbon X1 with Intel graphics (hopefully ubuntu-
  bug attached the relevant info).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  Date: Mon Nov 11 19:51:13 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: 

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[James Henstridge]

The two packages are in the upload queue now:


https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=pulseaudio

https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=pulseaudio

One additional acceptance test would be to verify that the policy module
continues to work across snapd restarts.  So at the end of the test
script, add something like:

The policy module continues to function over snapd restarts:

$ sudo systemctl restart snapd.service
$ test-snapd-audio-record.record /tmp/out.wav && echo yes # should pass
...
^Cyes

This was a problem with old versions of snapd-glib (before 1.44, I
think), but shouldn't be a problem now.

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should 

[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Tomoki Kosugi]

Same problem. I use laptop PC, Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, GPU 
GeForce GTX 1080 * 2.
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS".
Linux kernel version is  "Linux anomalydetect 4.15.0-66-generic".

I tried "cpupower" that controls CPU clock frequency.
cf. https://wiki.archlinux.org/index.php/CPU_frequency_scaling

# cpupower frequency-set -u clock_freq

I tried the above with "clock_freq" set to "3GHz". (My CPU default max
frequency is "4.5GHz")

Then, "cpupower" was able to keep CPU temperature lowly without slowing down in 
my application!!
What do you think about this solution?

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

[Anurag Soni]

Hi Brian,

I enabled the eoan-proposed repository and on upgrading mutter +
libmutter-5-0 I am able to use Night light and change color profiles
again.

Thanks,
Anurag

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1757299] Re: [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after launching applications

[gregrwm]

have been using biopic without issue for well over a year, no issue with
either gnome-session-flashback or twm, twm has the functionality i
require.  bug finally surfaced again today.  was in-call using google
voice via firefox nightly and bluetooth.  clicked on the microphone icon
on the top center of the screen (not within any Window).  thereafter,
like prior occurrences, tho the audio continued without interruption,
the screen froze, mostly, the mouse cursor still moves but neither
window borders nor anything else on screen respond to mouse movement,
buttons, or keyboard, even ctl-alt-f2 et al are unable to switch to
another VT.  am able to login via ssh and observe Xorg consuming 97%cpu.
signal 15 to Xorg ineffective, signaly 9 kills it, whereupon ctl-alt-f2
is finally able to switch the virtual terminal.  relaunch of X succeeds
without reboot.

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

Title:
  [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after
  launching applications

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The problem is that after launching a few applications, the GUI may
  become unresponsive, although this is not consistently reproducible.
  When the GUI is unresponsive, it is correlated to high CPU utilization
  of xorg.

  An example reproduction scenario is launch the following in order, and 
quickly:
  startx
  xterm via twm
  another xterm via the first xterm
  tmux
  firefox-esr
  bluetooth-manager
  pavucontrol

  While the above are launching, maximize the xterm running tmux, and
  the GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn
  don't respond.

  After this, I logged in via ssh, attached to tmux, launched htop,
  copied htop output, which shows xorg at 94.6 CPU%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    * Starting AppArmor profiles   
  [ OK ]
    * Restoring resolver state...   
  [ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  

[Desktop-packages] [Bug 1851807] Re: xdg-desktop-portal-gtk spams logs

[Ken VanDine]

** Changed in: xdg-desktop-portal-gtk (Ubuntu Eoan)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  xdg-desktop-portal-gtk spams logs

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gtk source package in Eoan:
  New

Bug description:
  Every minute I get a log entry that looks like

  > xdg-desktop-por[ ]: Failed to get application states:
  GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
  list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App
  introspection not allowed

  Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal-
  gtk/issues/222

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xdg-desktop-portal-gtk 1.4.0-2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:51:30 2019
  InstallationDate: Installed on 2019-11-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1851807] Re: xdg-desktop-portal-gtk spams logs

[Ken VanDine]

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Also affects: xdg-desktop-portal-gtk (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

Title:
  xdg-desktop-portal-gtk spams logs

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gtk source package in Eoan:
  New

Bug description:
  Every minute I get a log entry that looks like

  > xdg-desktop-por[ ]: Failed to get application states:
  GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
  list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App
  introspection not allowed

  Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal-
  gtk/issues/222

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xdg-desktop-portal-gtk 1.4.0-2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:51:30 2019
  InstallationDate: Installed on 2019-11-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

[Sebastien Bacher]

Could you report it upstream to
https://gitlab.gnome.org/GNOME/nautilus/issues/ ?

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

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Description:

  I recently noticed a strange behavior on my (pretty vanilla) Ubuntu
  18.04.2 LTS. Every time I copy some text from GNOME Terminal, using
  keyboard or mouse, it triggers a little hard drive activity.

  Intrigued, I decided to see what was going on (persistent clipboard
  data?). After some investigation, I found out that the activity is due
  to a file being written to whenever I do a copy in GNOME Terminal (or
  in other apps):

  ~/.config/nautilus/desktop-metadata

  The small file seems to record the nautilus view settings and the
  trash icon state, has no apparent relation to functions of the
  clipboard, and does not mutate following each write (the content stays
  unchanged).

  I also tested to see if the same happens on a different computer
  running 18.04.2 desktop live usb, and the answer is yes. So this
  shouldn't be something particular to my system.

  
  Steps to reproduce:

  * Boot your computer using live CD or usb created with: 
  ubuntu-18.04.2-desktop-amd64.iso
  You can obtain it from:
  http://releases.ubuntu.com/18.04/
  last modified: 2019-02-10 00:27
  sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4)

  * Start Gnome Terminal, copy some text from there, and note the
  current time when you perform the copying

  * Check the timestamp of ~/.config/nautilus/desktop-metadata and
  observe it's been modified at the same time you did the copying

  * Repeat as many times as you like

  
  Expected behavior:

  Copying text in Gnome should not trigger writes to some arbitrary file
  (and should not trigger any disk IO at all).

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

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

[Desktop-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard (in Wayland sessions only)

[Sebastien Bacher]

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

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

Title:
  Repeated keypresses from bluetooth keyboard (in Wayland sessions only)

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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

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

[Desktop-packages] [Bug 1850778] Re: Audio output changes to hdmi after hibernate

[Sebastien Bacher]

Thank you for your bug report, you submitted that on the wrong component
since it's not an issue with the command line application, it's also
already reported as bug #1847570

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Invalid

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

Title:
  Audio output changes to hdmi after hibernate

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  This wasn't present in 19.04:

  When returning from hibernate, audio devices is changed to hdmi (gp104 
device), which is not even plugged in. When playing audio and changing volume 
one has to go into volume settings or pavucontrol to change the 
output/controlled device back to "Line out".
  Disabling "module-switch-on-port-available" is not an option because that 
disable automatic switching to headphone output.

  I've tried disabling the gp104 device in pavucontrol, but this has no effect, 
it keeps switching to it.
  This is not specific to the nvidia driver's gp104 hdmi output though, to be 
clear, because the same thing happened when I had pulseaudio-dlna active -- it 
switched to those devices after wake, which was even worse because playing 
audio on the computer after a  wake-from-sleep kept launching my 
chromecast/other dlna devices in my apartment.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 12:04:19 2019
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-07-04 (483 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274

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

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

[Desktop-packages] [Bug 1798840] Re: Night Light is not functioning

[Sebastien Bacher]

the 19.10/wayland issue is new and tracked as bug ##1847551, that old
ticket is another issue

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

Title:
  Night Light is not functioning

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

Bug description:
  Night Light is not shading/filtering the screen anymore after the update to 
Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS).
  It still appears as an option and all the settings work, but the feature 
itself isn't filtering out blue light from the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:03:28 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1851725] Re: NetworkManager forgets VPN credentials

[Mathieu Tarral]

I would like to add that if you choose to store the password for all
users, then it works, the password is stored by NetworkManager.

However, the bug is important because it affects the default option
selected for anyone willing to use a VPN connection: store password for
the current user.

Any Ubuntu user who is trying to use a VPN connection will probably
decide to give up because of NetworkManager unability to store the
password, despite what the GUI says.

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

Title:
  NetworkManager forgets VPN credentials

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since recently, I can't import a VPN connection in NetworkManager and store 
my credentials.
  NetworkManager will systematically forget the password, despite a log entry 
confirming that the operation was a success:

  nov. 07 22:26:52  NetworkManager[1518]:   [1573162012.8680]
  audit: op="connection-update"
  uuid="3f985155-4e20-4351-88d7-14d5909a2d03"
  name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000
  result="success"

  Please look at the video attached.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 22:22:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-26 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  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.20.4   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/1851725/+subscriptions

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

[Desktop-packages] [Bug 1850931] Re: screen corruption after sleep mode

[Sebastien Bacher]

Thank you for your bug report. Does it do it every time?
Could you add your journalctl log just after getting the issue?

** Changed in: xorg (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/1850931

Title:
  screen corruption after sleep mode

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When my laptop goes into sleep mode, and I log back in, the screen is 
corrupted. I wanted to report with ubuntu-bug, but that doesn't open a browser 
window so it doesn't report a bug.
  I'll attach a screenshot of the corrupted screen. It stays corrupted until I 
restart the computer. The laptop is a new Dell XPS 15 with a GEforce GTX 1650 
card.
  I use Ubuntu 19.04.

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

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

[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system

[paz]

Thank you for looking at it @seb 128,
as I mentioned above, I initiated the oom when my browser and the system are 
completely freezing.
It is happening only when using Firefox (last 2 versions). it feels like a 
process within the browser
just go wild suddenly and cousin the freeze. 

There is a major improvement in the last update but still going on
randomly.

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

Title:
  Latest Firefox update freezing my system

Status in firefox package in Ubuntu:
  New

Bug description:
  The latest updates of firefox renders my machine useless. I'm sending
  it as is hopefully before it freezes completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  BuildID: 20190828152935
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 01:22:17 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-05-01 (506 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/20190828152935 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Sebastien Bacher]

Thank you for your bug report, did you notice anything special in your usage 
triggering the bug?
For how long does it freeze and does it come back?
Is there any error in the journalctl log around the time of the issue?

** Changed in: xorg (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/1850551

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded to ubuntu-18.04 and the screen starts to freeze
  randomly. The CPU used to gets overheated on minimal use.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 02:03:51 2019
  DistUpgraded: 2019-07-26 05:15:58,339 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-64-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2018-02-01 (635 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=bf1c9a5c-ebb8-4edf-8bde-0767ec9746b0 ro nouveau.modeset=0 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2019-07-25 (95 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.06.00
  dmi.board.name: 0D53F5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0D53F5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.100+git1910210630.c69c9c~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909090730.ae5ac2~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909090730.ae5ac2~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.1.0+git1910151930.b9bd80~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1910071930.bff5ec~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Desktop-packages] [Bug 1851964] Re: Volume indicator lags behind scroll action to change volume

[Sebastien Bacher]

Thank you for your bug report, do you think you could report it upstream as 
well?
https://gitlab.gnome.org/GNOME/gnome-shell/issues

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

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

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

Title:
  Volume indicator lags behind scroll action to change volume

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume with the help of the mouse/touchpad, scrolling on
  top of the sound icon used to work fine in the older versions of gnome
  shell. In Ubuntu 19.10, it does not. I scroll, but the graphic
  indicator that shows on the screen lags behind, even jumps. If needed,
  I could try to record it as video. There is definitely some
  performance issue over there.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc6-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 23:50:04 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (21 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.

[Sebastien Bacher]

Thank you for your bug report. Could you try with a new user/without
extensions to see if that makes a difference?

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

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

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

Title:
  Monitors keep turning on when in power saving mode, every time.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I lock my computer, or it goes into power saving mode
  automatically, the monitors turn back on and show the lock screen a
  few seconds later. This has persisted now for about a year, has
  persisted across multiple upgrades (18.10, 19.04, 19.10) as well as
  complete hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD).
  So I'm convinced this is a software bug.

  The first line in logging that I can find that seems to trigger this
  is:

  "gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance
  '0x55daa50a2920' has no handler with id '145952'"

  I update my system regularly, so this looks to either be a regression,
  or uncaught bug. I don't know if other things are causing this, but
  that's the first line (based on time) that is reported when it turns
  the monitors back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 09:40:42 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-08 (247 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago)

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

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

[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

[Brian Murray]

Hello Angel, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.34.1+git20191107-1ubuntu1~19.10.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: mutter (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Committed
Status in gnome-shell source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

[Desktop-packages] [Bug 1841709] Re: [regression] gobject.h:767: syntax error

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.34.1+git20191107-1ubuntu1~19.10.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: mutter (Ubuntu Eoan)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  [regression] gobject.h:767: syntax error

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Impact ]

  Building mutter triggers various non-fatal syntax errors:

  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in 
'  do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at '/'
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')', 
expecting identifier or '(' in '  do { if 
g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at ')'
  /usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')', 
expecting identifier or '(' in '# 770 
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'

  Looks like the offending release glib2.0 (2.61.2-2) is from last
  night's updates.

  [ Test case ]

  - Just build mutter and ensure that no such errors are triggered

  [ Regression potential ]

  None, once it builds we're all happy :)

  ---

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: libglib2.0-dev 2.61.2-2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 28 11:30:06 2019
  InstallationDate: Installed on 2019-05-02 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 
(20190501)SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

[Brian Murray]

Hello Anders, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.34.1+git20191107-1ubuntu1~19.10.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: mutter (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened

[Brian Murray]

Hello betteropensource, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.34.1+git20191107-1ubuntu1~19.10.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: mutter (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  cannot click on others opened applications while the "application not
  responding" dialog is opened

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Impact ]

  The "application is not responding" can make the shell hang under X11

  [ Test case ]

  - Start an application (i.e. firefox)
  - Stop the process
killall -STOP firefox
  - After some moments and interactions with the window the gnome shell
dialog to kill the window should pop-up
  - The shell should be still responsive and you can get the program to
run again (killall -CONT firefox)

  [ Regression potential ]

  Focus might be wrongly set to the applications or actors and instead
  be owned by the shell

  This is uploaded under the gnome MRE, so the fix doesn't need to be
  explicitly verified.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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

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

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

[Sebastien Bacher]

it's not a bug in nmapplet if lubuntu includes 2 indicators

** Package changed: network-manager-applet (Ubuntu) => lubuntu-default-
settings (Ubuntu)

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

Status in lubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  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/lubuntu-default-settings/+bug/1761606/+subscriptions

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

[Desktop-packages] [Bug 1838081] Re: Local printers crowd out installed printers in list

[Sebastien Bacher]

Thank you for your bug report. Could you report it upstream on 
https://gitlab.gnome.org/GNOME/gnome-control-center/issues ?

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Local printers crowd out installed printers in list

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

Bug description:
  In Ubuntu 18.04, the list of printers show in the control center seems
  to include everything which is visible by Bonjour or some other
  discovery service on the local network; there is no visual distinction
  made between "installed" printers and available ones (this is also
  true of print dialogs, but that's another issue).

  For networks with many shared printers (many of which seem to be the
  result of Apple sharing attached printers by default; see screenshot),
  this results in an overwhelming flood of listed printers, which,
  worse, is constantly shifting and jumping around as network state
  changes. This makes it difficult to find previously installed printers
  in the list.

  My suggestion would be to make a distinction in the UI between
  installed and available printers (and perhaps also to have a listing
  that uses less vertical space per discovered printer).

  Really,system-config-printer CUPS window which is brought up by the
  "Additional Printer Settings" button at the bottom is far more
  functional, and in fact was the *only* way that I was able to add a
  new printer via address alone.

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 26 13:52:06 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-12-17 (221 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1838081/+subscriptions

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

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

[Sebastien Bacher]

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I clicked around on the top panel, e.g. the battery, the wifi, and app
  icons.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  Date: Tue Nov  5 10:25:30 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-13 (752 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  SegvAnalysis:
   Segfault happened at: 0x7fa6ab83c05d :
movzbl 0x16(%rax),%edx
   PC (0x7fa6ab83c05d) ok
   source "0x16(%rax)" (0x3f8008ec8348536a) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   shell_tray_icon_click () at /usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-06-25 (497 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo

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

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

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

[Pål Bergström]

Thank you for taking the time. I have a hard time pinpointing the exact
moments it happens. It's a short freeze, then it works again.
Irrational. Didn't happen in 19.04. One occasion is when working with
LibreOffice Version: 6.3.2.2 and Calc. When opening a document from
inside Calc it happened when scrolling down a long list to find the
right one and the window "rendering" (not an expert) seemed to have a
problem keeping up. Mouse freeze for a millisecond. Also when opening
Calc and trying to do something inside to fast, like moving the mouse to
the menu before it's done opening and rendering the window content, the
mouse freeze for a millisecond and work again. If you see what I mean.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor
  now and then. Problem with multitasking.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 10:29:50 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-10-18 (17 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/xorg/+bug/1851349/+subscriptions

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

[Desktop-packages] [Bug 1851725] Re: NetworkManager forgets VPN credentials

[Mathieu Tarral]

Hi Sebastien,

The only line that pops up when I click apply is the one I already
pasted before:

nov. 12 00:40:00  NetworkManager[1529]:   [1573515600.3387]
audit: op="connection-update" uuid="45154b5c-
bed9-4904-a090-7d2e0303e27e" name="at-01.protonvpn.com.udp"
args="vpn.secrets" pid=23095 uid=1000 result="success"

There is no other relevant information in journalctl in my opnion.

I could send you a log if you want, but I don't know how to NOT make it
publicly available on this Launchpad report.

Thanks/

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

Title:
  NetworkManager forgets VPN credentials

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since recently, I can't import a VPN connection in NetworkManager and store 
my credentials.
  NetworkManager will systematically forget the password, despite a log entry 
confirming that the operation was a success:

  nov. 07 22:26:52  NetworkManager[1518]:   [1573162012.8680]
  audit: op="connection-update"
  uuid="3f985155-4e20-4351-88d7-14d5909a2d03"
  name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000
  result="success"

  Please look at the video attached.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 22:22:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-26 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  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.20.4   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/1851725/+subscriptions

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

[Desktop-packages] [Bug 1179834] Re: baobab hangs at startup

[Sebastien Bacher]

Thank you for your bug report. Do you have some non local filesystems mounted?
Could you get a gdb backtrace of the hang as well?

** Changed in: baobab (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  baobab hangs at startup

Status in baobab package in Ubuntu:
  Incomplete

Bug description:
  When I run baobab nothing happens - I don't get a window or when
  started from a console any messages, even after waiting for several
  minutes.  strace has this at the end with the hanging:

  geteuid()   = 1000
  getegid()   = 1000
  poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, 
revents=POLLOUT}])
  sendmsg(11, {msg_name(0)=NULL, msg_iov(1)=[{"\0", 1}], msg_controllen=32, 
{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=13565, 
uid=1000, gid=1000}}, msg_flags=0}, MSG_NOSIGNAL) = 1
  poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, 
revents=POLLOUT}])
  sendto(11, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
  poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
  recvfrom(11, "REJECTED EXTERNAL DBUS_COOKIE_SH"..., 4096, 0, NULL, NULL) = 36
  poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, 
revents=POLLOUT}])
  sendto(11, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
  poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
  recvfrom(11, "OK 41b3c3c0a40c65fd7d45c7c85191f"..., 4096, 0, NULL, NULL) = 37
  poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, 
revents=POLLOUT}])
  sendto(11, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
  poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
  recvfrom(11, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
  poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, 
revents=POLLOUT}])
  sendto(11, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
  write(8, "\1\0\0\0\0\0\0\0", 8) = 8
  futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
  eventfd2(0, O_NONBLOCK|O_CLOEXEC)   = 13
  write(13, "\1\0\0\0\0\0\0\0", 8)= 8
  poll([{fd=13, events=POLLIN}], 1, 0)= 1 ([{fd=13, revents=POLLIN}])
  write(13, "\1\0\0\0\0\0\0\0", 8)= 8
  close(13)   = 0
  eventfd2(0, O_NONBLOCK|O_CLOEXEC)   = 13
  write(13, "\1\0\0\0\0\0\0\0", 8)= 8
  write(8, "\1\0\0\0\0\0\0\0", 8) = 8
  futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
  futex(0x1618400, FUTEX_WAKE_PRIVATE, 1) = 1
  futex(0x16183d0, FUTEX_WAKE_PRIVATE, 1) = 1
  poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
  poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
  read(13, "\1\0\0\0\0\0\0\0", 16)= 8
  poll([{fd=13, events=POLLIN}], 1, 4294967295^C 

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: baobab 3.6.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May 14 01:27:58 2013
  MarkForUpload: True
  SourcePackage: baobab
  UpgradeStatus: Upgraded to raring on 2013-04-28 (16 days ago)

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

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

[Desktop-packages] [Bug 1851546] Re: Debug spew to stderr at startup

[Sebastien Bacher]

Thank you for your bug report, that should be reported upstream on
gitlab.gnome.org though

** Changed in: gnome-terminal (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Debug spew to stderr at startup

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal writes debug messages to stderr every time it starts
  up:

  # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) 
for ‘gio-vfs’
  # _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
  # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
  # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

  This pollutes the terminal when a script explicitly invokes gnome-
  terminal to open another window.

  STEPS TO REPRODUCE:

  1. Open a terminal and type "gnome-terminal"

  RESULTS:  Debug messages appear on the first terminal

  EXPECTED RESULTS: Nothing should appear on stderr or stdout of gnome-
  terminal itself, unless there is an actual error.

  P.S. Presumably a debug build escaped and was released.  To prevent
  this from happening, it would be a good idea to add a test which
  checks that gnome-terminal writes nothing to std* in normal (non-
  error) cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 10:03:24 2019
  InstallationDate: Installed on 2019-02-06 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago)

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

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

[Desktop-packages] [Bug 1851551] Re: man page does not mention that -e is deprecated

[Sebastien Bacher]

** Changed in: gnome-terminal (Ubuntu)
   Importance: Undecided => Low

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

Title:
  man page does not mention that -e is deprecated

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal -e 'command...'  emits a warning:

  # Option “-e” is deprecated and might be removed in a later version of 
gnome-terminal.
  # Use “-- ” to terminate the options and put the command line to execute 
after it.

  However this is contrary to the man page, which says nothing about -e
  being deprecated, and does not mention anything about the new method
  being possible (-- followed by command and options).

  Please update the documentation

  STEPS TO REPRODUCE:

  1.  man gnome-terminal
  2.  gnome-terminal -e "sh -c 'ls -l; sleep 3'"

  RESULTS: The documented method of specifying a command causes a
  deprecation warning.

  EXPECTED RESULTS: Documentation should say how to do the right thing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 10:20:44 2019
  InstallationDate: Installed on 2019-02-06 (273 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago)

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

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

[Desktop-packages] [Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault

[Sebastien Bacher]

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

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870
   Importance: Unknown
   Status: Unknown

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

Title:
  JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
  and segfault

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I was trying to bring my Firefox window to front by pressing Super+2
  (it's my second pinned launcher), and gnome-shell crashed.

  journalctl shows this:

  lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed 
UTF-8 character sequence at offset 0
   
_filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43
  lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 
11
  lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 
0x56068fb2e3e0 ==

  I have a crash dump in /var/crash/, but apport thinks it's
  unreportable because my rygel was out of date.

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

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

[Desktop-packages] [Bug 1851649] Re: Package bug

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (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/1851649

Title:
  Package bug

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I couldn't change brightness. Probably this bug is related to the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 14:54:15 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d]
  InstallationDate: Installed on 2019-11-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 44CN43WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: HuronRiver Platform
  dmi.product.sku: System SKUNumber
  dmi.product.version: Lenovo B570e
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.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/xorg/+bug/1851649/+subscriptions

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

[Desktop-packages] [Bug 1851672] Re: gnome-control-centre does not open, even from terminal - segmentation fault

[Sebastien Bacher]

Thank you for your bug report.  the package you are using is not coming from 
Ubuntu though
1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
You should report it to popOS

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-control-centre does not open, even from terminal - segmentation
  fault

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

Bug description:
  Ubuntu 19.10

  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Candidate: 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f
Version table:
   *** 1:3.34.1-1ubuntu2pop1~1571679625~19.10~ef2ab1f 500
  500 http://ppa.launchpad.net/system76/pop/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.34.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gnome-control-center...
  (No debugging symbols found in gnome-control-center)
  (gdb) run
  Starting program: /usr/bin/gnome-control-center 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffea25c700 (LWP 13902)]
  [New Thread 0x7fffe9a5b700 (LWP 13903)]
  [New Thread 0x7fffe3fff700 (LWP 13906)]
  [New Thread 0x7fffe36c5700 (LWP 13907)]
  [New Thread 0x7fffe2ec4700 (LWP 13908)]
  [New Thread 0x7fffe266d700 (LWP 13910)]

  Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
  0x776bae1e in gtk_container_add ()
 from /lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb)

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

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

[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions

[Sebastien Bacher]

Does it work with a new user on the same system?

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

Title:
  can't install gnome shell extensions

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Here's what I'm trying to do:

  1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
  2. Click the toggle switch to install it.
  3. Use the extension after it is installed.

  Here's what should happen:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch goes from Off to On and the extension is added to my top 
bar.

  Here's what happens instead:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch stays in the Off permission, and the extension is not 
added to my top bar.

  Here's what I see in journalctl:

  Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user
  /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from
  available to installed is not OK

  I've also tried unzipping by hand into a subdirectory of
  ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and
  enabling the extension at extensions.gnome.org/local, but that doesn't
  work either. The toggle switch goes to On when I toggle it, but the
  extension isn't actually enabled and when I reload the page the switch
  is Off again.

  I've tried with https://extensions.gnome.org/extension/779/clipboard-
  indicator/ and https://extensions.gnome.org/extension/7/removable-
  drive-menu/ too. They won't install and activate either.

  *** I do not have this problem on a second Ubuntu 19.10 computer I
  use. *** I have no idea what is different between the two computers or
  how to troubleshoot further.

  I am using Xorg, not Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 14:16:34 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

Title:
  gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-software/issues/792

  ---

  I do not know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 07:57:24 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-12-02 (283 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10
   gnome-software-plugin-snap3.30.6-2ubuntu10
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: 
vmovdqu -0x20(%rsi,%rdx,1),%ymm5
   PC (0x7f565aa3fcc4) ok
   source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA 
region (needed readable region)!
   destination "%ymm5" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   __memmove_avx_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
   g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
   () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so
  Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login

[Sebastien Bacher]

Thank you for your bug report. Could you test if the issue exists under X?
It looks like an upstream bug, could you report it there
https://gitlab.gnome.org/GNOME/gnome-shell/issues

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

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

Title:
  monitor configuration restored incorrectly upon Wayland login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have an ultrawide monitor plugged into my laptop. When I log into a
  Wayland session, my monitor configuration (resolution, relative
  position, which monitor is the primary) is not restored correctly.
  When I unplug the monitor cable after logging in and plug it in again,
  the correct configuration is restored.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 15:45:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1851564] Re: Daily Limit Exceeded messages for google calendars

[Sebastien Bacher]

GNOME got tht key situation sorted out, the problem should be resolved
now

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Daily Limit Exceeded messages for google calendars

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  This seems to coincide with the 19.04 -> 19.10 upgrade, but I only
  have logs going back to mid august.  The message is repeated for each
  calendar at various times.

  Nov 06 13:49:13 dipper gnome-calendar[8681]:
  source_credentials_required_cb: Failed to authenticate 'Kai Groner':
  Daily Limit Exceeded. The quota will be reset at midnight Pacific Time
  (PT). You may monitor your quota usage and adjust limits in the API
  Console:
  
https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.2-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 15:07:56 2019
  InstallationDate: Installed on 2019-06-18 (141 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)

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

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

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

[Sebastien Bacher]

Thank you for your bug report. Can you corolate the freezes with
specific actions or e.g I/O use? Could look if there is anything printed
in the journalctl logs at the time of the hang? Could you try if it's
happening on a wayland session as well?

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

** Changed in: xorg (Ubuntu)
   Status: Confirmed => 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/1851349

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor
  now and then. Problem with multitasking.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 10:29:50 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-10-18 (17 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/xorg/+bug/1851349/+subscriptions

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

[Desktop-packages] [Bug 1852069] Re: Failed to backup to google drive on ubuntu 19.10

[Bug Watch Updater]

** Changed in: deja-dup (Debian)
   Status: Unknown => New

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

Title:
  Failed to backup to google drive on ubuntu 19.10

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Confirmed
Status in deja-dup package in Debian:
  New

Bug description:
  On Ubuntu 19.10 can't do backup to Google Drive anymore with the
  following error message:

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'apiclient'

  I also could not find pydrive package or don't know how it properly
  called.

  $ lsb_release -d
  Description:Ubuntu 19.10

  $ dpkg-query -W deja-dup duplicity
  deja-dup40.1-1ubuntu2
  duplicity   0.8.04-2ubuntu1

  The logfile for following command is empy:
  DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1852069/+subscriptions

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

[Desktop-packages] [Bug 1851715] Re: Screen brightness adjustment delay

[Sebastien Bacher]

** Package changed: xorg (Ubuntu) => linux (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/1851715

Title:
  Screen brightness adjustment delay

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time I adjust my laptop's screen brightness using the dedicated
  brightness keys, there is a substantial delay between when I press the
  button and the screen adjusts. Sometimes it even "twitches" and
  decreasing the brightness by tapping the button two times will quickly
  drop the brightness all the way to the lowest setting after the delay
  takes place. I've noticed the issue in the default Ubuntu session and
  in my current vanilla gnome-session. It also doesn't matter which
  extensions I have installed. The keys work flawlessly in Windows so it
  isn't a hardware issue. I have been meaning to report this for a while
  and have just never gotten around to it until just now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Nov  7 14:37:43 2019
  DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-19-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]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2019-09-08 (59 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
  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: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/linux/+bug/1851715/+subscriptions

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

[Desktop-packages] [Bug 1851725] Re: NetworkManager forgets VPN credentials

[Sebastien Bacher]

Thank you for your bug report. Could you add your journalctl log from
around the time of the issue?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  NetworkManager forgets VPN credentials

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since recently, I can't import a VPN connection in NetworkManager and store 
my credentials.
  NetworkManager will systematically forget the password, despite a log entry 
confirming that the operation was a success:

  nov. 07 22:26:52  NetworkManager[1518]:   [1573162012.8680]
  audit: op="connection-update"
  uuid="3f985155-4e20-4351-88d7-14d5909a2d03"
  name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000
  result="success"

  Please look at the video attached.

  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  7 22:22:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-26 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  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.20.4   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/1851725/+subscriptions

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

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

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (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/1851789

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  While each window partly unresponsive, the system did not freeze up 
completely.
  I was still able to switch active windows or change to different desktops.

  But within each window, only the previously active part I was still able to 
interact with.
  For example in my browser, the active part was the address bar. I was still 
able to type, but any other interaction (buttons, opening new tabs etc) was not 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 09:51:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:07a8]
  InstallationDate: Installed on 2019-03-08 (244 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Latitude 5580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=6b2676ab-dd94-4534-9d03-ddde577418a3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 06K7YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn06K7YG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.product.sku: 07A8
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.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/xorg/+bug/1851789/+subscriptions

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

[Desktop-packages] [Bug 1851944] Re: Connection problem with account 'laposte.net'

[Sebastien Bacher]

Thank you for your bug report. Are you sure the problem is with thunderbird? 
Does it work better with other softwares?
>From experience it's just that the laposte imap servers are not really 
>reliable...

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

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

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

Title:
  Connection problem with account 'laposte.net'

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  IMAP access to laposte.net is wrong : mails are not downloaded to my computer 
(time-out), neither new mails, nor content for already downloaded mails.
  Nevertheless I'm still able to sent mail via SMTP on Thunderbird.

  The webmail on laposte is OK, though.

  Mails from my Microsoft account are downloaded smouthly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.9.0+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  norb   3642 F pulseaudio
   /dev/snd/controlC1:  norb   3642 F pulseaudio
   /dev/snd/controlC2:  norb   3642 F pulseaudio
   /dev/snd/controlC0:  norb   3642 F pulseaudio
  BuildID: 20191007090452
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 17:04:52 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-07-12 (1214 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090452 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.G0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING PRO (MS-7984)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.G0:bd06/16/2018:svnMSI:pnMS-7984:pvr1.0:rvnMSI:rnZ170AGAMINGPRO(MS-7984):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7984
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear

[Sebastien Bacher]

Thank you for your bug report. How many notifications are you getting?
Can you trigger with notify-send? Do you get any error with apport/in
the journal at the time of the issue?

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

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

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

Title:
  gnome shell freezes when too many notifications appear

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using 20.04. When I receive some notifications immediately one
  after the other, the shell sometimes freezes.

  I usually make it start again moving to a vt and doing `killall -3
  gnome-shell`.

  This makes it work again (except it makes some apps like PyCharm and
  Chrome to crash).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 13:26:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-03 (277 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago)

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

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

[Desktop-packages] [Bug 1852140] Re: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package
  hplip-data is already installed and configured

Status in hplip package in Ubuntu:
  New

Bug description:
  he conseguido agregar la impresora a pesar del error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hplip-data 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Nov 11 22:57:50 2019
  DuplicateSignature:
   package:hplip-data:3.16.3+repack0-1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libart-2.0-2:i386 (--configure):
package libart-2.0-2:i386 is already installed and configured
  ErrorMessage: package hplip-data is already installed and configured
  InstallationDate: Installed on 2019-11-11 (0 days ago)
  InstallationMedia:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell DOA150
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=78936867-355d-46e8-9d95-523db97202d8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: hplip
  Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package 
hplip-data is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2008
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: v0.3103
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPackardBell:bvrv0.3103:bd10/09/2008:svnPackardBell:pnDOA150:pvrLU.B040B.016:rvnPackardBell:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: DOA150
  dmi.product.version: LU.B040B.016
  dmi.sys.vendor: Packard Bell

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

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

[Desktop-packages] [Bug 1851833] Re: Unable to adjust brightness of backlight

[Sebastien Bacher]

** Package changed: xorg (Ubuntu) => linux (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/1851833

Title:
  Unable to adjust brightness of backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am unable to adjust the brightness of the backlight of my laptop
  screen either by using the slider of by changing the value in
  /sys/class/backlight/intel_backlight/brightness directly.

  I have tried changing my GRUB configuration:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  But that did not help.

  I am using Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 14:03:33 2019
  DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
   NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] 
[1558:65d1]
  InstallationDate: Installed on 2019-10-09 (30 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Notebook PB50_70RF,RD,RC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: PB50_70RF,RD,RC
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: PB50_70RF,RD,RC
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/linux/+bug/1851833/+subscriptions

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

[Desktop-packages] [Bug 1852140] [NEW] package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured

[Ivan A.]

Public bug reported:

he conseguido agregar la impresora a pesar del error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: hplip-data 3.16.3+repack0-1
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic i686
ApportVersion: 2.20.1-0ubuntu2.21
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
Architecture: i386
CupsErrorLog:
 
Date: Mon Nov 11 22:57:50 2019
DuplicateSignature:
 package:hplip-data:3.16.3+repack0-1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libart-2.0-2:i386 (--configure):
  package libart-2.0-2:i386 is already installed and configured
ErrorMessage: package hplip-data is already installed and configured
InstallationDate: Installed on 2019-11-11 (0 days ago)
InstallationMedia:
 
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Packard Bell DOA150
PackageArchitecture: all
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=78936867-355d-46e8-9d95-523db97202d8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: hplip
Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package 
hplip-data is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2008
dmi.bios.vendor: Packard Bell
dmi.bios.version: v0.3103
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPackardBell:bvrv0.3103:bd10/09/2008:svnPackardBell:pnDOA150:pvrLU.B040B.016:rvnPackardBell:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: DOA150
dmi.product.version: LU.B040B.016
dmi.sys.vendor: Packard Bell

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


** Tags: already-installed apport-package i386 xenial

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

Title:
  package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package
  hplip-data is already installed and configured

Status in hplip package in Ubuntu:
  New

Bug description:
  he conseguido agregar la impresora a pesar del error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hplip-data 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Nov 11 22:57:50 2019
  DuplicateSignature:
   package:hplip-data:3.16.3+repack0-1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libart-2.0-2:i386 (--configure):
package libart-2.0-2:i386 is already installed and configured
  ErrorMessage: package hplip-data is already installed and configured
  InstallationDate: Installed on 2019-11-11 (0 days ago)
  InstallationMedia:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Packard Bell DOA150
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=78936867-355d-46e8-9d95-523db97202d8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: hplip
  Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package 
hplip-data is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2008
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: v0.3103
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPackardBell:bvrv0.3103:bd10/09/2008:svnPackardBell:pnDOA150:pvrLU.B040B.016:rvnPackardBell:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: DOA150
  dmi.product.version: LU.B040B.016
  dmi.sys.vendor: Packard Bell

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

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

[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system

[Sebastien Bacher]

Could you check the available RAM/swap, could perhaps be that the system is 
running out of memory?
The log you added seems to confirm that
08:22:31 kernel: Out of memory: Kill process 4459 (gnome-shell) score 106 or 
sacrifice child

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

Title:
  Latest Firefox update freezing my system

Status in firefox package in Ubuntu:
  New

Bug description:
  The latest updates of firefox renders my machine useless. I'm sending
  it as is hopefully before it freezes completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  BuildID: 20190828152935
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 01:22:17 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-05-01 (506 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/20190828152935 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1851790] Re: Cheese webcam image dropping at random launch

[Sebastien Bacher]

Could you add the log from
$ GST_DEBUG=*cheese*:3 cheese

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

Title:
  Cheese webcam image dropping at random launch

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 development branch with kernel 5.3.0-18-generic all up to
  date to latest @ 8/11/2019

  After the launch of cheese webcam image drops to black image
  at random launches, sometimes after a reboot it works again
  properly, and the next launch goes to black again.

  Compared with Kamoso where everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 09:21:07 2019
  InstallationDate: Installed on 2019-10-25 (14 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021)
  MachineType: Notebook N7x0WU
  RelatedPackageVersions:
   cheese3.34.0-1
   cheese-common 3.34.0-1
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

[Desktop-packages] [Bug 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan

[Sebastien Bacher]

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

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

Title:
  On-screen keyboard does not appear automatically when selecting some
  text fields on Eoan

Status in chromium package in Ubuntu:
  New

Bug description:
  I get this on Eoan, no OSK pop up for Chromium text fields, on a
  laptop and a desktop.

  The OSK pops up fine on terminal, login field and text editor. It also
  doesn't work on Chrome.

  Curiously, when swiping up with mouse on the laptop the OSK doesn't
  come up when Chromium is on the view, but it comes up when on desktop.

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

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

[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

[Sebastien Bacher]

Can you open those steps
- ctrl-alt-T
$ nautilus -q
$ gdb nautilus
(gdb) r

(gdb) backtrace

Ideally with libglib2.0-0-dbgsym libgtk-3-0-dbgsym nautilus-dbgsym installed
(enabled of dbg source as explained on 
https://wiki.ubuntu.com/Debug%20Symbol%20Packages)

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

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

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

[Desktop-packages] [Bug 1842662] Re: Gnome Dash (vanilla - no extensions) first icon always missing unless you open the dash soon after login

[Sebastien Bacher]

Closing then since it seems fixed in 19.10

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

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

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

Title:
  Gnome Dash (vanilla - no extensions) first icon always missing unless
  you open the dash soon after login

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Using Vanilla Gnome session, with extensions turned off, the dash
  icons on the left of the screen do not display properly.

  The topmost icon is always missing (with the exception below) and
  replaced by a small empty square (which can still be clicked to open
  the application).

  This is very reproducible; I have the same issue on two separate
  machines, and the behaviour is identical

  * Opening the dash shortly after login prevents the problem from happening - 
all icons display correctly and remain correct for the duration of the session.
  * Waiting a while (e.g. one minute) after logging in before opening the dash 
will always result in the topmost icon being missing, and the only way to get 
it back is to restart the session.
  * It doesn't matter what application is placed in the topmost position on the 
dash - its icon will go missing.

  This doesn't seem to be related to extensions as I have extensions
  turned off in Tweaks, and both X11 and Wayland sessions have the same
  behavior.

  This is the same behavior as shown at this askubuntu link, and has been 
occurring ever since updating to 19.04: 
https://askubuntu.com/questions/1142990/first-most-application-icon-on-dash-hidden-until-gnome-shell-restarts?newreg=d0a226571a884b3fb3efed0639123106
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2013-12-07 (2132 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
  Tags:  wayland-session disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-31 (131 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1851139] Re: Firefox crashing about every 10-20 minutes

[Sebastien Bacher]

setting to incomplete until it happens again/crash details are provided

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

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

Title:
  Firefox crashing about every 10-20 minutes

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  no details yet. Since today's ubuntu 18.04 update my firefox is
  crashing completely about every 10-20 minutes while browsing.
  terminates immediately, all windows/tabs gone instantly.

  I'm not absolutely sure, but I'm unter the impression that it always
  happens when visiting pages with commercial ads or having such pages
  in a tab.

  Since I am hosting web sites with ads myself, I am aware that for
  about three weeks several readers complained about malware and page
  redirects, which have been limited to MacOS/iOS/Safari so far, but it
  proves that particular Browsers are under attack through embedded
  commercial ads. Thus, I am also not sure whether it is actually caused
  by today's update or just a conincidence. But it looks as if there's
  something out there which causes firefox to immediately crash and
  terminate. All windows immediately gone, program terminated. Smells
  like some sort of attack or maybe just a regular bug and no
  intentional attack.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 5779 F pulseaudio
  BuildID: 20191021054351
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Nov  3 16:20:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-06-09 (511 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=69.0.2/20191002193559 (Out of date)
   Profile2 (Default) - LastVersion=70.0/20191021054351 (In use)
   Profile1 - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=None/None (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  

[Desktop-packages] [Bug 1851865] Re: bug reporrt

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (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/1851865

Title:
  bug reporrt

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Not sure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-68.77~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-68-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  7 22:17:53 2019
  DistUpgraded: 2019-11-07 17:58:35,255 DEBUG /openCache(), new cache size 90136
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-66-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-68-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-66-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-68-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02a0]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02a0]
  InstallationDate: Installed on 2019-11-04 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Dell Inc. Studio 1737
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-68-generic 
root=UUID=28143eaf-551d-47e2-90aa-bfd9fb618e90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-11-07 (0 days ago)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1851956] Re: Initialization too slow, about 2 minutes. After is normal.

[Sebastien Bacher]

** Package changed: xorg (Ubuntu) => linux (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/1851956

Title:
  Initialization too slow, about 2 minutes. After is normal.

Status in linux package in Ubuntu:
  New

Bug description:
  When init the grub boot, stop and wait for 2 minutes, circa...
  After this time, normal speed and OS load normally, no problem !!! Ubuntu 
Studio 18.04 LTS. Sony Vaio VPCEE45B. 
  Ubuntu Studio 20.04 (Daily) work fine, without wait 
  Thanks
  

  (My english is bad,,,sorry)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18
  Uname: Linux 4.15.0-66-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov  9 16:26:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] 
[104d:9077]
  InstallationDate: Installed on 2019-11-08 (1 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Sony Corporation VPCEE45FB
  ProcEnviron:
   LANGUAGE=pt_BR
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0200Z5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEE45FB
  dmi.product.version: C8002NHR
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Nov  9 15:54:20 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1850064] [thunderbird/bionic] possible regression found

[Brian Murray]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of thunderbird from bionic-
proposed was performed and bug 1852097 was found.  Please investigate
this bug report to ensure that a regression will not be created by this
SRU. In the event that this is not a regression remove the
"verification-failed-bionic" tag from this bug report and add the tag
"bot-stop-nagging" to bug 1852097 (not this bug). Thanks!

** Tags added: verification-failed-bionic

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

Title:
  Please upgrade it to 68.x on Ubuntu 18.04 LTS

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

Bug description:
  Now the official upgrade way from 60 to 68 got open by mozilla.

  Plus there are security fixes and performance enhancements.
  
https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2

  NOTE TO SRU TEAM: Please do not release this package without
  consulting first. This is a security update pushed via -proposed to
  get a bit more testing. Will be released via it's own processes.

  Packages that are part of this security update: thunderbird, mozilla-
  devscripts, jsunit and enigmail.

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

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

[Desktop-packages] [Bug 1851807] Re: xdg-desktop-portal-gtk spams logs

[Sebastien Bacher]

Ken, do you think that's worth SRUIng?
https://github.com/flatpak/xdg-desktop-portal/commit/a3fd03f8

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Undecided => Low

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

Title:
  xdg-desktop-portal-gtk spams logs

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

Bug description:
  Every minute I get a log entry that looks like

  > xdg-desktop-por[ ]: Failed to get application states:
  GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
  list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App
  introspection not allowed

  Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal-
  gtk/issues/222

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xdg-desktop-portal-gtk 1.4.0-2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:51:30 2019
  InstallationDate: Installed on 2019-11-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852005] Re: IR connection off

[Sebastien Bacher]

Thank you for your bug report. Could you give details on the hardware
you are using? Is there any OS handling of the communication between the
dongle and the keyboard? It looks like it could rather be an hardware
issue... (did you check the keyboard batteries?)

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

** Changed in: linux (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/1852005

Title:
  IR connection off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  IR connection between keyboard and IR usb dongle don't work after
  update from 19.04 to 19.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Nov 10 17:45:17 2019
  DistUpgraded: 2019-11-09 21:16:11,874 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. 2nd Generation Core Processor 
Family Integrated Graphics Controller [19da:a166]
  InstallationDate: Installed on 2017-07-09 (854 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: MotherBoard By ZOTAC MotherBoard H67ITX-C-E
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=13b961a4-dd4b-4d07-b797-e439cb398142 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-11-09 (0 days ago)
  dmi.bios.date: 04/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A166P033
  dmi.board.asset.tag: NA
  dmi.board.name: H67ITX-C-E
  dmi.board.vendor: ZOTAC
  dmi.board.version: 05
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA166P033:bd04/13/2012:svnMotherBoardByZOTAC:pnMotherBoardH67ITX-C-E:pvrMotherBoard05:rvnZOTAC:rnH67ITX-C-E:rvr05:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: MotherBoard H67ITX-C-E
  dmi.product.sku: NA
  dmi.product.version: MotherBoard 05
  dmi.sys.vendor: MotherBoard By ZOTAC
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Sep 24 00:15:10 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

[Tom]

Randomly tried this :

apport-retrace --gdb  _usr_bin_nautilus.1000.crash

But that gave me:  "ERROR: report file does not contain one of the
required fields: Package"

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

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

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

[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

[Tom]

Is it possible the crash report auto-uploaded ( cb12411a-045e-11ea-
afb5-fa163e983629 ) ?

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

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

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

[Desktop-packages] [Bug 1852126] [NEW] [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound at all

[Antonio Pizarro]

Public bug reported:

i can listen normally but when i try to use the headphone the sound is
gone

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  aoplnx 1465 F pulseaudio
 /dev/snd/controlC0:  aoplnx 1465 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 15:04:02 2019
InstallationDate: Installed on 2019-11-11 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1012 F pulseaudio
  aoplnx 1465 F pulseaudio
 /dev/snd/controlC0:  gdm1012 F pulseaudio
  aoplnx 1465 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Squirtle_SR
dmi.board.vendor: SR
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd06/19/2018:svnAcer:pnAspireA315-21:pvrV1.12:rvnSR:rnSquirtle_SR:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-21
dmi.product.sku: 
dmi.product.version: V1.12
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i can listen normally but when i try to use the headphone the sound is
  gone

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aoplnx 1465 F pulseaudio
   /dev/snd/controlC0:  aoplnx 1465 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 15:04:02 2019
  InstallationDate: Installed on 2019-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1012 F pulseaudio
aoplnx 1465 F pulseaudio
   /dev/snd/controlC0:  gdm1012 F pulseaudio
aoplnx 1465 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Squirtle_SR
  dmi.board.vendor: SR
  dmi.board.version: V1.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd06/19/2018:svnAcer:pnAspireA315-21:pvrV1.12:rvnSR:rnSquirtle_SR:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire 3
  dmi.product.name: Aspire A315-21
  dmi.product.sku: 
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

[Tom]

Sorry I spend about 30 minutes trying to understand how to open a crash
report program. I followed your link and Googled, but these
"explanations" are so unclear that I cant get any further. I use Ubuntu
since version 11 I think and it's remarkable how complex that crash
reporting remained...

In meantime problem persists, also after cold reboot. There is no
message popping up as in the past, to report the bug. Just window
disappears..

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

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

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

[Desktop-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Sebastien Bacher]

Thank you for your bug report.

- What sound card/driver do you use? 
- Could you add your '$ journactl -b 0' log to the bug?
- Do you get the same problem if you play a sound using 'paplay'?

** Package changed: gdm3 (Ubuntu) => pulseaudio (Ubuntu)

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

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

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

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

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

[Desktop-packages] [Bug 1852113] Re: gdm logic for disabling wayland on nvidia is too rigid

[Sebastien Bacher]

Thank you for your bug report, the patch was removed on purpose the summary of 
the Ubuntu changes just got copied over without that bit removed
https://launchpad.net/ubuntu/+source/gdm3/3.32.0-1ubuntu2

The issue there seems to be 
'gdm will trigger a kernel oops in the i915 driver'

That's a kernel bug, could you report it using 'ubuntu-bug linux' and
include the logs/details of the oops error?

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

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

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

Title:
  gdm logic for disabling wayland on nvidia is too rigid

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  First observation is that the changelog here:

  https://bugs.launchpad.net/ubuntu/+source/gdm3/3.34.1-1ubuntu1

  says that the blacklisting of wayland+nvidia was reverted:

  + Add debian/patches/revert_nvidia_wayland_blacklist.patch:
- Don't blacklist nvidia for wayland

  But this patch isn't in the sources and the blacklist rule is still
  present.

  If I disable the udev blacklist rule, wayland on nvidia continues to
  work as well as it did in 19.04.

  However, I've been doing a bunch of playing around with hybrid
  configurations, and there is one situation, where there can be a
  problem. If you are using nvidia as your primary graphics device, but
  the Intel one is still visible on the pci bus (not disabled in
  firmware), then gdm will trigger a kernel oops in the i915 driver if
  wayland is not disabled. This didn't happen in 19.04 so it's a
  regression somewhere.

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

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

[Desktop-packages] [Bug 1852117] Re: non appare nessuna applicazione

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

** Changed in: xorg (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/1852117

Title:
  non appare nessuna applicazione

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  cliccando sul simbolo di ubuntu non appare nessuna applicazione
  neanche digitando il nome

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Nov 11 19:32:52 2019
  DistUpgraded: 2019-11-11 06:32:02,732 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
«./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:8023]
  InstallationDate: Installed on 2016-04-29 (1291 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Stream Notebook PC 11
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic 
root=UUID=e1727860-ed33-4311-9c36-c63aa9894bb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-11-11 (0 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8023
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 54.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.07:bd11/28/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Stream Notebook PC 11
  dmi.product.sku: L0N58EA#ABZ
  dmi.product.version: Type1 - ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Nov 11 19:22:49 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[Wissam Youssef]

Disabling switch on port and switching on connect for me is not ideal, since I 
have a bluetooth headphones that I still want to use from time to time.
I even tried to set a default sink in default.pa, still get hdmi on power 
events.
Installed pavucontrol to disable hdmi output, it  just resets on power events.

I just use
pacmd set-default-sink  
After each power event, annoying... hopefully this is fixed soon.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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

[Desktop-packages] [Bug 1852117] [NEW] non appare nessuna applicazione

[giuseppe]

Public bug reported:

cliccando sul simbolo di ubuntu non appare nessuna applicazione neanche
digitando il nome

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
Uname: Linux 5.3.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Nov 11 19:32:52 2019
DistUpgraded: 2019-11-11 06:32:02,732 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
«./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8))
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:8023]
InstallationDate: Installed on 2016-04-29 (1291 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Stream Notebook PC 11
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic 
root=UUID=e1727860-ed33-4311-9c36-c63aa9894bb6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-11 (0 days ago)
dmi.bios.date: 11/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8023
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.07:bd11/28/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Stream Notebook PC 11
dmi.product.sku: L0N58EA#ABZ
dmi.product.version: Type1 - ProductConfigId
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Mon Nov 11 19:22:49 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.5+git20191008-0ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 eoan 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/1852117

Title:
  non appare nessuna applicazione

Status in xorg package in Ubuntu:
  New

Bug description:
  cliccando sul simbolo di ubuntu non appare nessuna applicazione
  neanche digitando il nome

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Nov 11 19:32:52 2019
  DistUpgraded: 2019-11-11 06:32:02,732 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
«./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:8023]
  InstallationDate: Installed on 2016-04-29 (1291 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Stream Notebook PC 11
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic 
root=UUID=e1727860-ed33-4311-9c36-c63aa9894bb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 

[Desktop-packages] [Bug 1852113] [NEW] gdm logic for disabling wayland on nvidia is too rigid

[Philip Langdale]

Public bug reported:

First observation is that the changelog here:

https://bugs.launchpad.net/ubuntu/+source/gdm3/3.34.1-1ubuntu1

says that the blacklisting of wayland+nvidia was reverted:

+ Add debian/patches/revert_nvidia_wayland_blacklist.patch:
  - Don't blacklist nvidia for wayland

But this patch isn't in the sources and the blacklist rule is still
present.

If I disable the udev blacklist rule, wayland on nvidia continues to
work as well as it did in 19.04.

However, I've been doing a bunch of playing around with hybrid
configurations, and there is one situation, where there can be a
problem. If you are using nvidia as your primary graphics device, but
the Intel one is still visible on the pci bus (not disabled in
firmware), then gdm will trigger a kernel oops in the i915 driver if
wayland is not disabled. This didn't happen in 19.04 so it's a
regression somewhere.

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

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

Title:
  gdm logic for disabling wayland on nvidia is too rigid

Status in gdm3 package in Ubuntu:
  New

Bug description:
  First observation is that the changelog here:

  https://bugs.launchpad.net/ubuntu/+source/gdm3/3.34.1-1ubuntu1

  says that the blacklisting of wayland+nvidia was reverted:

  + Add debian/patches/revert_nvidia_wayland_blacklist.patch:
- Don't blacklist nvidia for wayland

  But this patch isn't in the sources and the blacklist rule is still
  present.

  If I disable the udev blacklist rule, wayland on nvidia continues to
  work as well as it did in 19.04.

  However, I've been doing a bunch of playing around with hybrid
  configurations, and there is one situation, where there can be a
  problem. If you are using nvidia as your primary graphics device, but
  the Intel one is still visible on the pci bus (not disabled in
  firmware), then gdm will trigger a kernel oops in the i915 driver if
  wayland is not disabled. This didn't happen in 19.04 so it's a
  regression somewhere.

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

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

[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

[Ronni]

I'm affected by this as well, with a Sony MDR-XB950BT - but it behaves
as intended in both Fedora and openSUSE.

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

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

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions

[Treviño]

Unfortunately due to a 3.34.1 git snapshot regression
(https://gitlab.gnome.org/GNOME/mutter/issues/896, fixed now) we had to
delay this upload, but the upload is in queue for few days now.


** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #896
   https://gitlab.gnome.org/GNOME/mutter/issues/896

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
  sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  In Progress
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color 
profile switching.
  The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict 
state changes when processing update” (which was intended to fix LP bug 
1847044).

  [ Test case ]

  - From gnome-control-center display panel, enable the Night Light
  - Force it on, and ensure that the display color temperature increases

  [ Regression potential ]

  Display gamma value might be incorrect

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus

[Treviño]

This specific issue has been fixed, in order to check what is yours you
should help us to identify it by using gdb to connect to the process.

Can you provide us such feedback?

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

Title:
  [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung
  in (varying functions under) meta_stack_get_default_focus_window()
  from meta_window_x11_focus()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  On my eaon system, closing any dialog in CLion (a Java program, which
  might be relevant) results in GNOME Shell hanging. I believe this to
  be a recent (in the last week or so, maybe?) regression.

  https://errors.ubuntu.com/problem/4a57302829116966b06eef27966d687ea662af4f

  [ Test case ]

   $ sudo snap install clion
   - Start clion, open a file
   - Hit Ctrl+Shift+F
   - Select Directory -> Click "..." to select the path
   - Hit OK / Cancel
   - The dialog should show and the shell should be responsive

  [ Regression potential ]

  The wrong window or no window is focused when a window is destroyed.

  ProblemType: HangDistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 28 17:27:00 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/usr/bin/fish
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ()
    () at /lib/x86_64-linux-gnu/libc.so.6
   g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sudo
  separator:

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

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

[Desktop-packages] [Bug 1852101] [NEW] Monitors keep turning on when in power saving mode, every time.

[BloodyIron]

Public bug reported:

Whenever I lock my computer, or it goes into power saving mode
automatically, the monitors turn back on and show the lock screen a few
seconds later. This has persisted now for about a year, has persisted
across multiple upgrades (18.10, 19.04, 19.10) as well as complete
hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD). So I'm
convinced this is a software bug.

The first line in logging that I can find that seems to trigger this is:

"gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance
'0x55daa50a2920' has no handler with id '145952'"

I update my system regularly, so this looks to either be a regression,
or uncaught bug. I don't know if other things are causing this, but
that's the first line (based on time) that is reported when it turns the
monitors back on.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 09:40:42 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-03-08 (247 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Monitors keep turning on when in power saving mode, every time.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I lock my computer, or it goes into power saving mode
  automatically, the monitors turn back on and show the lock screen a
  few seconds later. This has persisted now for about a year, has
  persisted across multiple upgrades (18.10, 19.04, 19.10) as well as
  complete hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD).
  So I'm convinced this is a software bug.

  The first line in logging that I can find that seems to trigger this
  is:

  "gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance
  '0x55daa50a2920' has no handler with id '145952'"

  I update my system regularly, so this looks to either be a regression,
  or uncaught bug. I don't know if other things are causing this, but
  that's the first line (based on time) that is reported when it turns
  the monitors back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 09:40:42 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-08 (247 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago)

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

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

[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly

[Ian Johnson]

Ah sorry my apologies I confused LZMA and LZO...

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

Title:
  [snap] Chromium snap starts slowly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The problem is shown here, https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/141 more
  graphically.

  Chromium snap takes quite a while to start and doesn't carry the
  system theme, whereas the chromium-browser folder taken off the
  snap/chromium starts practically immediately.

  The libcanberra-gtk3-module is missing inside the snap, and cannot use
  the module in the system.

  The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2
  MB, taken off the snap.

  Conclusion on Chromium snap on Ubuntu Eoan;
  Two bugs and a missing module
  1) Starts slowly,
  2) Cannot carry the system theme,
  3) Doesn't have libcanberra-gtk3-module

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

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

[Desktop-packages] [Bug 1852094] Re: chromium snap cannot open external apps by uri using xdg-open

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1776873
   Whitelisted allowedURLschemes breaks some desktop apps

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

Title:
  chromium snap cannot open external apps by uri using xdg-open

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
  like Gecko) snap Chromium/78.0.3904.97 Chrome/78.0.3904.97
  Safari/537.36

  Steps to reproduce the problem:
  0.run chromium snap on ubuntu
  1.open page with link like tg://resolve?domain=abcd=123
  2.click the link
  3.the dialog opens, click "open xdg-open" button

  What is the expected behavior?
  the system default app must open the link (telegram app in this case)

  What went wrong?
  after step 3, nothing happens.

  if chromium is run from terminal, one may see in terminal the
  following text:

  user-open error: Supplied URL scheme "tg" is not allowed

  Did this work before? Yes ubuntu 19.04, in apt-chromium

  Chrome version: 78.0.3904.97  Channel: stable
  OS Version: ubuntu 19.10

  pls note that the same link opens fine when clicked from "usual" apt
  chromium package (tested on both apt- and snap-chromium on ubuntu
  19.04, and on snap-chromium on 19.10).

  correctly working apt-chromium package was available till ubuntu
  19.04. now, since ubuntu 19.10, only snap-version of chromium is
  available which is broken

  i've already posted this bug on chromium bug tracker:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1023216#c2
  chromium's team member replied:
  Status: WontFix
  We don't maintain or build the snap distribution. You'll have to open an 
issue on ubuntu's bug reporting tool against this.

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

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

[Desktop-packages] [Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

[Amr Ibrahim]

Bug #1852097 Google Calendar provider is missing in Thunderbird 68.2.1
in bionic-proposed

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

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

Title:
  Please upgrade it to 68.x on Ubuntu 18.04 LTS

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

Bug description:
  Now the official upgrade way from 60 to 68 got open by mozilla.

  Plus there are security fixes and performance enhancements.
  
https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2

  NOTE TO SRU TEAM: Please do not release this package without
  consulting first. This is a security update pushed via -proposed to
  get a bit more testing. Will be released via it's own processes.

  Packages that are part of this security update: thunderbird, mozilla-
  devscripts, jsunit and enigmail.

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

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

[Desktop-packages] [Bug 1852097] [NEW] Google Calendar provider is missing in Thunderbird 68.2.1 in bionic-proposed

[Amr Ibrahim]

Public bug reported:

The Google Calendar provider is missing in Thunderbird 68.2.1 in bionic-
proposed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xul-ext-lightning 1:68.2.1+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  amr2089 F pulseaudio
BuildID: 20191031185816
Channel: Unavailable
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Mon Nov 11 17:19:31 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-11-29 (346 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 141.23.192.1 dev wlp6s0 proto dhcp metric 600 
 141.23.192.0/19 dev wlp6s0 proto kernel scope link src 141.23.216.93 metric 
600 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-b6869c51-47ea-4d0c-b5a8-08b020190419
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=68.2.1/20191031185816 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs: bp-b6869c51-47ea-4d0c-b5a8-08b020190419
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET57W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LTS01800
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LTS01800
dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

Title:
  Google Calendar provider is missing in Thunderbird 68.2.1 in bionic-
  proposed

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The Google Calendar provider is missing in Thunderbird 68.2.1 in
  bionic-proposed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xul-ext-lightning 1:68.2.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr2089 F pulseaudio
  BuildID: 20191031185816
  Channel: Unavailable
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Nov 11 17:19:31 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-11-29 (346 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 141.23.192.1 dev wlp6s0 proto dhcp metric 600 
   141.23.192.0/19 dev wlp6s0 proto kernel scope link src 141.23.216.93 metric 
600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-b6869c51-47ea-4d0c-b5a8-08b020190419
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=68.2.1/20191031185816 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-b6869c51-47ea-4d0c-b5a8-08b020190419
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly

[Jalon Funk]

"note that all snaps today actually use XZ compression, not LZMA."

xz = LZMA2 ( https://tukaani.org/xz/ ) which I guess is what was
referenced above.

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

Title:
  [snap] Chromium snap starts slowly

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The problem is shown here, https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/141 more
  graphically.

  Chromium snap takes quite a while to start and doesn't carry the
  system theme, whereas the chromium-browser folder taken off the
  snap/chromium starts practically immediately.

  The libcanberra-gtk3-module is missing inside the snap, and cannot use
  the module in the system.

  The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2
  MB, taken off the snap.

  Conclusion on Chromium snap on Ubuntu Eoan;
  Two bugs and a missing module
  1) Starts slowly,
  2) Cannot carry the system theme,
  3) Doesn't have libcanberra-gtk3-module

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

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

[Desktop-packages] [Bug 1852094] [NEW] chromium snap cannot open external apps by uri using xdg-open

[Anatoly]

Public bug reported:

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) snap Chromium/78.0.3904.97 Chrome/78.0.3904.97 Safari/537.36

Steps to reproduce the problem:
0.run chromium snap on ubuntu
1.open page with link like tg://resolve?domain=abcd=123
2.click the link
3.the dialog opens, click "open xdg-open" button

What is the expected behavior?
the system default app must open the link (telegram app in this case)

What went wrong?
after step 3, nothing happens.

if chromium is run from terminal, one may see in terminal the following
text:

user-open error: Supplied URL scheme "tg" is not allowed

Did this work before? Yes ubuntu 19.04, in apt-chromium

Chrome version: 78.0.3904.97  Channel: stable
OS Version: ubuntu 19.10

pls note that the same link opens fine when clicked from "usual" apt
chromium package (tested on both apt- and snap-chromium on ubuntu 19.04,
and on snap-chromium on 19.10).

correctly working apt-chromium package was available till ubuntu 19.04.
now, since ubuntu 19.10, only snap-version of chromium is available
which is broken

i've already posted this bug on chromium bug tracker:
https://bugs.chromium.org/p/chromium/issues/detail?id=1023216#c2
chromium's team member replied:
Status: WontFix
We don't maintain or build the snap distribution. You'll have to open an issue 
on ubuntu's bug reporting tool against this.

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

Title:
  chromium snap cannot open external apps by uri using xdg-open

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
  like Gecko) snap Chromium/78.0.3904.97 Chrome/78.0.3904.97
  Safari/537.36

  Steps to reproduce the problem:
  0.run chromium snap on ubuntu
  1.open page with link like tg://resolve?domain=abcd=123
  2.click the link
  3.the dialog opens, click "open xdg-open" button

  What is the expected behavior?
  the system default app must open the link (telegram app in this case)

  What went wrong?
  after step 3, nothing happens.

  if chromium is run from terminal, one may see in terminal the
  following text:

  user-open error: Supplied URL scheme "tg" is not allowed

  Did this work before? Yes ubuntu 19.04, in apt-chromium

  Chrome version: 78.0.3904.97  Channel: stable
  OS Version: ubuntu 19.10

  pls note that the same link opens fine when clicked from "usual" apt
  chromium package (tested on both apt- and snap-chromium on ubuntu
  19.04, and on snap-chromium on 19.10).

  correctly working apt-chromium package was available till ubuntu
  19.04. now, since ubuntu 19.10, only snap-version of chromium is
  available which is broken

  i've already posted this bug on chromium bug tracker:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1023216#c2
  chromium's team member replied:
  Status: WontFix
  We don't maintain or build the snap distribution. You'll have to open an 
issue on ubuntu's bug reporting tool against this.

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

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

[Desktop-packages] [Bug 1848489] Re: [SRU] libreoffice 6.2.8 for disco

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:6.2.8-0ubuntu0.19.04.1

---
libreoffice (1:6.2.8-0ubuntu0.19.04.1) disco; urgency=medium

  * New upstream release (LP: #1848489)

 -- Marcus Tomlinson   Thu, 17 Oct 2019
12:34:51 +0100

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

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

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

Title:
  [SRU] libreoffice 6.2.8 for disco

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.2.8 is in its eighth bugfix release of the 6.2 line.
     For a list of fixed bugs compared to 6.2.7 see:
   https://wiki.documentfoundation.org/Releases/6.2.8/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.2.8/RC2#List_of_fixed_bugs
     (that's a total of 26 bugs)

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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