date:20200605

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

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  when installing ubuntu I went to open the livepatch and the error
  appeared add-apt-repository crashed with OSError in __main__: [Errno
  5] Erro de entrada/saída

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  there is not

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: software-properties-common 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Sat Apr  4 11:39:13 2020
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:webupd8team/java
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:webupd8team/java']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with OSError in __main__: [Errno 5] Erro de 
entrada/saída
  Traceback:
   Traceback (most recent call last):
 File "/usr/bin/add-apt-repository", line 158, in 
   sys.stdin.readline()
   OSError: [Errno 5] Erro de entrada/saída
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1870787] Re: soffice.bin crashed with SIGABRT in GtkSalMenu::~GtkSalMenu()

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

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

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

Title:
  soffice.bin crashed with SIGABRT in GtkSalMenu::~GtkSalMenu()

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  When I change the size of the icon menu it stumbled then created the
  report, but it may be a bug with libreoffice.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr  4 09:36:49 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer
  Signal: 6
  SourcePackage: libreoffice
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/libreoffice/program/libvclplug_gtk3lo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_gtk3lo.so
   Menu::dispose() () from /usr/lib/libreoffice/program/libmergedlo.so
   VCLXMenu::~VCLXMenu() () from /usr/lib/libreoffice/program/libmergedlo.so
  Title: soffice.bin crashed with SIGABRT in Menu::dispose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1867821] Re: gnome-calculator crashed with signal 5 in g_object_new_valist()

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

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

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

Title:
  gnome-calculator crashed with signal 5 in g_object_new_valist()

Status in gnome-calculator package in Ubuntu:
  Expired

Bug description:
  calculator gives error reports.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-calculator 1:3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 00:15:02 2020
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2019-12-18 (90 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: gnome-calculator --solve cal
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-calculator
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-calculator crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1870624] Re: fails to install after password prompt

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

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

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

Title:
  fails to install after password prompt

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  1) Description:   Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) gnome-software:
Installed: 3.35.91-0ubuntu1
Candidate: 3.35.91-0ubuntu1
Version table:
   *** 3.35.91-0ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Opera installation

  4) Blank error

  
  Screenshot: https://imgur.com/TWGk02s.png

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

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

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

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

Title:
  Authentication required window after startup

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

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected

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

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

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

Title:
  pulseaudio still trying to reproduce audio to HDMI without the HDMI
  cable connected

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Yesterday I was using the HDMI cable to duplicate the monitor in the
  tv and play sound with the tv by selecting HDMI exit sound in ubuntu
  settings.

  With the pc turned off I removed the HDMI from the tv but ubuntu
  doesn't automatically set the exit sound to the default till in the
  settings there is only that option and till I selected it, ubuntu was
  still trying to reproduce the audio via HDMI...

  Also rebooting the system the problem persists.

  Also by reloading pulseaudio the problem persists.

  The only solution was installing a third-party program to switch
  correctly to the default audio exit...

  lsb_release -rd:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  apt-cache policy pulseaudio:
  pulseaudio:
Installato: 1:11.1-1ubuntu7.2
Candidato:  1:11.1-1ubuntu7.4
Tabella versione:
   1:11.1-1ubuntu7.4 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 1:11.1-1ubuntu7.2 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

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

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

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

Title:
  Authentication required window after startup

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

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870901] Re: soffice.bin crashed with SIGSEGV

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

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

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

Title:
  soffice.bin crashed with SIGSEGV

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  I was trying to save a server based spreadsheet after amending

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Apr  5 11:25:30 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
/home/username/.cache/kioexec/krun/6264_0/Budget2019-20.xlsx
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libsclo.so
   ?? () from /usr/lib/libreoffice/program/libsclo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_qt5lo.so
   ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
  Title: soffice.bin crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1871201] Re: package gnome-user-docs-es 3.36.1-0ubuntu1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

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

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

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

Title:
  package gnome-user-docs-es 3.36.1-0ubuntu1 failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 2

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

Bug description:
  Happened straight after a fresh install of Ubuntu 20.04 and doing its
  first update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gnome-user-docs-es 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Mon Apr  6 20:12:52 2020
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1
  SourcePackage: gnome-user-docs
  Title: package gnome-user-docs-es 3.36.1-0ubuntu1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2020-06-05 Thread Hui Wang

The oem project is waiting for the fix while upstream has no final
solution. How about we merge this fix as ubuntu specific part first,
once upstream has a solution, let's revert this fix and apply the
upstream's one？

thx,
Hui.

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

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

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in pulseaudio source package in Focal:
  Incomplete
Status in pulseaudio source package in Groovy:
  Incomplete

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

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

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

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

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. This 
fix is not accepted by upstream yet. Maybe we could apply this fix to ubuntu 
specific part, if the upstream has a solution for this issue in the future, we 
could revert this fix and merge the uptream's solution then.

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

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

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

2020-06-05 Thread Hui Wang

** Description changed:

- This bug is for tracking purpose.
+ This bug originates from an OEM private bug #1875597, then ubuntu users
+ reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
+ and the 1st issue of #1881659 have the same root cause as #1875597
+ 
+ [Impact]
+ On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.
+ 
+ [Fix]
+ The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2. 
+ 
+ [Test Case]
+ applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.
+ 
+ [Regression Risk]
+ Low, just do a small change to store the ucm devices by their priority. This 
fix is not accepted by upstream yet. Maybe we could apply this fix to ubuntu 
specific part, if the upstream has a solution for this issue in the future, we 
could revert this fix and merge the uptream's solution then.

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

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

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in pulseaudio source package in Focal:
  Incomplete
Status in pulseaudio source package in Groovy:
  Incomplete

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

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

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

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

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. This 
fix is not accepted by upstream yet. Maybe we could apply this fix to ubuntu 
specific part, if the upstream has a solution for this issue in the future, we 
could revert this fix and merge the uptream's solution then.

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

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

[Desktop-packages] [Bug 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

2020-06-05 Thread Corentin Noël

@seb128 Tested it since it is available in focal-proposed and it solved
the issue for me. I haven't noticed any issue so far.

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

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

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

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

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

[Desktop-packages] [Bug 1882309] [NEW] Cutted off font on Facebook in Firefox

2020-06-05 Thread Konrad Kołodziejczyk

Public bug reported:

The domain of site is cutted off on Facebook site as it is seen on this 
screenshot. 
https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png
I've seen this problem in Ubuntu 20.04 and I haven't seen in Ubuntu 19.10. This 
issue is merely in Firefox. Facebook site in Google Chrome looks ok.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 77.0.1+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  konrad 1159 F pulseaudio
 /dev/snd/pcmC1D0p:   konrad 1159 F...m pulseaudio
 /dev/snd/controlC0:  konrad 1159 F pulseaudio
BuildID: 2020060727
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: MATE
Date: Sat Jun  6 00:05:28 2020
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:731
DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source-directory /etc/network/interfaces.d
InstallationDate: Installed on 2020-06-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
IpRoute:
 default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.8 metric 600
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:731
Profile0PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntumate.js
 prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=77.0.1/2020060727 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.name: 0V8RX3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd11/25/2019:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7250
dmi.product.sku: 062D
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  Cutted off font  on Facebook in Firefox

Status in firefox package in Ubuntu:
  New

Bug description:
  The domain of site is cutted off on Facebook site as it is seen on this 
screenshot. 
  https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png
  I've seen this problem in Ubuntu 20.04 and I haven't seen in Ubuntu 19.10. 
This issue is merely in Firefox. Facebook site in Google Chrome looks ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 77.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  konrad 1159 F pulseaudio
   /dev/snd/pcmC1D0p:   konrad 1159 F...m pulseaudio
   /dev/snd/controlC0:  konrad 1159 F pulseaudio
  BuildID: 2020060727
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sat Jun  6 00:05:28 2020
  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:731
  DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   #

[Desktop-packages] [Bug 1882237] Re: Libre Office doesn't start at all (wrong library version)

2020-06-05 Thread Leo Cacciari

@hellsworth I tried your suggestion, but it didn't solve the problem: it
still complains that it can find the 63 version of libicui18n

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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

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

[Desktop-packages] [Bug 1880806] Re: Gedit unable to save preferences on 20.04

2020-06-05 Thread Balazs Gyurak

> The issue seems specific to your system.
Interesting, I assumed it was a bug with Focal. I appreciate you taking the 
time to look into it!

> change the setting in gedit and see if there is a change printed
No change is printed while 'gsettings monitor' is running. Tried with other 
'org.gnome.gedit.preferences.editor' keys as well. I presume this is why it 
doesn't persist? The change made on the UI does not get through to gsettings?

> gsettings set org.gnome.gedit.preferences.editor display-line-numbers false
Yes this works, setting the properties with the above command persists as 
expected.

> $ dpkg -l | grep dconf
ii  dconf-cli   0.36.0-1
  amd64simple configuration storage system 
- utilities
ii  dconf-editor3.36.0-1
  amd64simple configuration storage system 
- graphical editor
ii  dconf-gsettings-backend:amd64   0.36.0-1
  amd64simple configuration storage system 
- GSettings back-end
ii  dconf-service   0.36.0-1
  amd64simple configuration storage system 
- D-Bus service
ii  libdconf1:amd64 0.36.0-1
  amd64simple configuration storage system 
- runtime library

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

Title:
  Gedit unable to save preferences on 20.04

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By 
default, it came with the following:
  Display line numbers: on
  Display right margin: off
  Highlight current line: on
  Text wrapping: on

  I wanted to disable the first and third option, so I did. It works as
  long as gedit is open, but if I close and reopen it, the settings were
  reverted.

  Repro steps:
  1. Open gedit
  2. Toggle the "Highlight current line" preference
  3. Close gedit
  4. Open gedit again
  5. Observe that the "Highlight current line" preference is reverted to the 
original value

  Expected behavior
  Gedit persists preferences after closing & reopening

  Actual behavior:
  Gedit does not persist preferences after closing & reopening

  Workaround:
  Using gsettings seemed to do the trick. I've run:
  gsettings set org.gnome.gedit.preferences.editor highlight-current-line false
  gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

  This persists the settings correctly, so I believe the bug is related
  to the UI.

  Additional information:
  OS: Ubuntu 20.04
  Package: /usr/bin/gedit
  Version: 3.36.2-0ubuntu1

  Thanks,
  Balazs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 06:37:36 2020
  InstallationDate: Installed on 2018-11-05 (568 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

@Corentin, any chance you could test if the SRU resolve the issue for
you?

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

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

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

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

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

[Desktop-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

The fix is not easy to confirm since it's random and the errors report
are against services using it like gdm so the 'version it's happening
with table' don't tell us what version of e.g gdm was in use and not
accountsservice

The updated 0ubuntu12~20.04.1 version works without visible problems
though and the fix is simple and got upstream reviewed. There are also
no regression reported

Based on those facts I'm going to mark the SRU as verified

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

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  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: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1878010] Re: SRU the current 3.36.1 stable update

The 3.36.1-2ubuntu0.20.04.2 update seems fine, no visible problems
noticed nor new reports

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

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

Title:
  SRU the current 3.36.1 stable update

Status in adwaita-icon-theme package in Ubuntu:
  Fix Released
Status in adwaita-icon-theme source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, which includes a handful of icon 
updates/fixes 
(https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/blob/master/NEWS).

  
  * Test case

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

  Switch to adwaita and verify that all icons in the shell and in GTK
  applications are rendered correctly.

  
  * Regression potential

  Visual changes only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1878010/+subscriptions

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

[Desktop-packages] [Bug 1870847] Re: App grid has too many page dots on right

@Łukasz, the fix there is correct, if there is another problem with the
newer gnome-shell SRU it's not something created by the ubuntucok
package update. As Marco stated the SRU also includes other fixes. Since
there are no regression and only improvement I'm setting it back as
verified

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

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

Title:
  App grid has too many page dots on right

Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1877093] Re: [SRU] New stable release 2.34.2

Things seems happy with 2.34.2-0ubuntu2~20.04.1, no problem seen in
local testing nor new bugs reported, the autopkgtests are green now,
marking as verified

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

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

Title:
  [SRU] New stable release 2.34.2

Status in at-spi2-atk package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of at-spi2-atk.

  Changes:

  What's new in at-spi2-atk 2.34.2:

  * Meson: don't hard-code shared_library (!19).

  * Mitigate missing window events at startup.

  * Set C standard to gnu99 (#10).

  * Tests: include sys/time.h (#14).

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

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

  Install the desktop and exercise the screen reader in a variety of
  situations.

  Optionally, but ideally, test the installer too.

  [ Regression potential ]

  If this update is busted the screen reader might not work. This
  changes the C standard too, which should be fine, but make sure to do
  some QA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

@Chris, the current security update that is currently in focal-updates
is missing the risv64 build so that isn't a regression compared to the
current situation, could that update be unblocked and we will look at
fixing the test issues in the next upload

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1880806] Re: Gedit unable to save preferences on 20.04

> Out of curiosity, is this something that you are able to reproduce, or
is it just on my system?

The issue seems specific to your system.


Could you do
$ gsettings monitor org.gnome.gedit.preferences.editor display-line-numbers

change the setting in gedit and see if there is a change printed

and 
$ dpkg -l | grep dconf

and could you try if doing 
$ gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

works and keeps the change?

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

Title:
  Gedit unable to save preferences on 20.04

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By 
default, it came with the following:
  Display line numbers: on
  Display right margin: off
  Highlight current line: on
  Text wrapping: on

  I wanted to disable the first and third option, so I did. It works as
  long as gedit is open, but if I close and reopen it, the settings were
  reverted.

  Repro steps:
  1. Open gedit
  2. Toggle the "Highlight current line" preference
  3. Close gedit
  4. Open gedit again
  5. Observe that the "Highlight current line" preference is reverted to the 
original value

  Expected behavior
  Gedit persists preferences after closing & reopening

  Actual behavior:
  Gedit does not persist preferences after closing & reopening

  Workaround:
  Using gsettings seemed to do the trick. I've run:
  gsettings set org.gnome.gedit.preferences.editor highlight-current-line false
  gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

  This persists the settings correctly, so I believe the bug is related
  to the UI.

  Additional information:
  OS: Ubuntu 20.04
  Package: /usr/bin/gedit
  Version: 3.36.2-0ubuntu1

  Thanks,
  Balazs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 06:37:36 2020
  InstallationDate: Installed on 2018-11-05 (568 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

2020-06-05 Thread John Jacob

I repeated the steps on my laptop. The previous report was from the VM.

Look at the gnome-shell crash received on 2020-06-05 20:06 UTC at:
https://errors.ubuntu.com/user/27232d1c0322b0e12fbced3d5cc680848662bdab3723e8c5a2ef4f4994f0f37d64c8663e929ae708ddbfce7b00cf9529860901cc62597a8b0b414d4b29fc9792


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

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

Title:
  wayland session hard freezes on login from GDM (X11 session works
  fine)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │

[Desktop-packages] [Bug 1782581] Re: simple-scan on Ubuntu 18.04 does not find wireless scanner

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

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  simple-scan on Ubuntu 18.04 does not find wireless scanner

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  Scanner is combined with all-in-one device CANON TS8000 series.
  Scangearmp is able to find scanner and scan the document.

  Both simple-scan and xsane fails to detect scanner.

  apt-cache policy simple-scan
  simple-scan:
    Installed: 3.28.0-0ubuntu1
    Candidate: 3.28.0-0ubuntu1
    Version table:
   *** 3.28.0-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  From the logs app I notice this when using simple-sacan:-
  io/hpmud/model.c 532: no on_ts8000_series attributes found in 
/usr/share/hplip/data/models/models.dat

  The exact same but with 543 instead of 532 and then the exact same log
  when using x-sane

  They are mentioned in the "Security" logs and "Applications" logs

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

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

[Desktop-packages] [Bug 1782581] Re: simple-scan on Ubuntu 18.04 does not find wireless scanner

2020-06-05 Thread Smittie

Ubuntu 18.04 LTS clean install
SANE & XSANE latest versions as of 05Jun2020

Simple Scan cannot find the Canon MF731C/733C multi-function 
printer/copier/scanner.
The same computer prints to the Canon MF731C/733C without issue.

If I make an entry in pixma.conf specific to the MF731C/733C, XSANE says
it cannot read the MAC address and then that is cannot read the make and
model.

smittie@ranchhacks-1:~$ xsane
[bjnp] udp_command: ERROR - no data received (timeout = 5000)
[bjnp] bjnp_init_device_structure: Cannot read mac address, skipping this 
scanner
[bjnp] udp_command: ERROR - no data received (timeout = 5000)
[bjnp] add_scanner: ERROR - Cannot read scanner make & model: 
bjnp://192.168.30.18:8612/timeout=5000
s


avahi-discover can see the scanner including manufacturer and model when it 
does the _scanner._tcp scan.

Service data for service 'RanchHacks-Printer' of type '_scanner._tcp' in domain 
'local' on 2.0:
Host RanchHacks-Printer.local (192.168.30.18), port 8610, TXT data: 
['scannerAvailable=1', 'mdl=MF731C/733C', 'mfg=Canon', 'UUID=f80d60ea4433', 
'ty=Canon MF731C/733C', 
'adminurl=http://RanchHacks-Printer.local:80/airprint.html', 'note=', 
'txtvers=1']

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

Title:
  simple-scan on Ubuntu 18.04 does not find wireless scanner

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  Scanner is combined with all-in-one device CANON TS8000 series.
  Scangearmp is able to find scanner and scan the document.

  Both simple-scan and xsane fails to detect scanner.

  apt-cache policy simple-scan
  simple-scan:
    Installed: 3.28.0-0ubuntu1
    Candidate: 3.28.0-0ubuntu1
    Version table:
   *** 3.28.0-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  From the logs app I notice this when using simple-sacan:-
  io/hpmud/model.c 532: no on_ts8000_series attributes found in 
/usr/share/hplip/data/models/models.dat

  The exact same but with 543 instead of 532 and then the exact same log
  when using x-sane

  They are mentioned in the "Security" logs and "Applications" logs

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

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

[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

** No longer affects: glib2.0 (Ubuntu Focal)

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1869963] Re: Unable to install chromium-browser in docker

2020-06-05 Thread Fedor Korotkov

Disclaimer: I'm working on a CI system.

Another 2 cents about this issue affecting CI systems, not only our CI-
as-a-service solution but most of the modern CIs that embrace Docker
containers for reproducibility and isolation of the CI builds. This
issue means that people won't be able to run integration tests in
browsers as they used to. In our experience this technique is becoming
quite popular recently in front-end projects, just check Puppeteer or
Playwright projects.

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

Title:
  Unable to install chromium-browser in docker

Status in cloud-images:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce: Create a docker container with the official image
  "ubuntu:focal". Inside of the container, run "apt-get install
  chromium-browser".

  Expected results: Chromium is installed.

  Actual results: Chromium installation fails. The error is telling me
  that it is unable to reach the snap store (probably because snapd is
  not running).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions

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

[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

** Description changed:

+ [ Impact ]
+ 
+ gnome-shell-hotplug-sniffer crashes when attaching some device that may
+ have files with unknown content type
+ 
+ [ Test case ]
+ 
+ - Plug a media, but it's not yet known which kind of files cause this issue,
+   so we should just monitor the e.u.c crash:
+   https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9
+ 
+ [ Regression potential ]
+ 
+ - No valid application for opening a media is shown by gnome-shell
+ 
+ ---
+ 
+ This is for 3.34:
+ 
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
- https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9
  
  ---
  
  Happened during normal use of the desktop.
  
- ProblemType: Crash
- DistroRelease: Ubuntu 20.04
+ ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
- Signal: 11
- SourcePackage: gnome-shell
+ Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  In Progress
Status in glib2.0 source package in Focal:
  New
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from

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

2020-06-05 Thread David O Neill

Worked for me, require reboot, but then you can do fractional scaling

https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1870736/comments/86

root@dave-x1e:/home/dmzoneill/bin# lspci | grep -i nvidia
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 
Mobile / Max-Q] (rev a1)

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X

2020-06-05 Thread Matteo Pedani

After I removed the network manager to static old configuration, I had many 
plroblems like that.
But even if I "sudo apt-get install network-manager libteam-utils 
network-manager-gnome" I can't solve the problem. How to reset the network to 
default state?

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

Title:
  Certain features in the Sharing panel fail with D-Bus related messages
  when gnome-control-center is run over ssh -X

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu
  20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media
  Sharing in the Sharing panel (*) fails with the following D-Bus
  related messages on the standard error:

  --
  (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: 
couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files

  (gnome-control-center:25937): sharing-cc-panel-WARNING **:
  00:15:28.646: Failed to enable service vino-server:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SettingsDaemon.Sharing was not provided by any .service
  files

  (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: 
Failed to enable service rygel: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SettingsDaemon.Sharing was not provided by any .service files
  --

  What does this mean? Can I do anything about it? A remote user,
  sitting in front of the remote computer, can enable Screen Sharing or
  Media Sharing in gnome-control-center themselves. Failure to enable
  only occurs over ssh -X, as far as I can tell.

  Looking up this error online led me down a D-Bus rabbit hole. I found
  many year-old StackExchange answers that recommend setting various
  environment variables and/or running dbus-launch to start a session
  bus instance of dbus-daemon, in case of D-Bus related errors.

  I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep
  dbus that a session bus instance of dbus-daemon is already running. It
  has been started under my UID at the time of my SSH login. So I'm wary
  of those old resources. I have tried following their instructions
  though, for completeness sake, but to no avail. I can provide more
  information if necessary.

  (*) This odd situation happened when I had to provide technical
  support over VNC to an older user whose computer I had previously set
  up with SSH access. Hence why I was using ssh -X to try and enable VNC
  in gnome-control-center...

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

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

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

2020-06-05 Thread David O Neill

Worked for me, require reboot, but then you can do fractional scaling


https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/comments/86

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1845491] Re: CTRL + "Single Click" fails to un-select a selected icon

Confirmed working with:

$ apt-cache policy gnome-shell-extension-desktop-icons
gnome-shell-extension-desktop-icons:
  Installed: 20.04.0-2~ubuntu20.04.1
  Candidate: 20.04.0-2~ubuntu20.04.1
  Version table:
 *** 20.04.0-2~ubuntu20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages
100 /var/lib/dpkg/status
 20.04.0-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages

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

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

Title:
  CTRL + "Single Click" fails to un-select a selected icon

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Committed

Bug description:
  When selecting multiple files using CTRL + click, I noticed that I
  could NOT undo a selection by CRTL + clicking on it again.

  Inside the Nautilus file browser, however, this issue is NOT present.
  From my testing, the issue is only present on the desktop.

  
  PS: I filed this as a nautilus bug since desktop-icon related bugs are tagged 
as nautilus issues in this link: 
https://wiki.ubuntu.com/Bugs/FindRightPackage#Graphical_Environment

  ==
  SYSTEM INFORMATION
  ==

  lsb_release -rd
  ===
  Description:  Ubuntu 19.04
  Release:  19.04

  apt-cache policy nautilus
  =
  nautilus:
Installed: 1:3.32.1-0ubuntu0.19.04.0
Candidate: 1:3.32.1-0ubuntu0.19.04.0
Version table:
   *** 1:3.32.1-0ubuntu0.19.04.0 500
  500 http://ca.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.32.0-0ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 17:40:24 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(768, 789)'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2019-06-15 (102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1882237] Re: Libre Office doesn't start at all (wrong library version)

2020-06-05 Thread Heather Ellsworth

> Now, the libicu is (obviously) installed, but the installed version is 66, 
> not 63. Version 66, BTW, is the one listed as dependency for the libre office 
> package.

That is correct, libicu is v66 in ubuntu 20.04. Perhaps something funky
happened in your update from 18.10 to 20.04. I would recommend removing
libreoffice and reinstalling it

$ sudo apt update && sudo apt dist-upgrade
$ sudo apt-get remove --purge libreoffice*
$ sudo apt install libreoffice

Then lowriter should work.

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

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

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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

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

[Desktop-packages] [Bug 1879375] Re: Images thumbnails doesn't update on image changes

Tested with

$ apt-cache policy gnome-shell-extension-desktop-icons
gnome-shell-extension-desktop-icons:
  Installed: 20.04.0-2~ubuntu20.04.1
  Candidate: 20.04.0-2~ubuntu20.04.1
  Version table:
 *** 20.04.0-2~ubuntu20.04.1 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages
100 /var/lib/dpkg/status
 20.04.0-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages

Fixed version works

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

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

Title:
  Images thumbnails doesn't update on image changes

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Image thumbnails are not refreshed on file changes

  [ Test case ]

  1. Create a new image and save it in the desktop using your image editor
  2. Change the image content and save
  3. The image thumbnail in the desktop should reflect the changes

  [ Regression potential ]

  Icons updates (and so redraws) may increase even when there are no
  actual changes to perform.

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

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

[Desktop-packages] [Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed

** Changed in: mutter (Ubuntu Focal)
   Status: Triaged => In Progress

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

Title:
  gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost'' failed

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  In Progress

Bug description:
  [Impact]

  This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's
  duplicated across multiple problem reports according to locale:

  https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c
  https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b
  https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7
  https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0

  [Test Case]

  None known. The plan is to just continue monitoring crash reports.
  Still, we are confident this is the fix because:

   * The offending source code in libx11 tells us it is :) and
   * The crash only started in Ubuntu with gnome-shell 3.34, which is the
     exact release in which XInitThreads was removed from mutter.

  [Regression Potential]

  Low. We add a single function call that tells libX11 to enable thread
  safety. This same function call as one we had in bionic, cosmic and
  disco.

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

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

[Desktop-packages] [Bug 1882271] [NEW] adwaita-icon-theme is missing window action icons

Public bug reported:

[ Impact ]

Various window-* operation icons are missing in the adwaita-icon-theme
(but available in the full one) even if they're fundamental for gtk
apps.

In focal the icons are:

dpkg -L adwaita-icon-theme | grep "window-.*"  
/usr/share/icons/Adwaita/scalable/ui/window-close-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-maximize-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-minimize-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-new-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-restore-symbolic.svg

[ Test case ]

dpkg -L adwaita-icon-theme | grep "window-.*"

It should contain

/usr/share/icons/Adwaita/16x16/legacy/window-close.png
/usr/share/icons/Adwaita/16x16/legacy/window-new.png
/usr/share/icons/Adwaita/16x16/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/16x16/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/16x16/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/16x16/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/16x16/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/22x22/legacy/window-close.png
/usr/share/icons/Adwaita/22x22/legacy/window-new.png
/usr/share/icons/Adwaita/24x24/legacy/window-close.png
/usr/share/icons/Adwaita/24x24/legacy/window-new.png
/usr/share/icons/Adwaita/24x24/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/24x24/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/24x24/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/24x24/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/24x24/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/legacy/window-close.png
/usr/share/icons/Adwaita/32x32/legacy/window-new.png
/usr/share/icons/Adwaita/32x32/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/legacy/window-close.png
/usr/share/icons/Adwaita/48x48/legacy/window-new.png
/usr/share/icons/Adwaita/48x48/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/ui/window-close-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/ui/window-maximize-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/ui/window-minimize-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/ui/window-new-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/ui/window-restore-symbolic.symbolic.png
/usr/share/icons/Adwaita/scalable/ui/window-close-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-maximize-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-minimize-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-new-symbolic.svg
/usr/share/icons/Adwaita/scalable/ui/window-restore-symbolic.svg


[ Regression potential ]

Fixed-size icons may be chosen in some cases, leading some slight
quality loss.

** Affects: adwaita-icon-theme (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Committed

** Affects: adwaita-icon-theme (Ubuntu Focal)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Also affects: adwaita-icon-theme (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: adwaita-icon-theme (Ubuntu Focal)
   Status: New => In Progress

** Changed in: adwaita-icon-theme (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: adwaita-icon-theme (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  adwaita-icon-theme is missing window action icons

Status in adwaita-icon-theme package in Ubuntu:
  Fix Committed
Status in adwaita-icon-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  Various window-* operation icons are missing in the adwaita-icon-theme
  (but available in the full one) even if they're fundamental for gtk
  apps.

  In focal the icons are:

  dpkg -L

[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-06-05 Thread Lance Parsons

Correction: I have the same display issue, but WiFi IS working on Dell
Precision 5520, Unbuntu 20.04.

My apologies, there was an unrelated DHCP issue, but this display
problem got me going down the wrong path to fix it.

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1882267] [NEW] nautilus Find function stuck in 'full text' search mode

2020-06-05 Thread larrybradley

Public bug reported:

After searching in "Full Text" mode in Nautilus, then changing to
"Filename" search mode, Nautilus continues to return results based on
"Full Text" mode. Example: I opened Files program, clicked on Find, then
clicked the drop-down and selected "File Name". I then searched for the
word "atlantic." The results returned not only file names with
"atlantic" in them, but file names that did not contain "atlantic" in
the file title, but where the word "atlantic" could be found in the body
of the file's text.

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

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

Title:
  nautilus Find function stuck in 'full text' search mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  After searching in "Full Text" mode in Nautilus, then changing to
  "Filename" search mode, Nautilus continues to return results based on
  "Full Text" mode. Example: I opened Files program, clicked on Find,
  then clicked the drop-down and selected "File Name". I then searched
  for the word "atlantic." The results returned not only file names with
  "atlantic" in them, but file names that did not contain "atlantic" in
  the file title, but where the word "atlantic" could be found in the
  body of the file's text.

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

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

[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

** Tags added: fixed-in-3.37.3 fixed-upstream

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)

2020-06-05 Thread Noctis Bennington

Apparently this happens to Ubuntu 18.04.4 and 19.10 (and obviously on
20.04). But on 18.04.1 the second monitor works perfectly. Windows 10
too.

This seems like a mistake or bug on the Mesa/Kernel.

At the moment, I'll be on 18.04.1 but updated.

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

Title:
  Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS
  Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-utils package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with noveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

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

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

[Desktop-packages] [Bug 1882258] [NEW] XRDP to Ubuntu 19.10 request many popup dialog for creating a colorprofile

2020-06-05 Thread AdlerHorst

Public bug reported:

While searching abougt a solution I found this Blogpost which was able to help 
me in this case:
https://c-nergy.be/blog/?p=12073

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

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

Title:
  XRDP to Ubuntu 19.10 request many popup dialog for creating a
  colorprofile

Status in policykit-1-gnome package in Ubuntu:
  New

Bug description:
  While searching abougt a solution I found this Blogpost which was able to 
help me in this case:
  https://c-nergy.be/blog/?p=12073

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

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

[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

I've prepared a mitigation in gnome-shell as
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1302

However, it may be that both debian and ubuntu are lacking some mime
type definitions, as it looks weird to me that it we're the only one
affected by this (which under the hood is `g_file_info_get_content_type`
returning NULL for a file).

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

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)

In lxd deb2snap we have this:

# Check store connectivity
echo "==> Checking connectivity with the snap store"
COUNT=0
SKIP=false
while :; do
if skip_unusable_snapd; then
echo "===> System doesn't have a working snapd and LXD was 
never used, skipping"
SKIP=true
break
fi


similar does not exist in chromium-browser, but must.

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

Title:
  Fresh install of chromium-browser during installer-like process, in a
  chroot fails (when preparing machines prior to first boot)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

  
  ===

  When a user is running the installer, and instructs to install
  chromium-browser with apt in the /target chroot the experience is
  extremely bad.

  There are timeouts, there is critical debconf prompt, and no
  explanation as to what is happening.

  This is not an upgrade, and no conversion from deb2snap is needed.

  It is in a chroot, because this is how installers work.

  It feels like as if on fresh install of chromium-browser it should try
  "snap install --now-or-schedule-for-later chromium-browser" such that
  if snapd is running and available install it now, otherwise record a
  task for snapd to execute if and when it comes up (on first boot). Or
  like for example, it should call snap prepare-image --classic instead.

  Overall, imho on new installations of the package, if there is no
  snapd running, it should be skipped without asking any questions or
  popping up any dialogues.

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

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

[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)

We had a lot of conversations on IRC about this.

tl;dr overall, the UX is bad and confusing and must be improved.

** Description changed:

  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.
+ 
+ 
+ ===
+ 
+ When a user is running the installer, and instructs to install chromium-
+ browser with apt in the /target chroot the experience is extremely bad.
+ 
+ There are timeouts, there is critical debconf prompt, and no explanation
+ as to what is happening.
+ 
+ This is not an upgrade, and no conversion from deb2snap is needed.
+ 
+ It is in a chroot, because this is how installers work.
+ 
+ It feels like as if on fresh install of chromium-browser it should try
+ "snap install --now-or-schedule-for-later chromium-browser" such that if
+ snapd is running and available install it now, otherwise record a task
+ for snapd to execute if and when it comes up (on first boot). Or like
+ for example, it should call snap prepare-image --classic instead.
+ 
+ Overall, imho on new installations of the package, if there is no snapd
+ running, it should be skipped without asking any questions or popping up
+ any dialogues.

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

** Tags added: rls-gg-incoming

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

Title:
  Fresh install of chromium-browser during installer-like process, in a
  chroot fails (when preparing machines prior to first boot)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

  
  ===

  When a user is running the installer, and instructs to install
  chromium-browser with apt in the /target chroot the experience is
  extremely bad.

  There are timeouts, there is critical debconf prompt, and no
  explanation as to what is happening.

  This is not an upgrade, and no conversion from deb2snap is needed.

  It is in a chroot, because this is how installers work.

  It feels like as if on fresh install of chromium-browser it should try
  "snap install --now-or-schedule-for-later chromium-browser" such that
  if snapd is running and available install it now, otherwise record a
  task for snapd to execute if and when it comes up (on first boot). Or
  like for example, it should call snap prepare-image --classic instead.

  Overall, imho on new installations of the package, if there is no
  snapd running, it should be skipped without asking any questions or
  popping up any dialogues.

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

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

[Desktop-packages] [Bug 1882248] [NEW] plug headset won't proper reconfig ouput to it on machine with default output

2020-06-05 Thread Yuan-Chen Cheng

Public bug reported:

target machine does not have built-in speaker, and the monitor does not
have an audio output (like d-sub VGA)

As first boot, there will be a "dummy output" in g-c-c.

After plug-in headset, there will be a headset appear in g-c-c, but it
won't be automatically selected even it's chosen in the pop-up window.

** Affects: oem-priority
 Importance: Critical
 Assignee: Yuan-Chen Cheng (ycheng-twn)
 Status: Confirmed

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


** Tags: bionic oem-priority originate-1881842 somerville

** Information type changed from Proprietary to Public

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

** No longer affects: pulseaudio

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

** Tags added: bionic

** Tags added: originate-1881842

** Tags added: somerville

** Changed in: oem-priority
   Importance: High => Critical

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

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1882248/+subscriptions

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

[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)

** Summary changed:

- install chromium-browser in a chroot fails
+ Fresh install of chromium-browser during installer-like process, in a chroot 
fails (when preparing machines prior to first boot)

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

Title:
  Fresh install of chromium-browser during installer-like process, in a
  chroot fails (when preparing machines prior to first boot)

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

My debconf prompt is different and has options to retry abort skip, or
press ok.


My screen is larger, is there a scrollbar that is not visible? can you scroll 
down to skip and press skip?

Alternatively, can you use debconf pressed to pressed the answer to the
quesiton as Skip:


chromium-browserchromium-browser/snap-no-connectivity   select  Skip

** Attachment added: "debconf-prompt-groovy.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+attachment/5380668/+files/debconf-prompt-groovy.png

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

Ansible use his own module to wrap apt command, and it uses non-
interactive way, not just "-y".

Anyway i confirm that this fails under a chroot :

$ DEBIAN_FRONTEND=noninteractive chroot /target apt-get -y install 
chromium-browser
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  liblzo2-2 snapd squashfs-tools
Suggested packages:
  zenity | kdialog
The following NEW packages will be installed:
  chromium-browser liblzo2-2 snapd squashfs-tools
Preconfiguring packages ...
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/23.4 MB of archives.
After this operation, 105 MB of additional disk space will be used.
Selecting previously unselected package liblzo2-2:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 72913 files and directories currently installed.)
Preparing to unpack .../liblzo2-2_2.10-2_amd64.deb ...
Unpacking liblzo2-2:amd64 (2.10-2) ...
Selecting previously unselected package squashfs-tools.
Preparing to unpack .../squashfs-tools_1%3a4.4-1_amd64.deb ...
Unpacking squashfs-tools (1:4.4-1) ...
Selecting previously unselected package snapd.
Preparing to unpack .../snapd_2.44.3+20.04_amd64.deb ...
Unpacking snapd (2.44.3+20.04) ...
Setting up liblzo2-2:amd64 (2.10-2) ...
Setting up squashfs-tools (1:4.4-1) ...
Setting up snapd (2.44.3+20.04) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.apparmor.service → 
/lib/systemd/system/snapd.apparmor.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.autoimport.service → 
/lib/systemd/system/snapd.autoimport.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.core-fixup.service → 
/lib/systemd/system/snapd.core-fixup.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.recovery-chooser-trigger.service
 → /lib/systemd/system/snapd.recovery-chooser-trigger.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.seeded.service → 
/lib/systemd/system/snapd.seeded.service.
Created symlink 
/etc/systemd/system/cloud-final.service.wants/snapd.seeded.service → 
/lib/systemd/system/snapd.seeded.service.
Created symlink /etc/systemd/system/multi-user.target.wants/snapd.service → 
/lib/systemd/system/snapd.service.
Created symlink /etc/systemd/system/timers.target.wants/snapd.snap-repair.timer 
→ /lib/systemd/system/snapd.snap-repair.timer.
Created symlink /etc/systemd/system/sockets.target.wants/snapd.socket → 
/lib/systemd/system/snapd.socket.
Created symlink 
/etc/systemd/system/final.target.wants/snapd.system-shutdown.service → 
/lib/systemd/system/snapd.system-shutdown.service.
Selecting previously unselected package chromium-browser.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 73011 files and directories currently installed.)
Preparing to unpack 
.../chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
===> Unable to contact the store, trying every minute for the next 30 minutes

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1192599]

2020-06-05 Thread Heiko-tietze-g

*** Bug 122030 has been marked as a duplicate of this bug. ***

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

Title:
  [upstream] writer: zoom fraction changes when clicking on figures

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192599/+attachment/3707409/+files/lorem_ipsum.odt
 && lowriter --nologo lorem_ipsum.odt

  is when one clicks View -> Zoom -> Fit width and height -> OK click
  the text, then click the picture, the zoom does not change.

  4) What happens instead is it does. All other zoom modes don't exhibit
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13
  Uname: Linux 3.5.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu11
  Architecture: amd64
  Date: Wed Jun 19 16:56:17 2013
  InstallationDate: Installed on 2012-11-22 (209 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1082110]

2020-06-05 Thread Greenandpleasant2000-support

I strongly support the OP's request to be able to add endnotes at the
end of the document (without having to create a section first, and
without a page break).

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

Title:
  [Upstream] Endnote placed at end of document is unmovable

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.6.2~rc2-0ubuntu4
Candidate: 1:3.6.2~rc2-0ubuntu4
Version table:
   *** 1:3.6.2~rc2-0ubuntu4 0
  900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.6.2~rc2-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages

  3) What is expected to happen in Calc is open a blank document -> type
  example -> click Insert -> Footnote/Endnote... -> under Numbering
  click radio button Automatic -> under Type click radio button Endnote
  -> click button OK and an Endnote is inserted one line down from
  example, which one may click Enter on the keyboard, moving the Endnote
  one line down, as it does in Microsoft Office Professional Plus 2010
  Word Version 14.0.6023.1000 (32-bit).

  4) What happens instead is the Endnote is placed all the way at the
  bottom of the document, and is not movable via clicking Del on the
  keyboard.

  WORKAROUND: Use AbiWord.

  apt-cache policy abiword
  abiword:
Installed: 2.9.2+svn20120603-8
Candidate: 2.9.2+svn20120603-8
Version table:
   *** 2.9.2+svn20120603-8 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
  100 /var/lib/dpkg/status

  Open a blank document -> type example -> click References -> Insert
  Endnote and an Endnote is inserted one line down from example, which
  one may click Enter on the keyboard, moving the Endnote one line down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Thu Nov 22 09:03:21 2012
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack

2020-06-05 Thread Gianfranco Costamagna

Hello, this broke virtualbox builds.

gcc -c -O2 -g -pipe -Wshadow -Wall -Wextra -Wno-missing-field-initializers 
-Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter 
-Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-variable 
-Wunused-function -Wunused-label -Wunused-parameter -Wmissing-prototypes 
-Wstrict-prototypes -Wmissing-declarations 
-Werror-implicit-function-declaration -Wno-variadic-macros -O2 -mtune=generic 
-fno-omit-frame-pointer -fno-strict-aliasing -fvisibility=hidden 
-DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fPIC 
-Wno-overlength-strings  -include /<>/include/iprt/linux/symvers.h 
-fno-stack-protector -m64 -I/<>/src/VBox/GuestHost/OpenGL/include 
-I/<>/out/obj/VBoxOGLgen -I/<>/out/obj/VBoxEGL/dtrace 
-I/<>/include -I/<>/out -DVBOX -DVBOX_OSE 
-DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX 
-D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER 
-DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" 
-DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" 
-DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" 
-DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE 
-DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 
-DPIC -DVBOX_WITH_HGCM -DLOG_USE_C99 -DRT_WITHOUT_EXEC_ALLOC -DLinux=1 
-D_GNU_SOURCE -Wp,-MD,/<>/out/obj/VBoxEGL/egl.o.dep 
-Wp,-MT,/<>/out/obj/VBoxEGL/egl.o -Wp,-MP -o 
/<>/out/obj/VBoxEGL/egl.o 
/<>/src/VBox/Additions/common/crOpenGL/egl.c
In file included from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0:
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:114:35: error: 
conflicting types for ‘glXQueryGLXPbufferSGIX’
 extern DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)
   ^
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in 
definition of macro ‘VBOXGLXTAG’
  #define VBOXGLXTAG(Func) Func
   ^~~~
In file included from /usr/include/GL/glx.h:328:0,
 from 
/<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99,
 from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:26:
/usr/include/GL/glxext.h:861:6: note: previous declaration of 
‘glXQueryGLXPbufferSGIX’ was here
 void glXQueryGLXPbufferSGIX (Display *dpy, GLXPbufferSGIX pbuf, int attribute, 
unsigned int *value);
  ^~
kmk_builtin_append -n "/<>/out/obj/VBoxOGL/context.o.dep" "" 
"/<>/src/VBox/Additions/common/crOpenGL/context.c:" ""
kBuild: Creating directory /<>/out/obj/pam_vbox/
kmk_builtin_mkdir -p -- /<>/out/obj/pam_vbox/
kBuild: Compiling pam_vbox - 
/<>/src/VBox/Additions/common/pam/pam_vbox.cpp => 
/<>/out/obj/pam_vbox/pam_vbox.o
kmk_builtin_rm -f -- /<>/out/obj/pam_vbox/pam_vbox.o.dep 
/<>/out/obj/pam_vbox/pam_vbox.o  
g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra 
-Wno-missing-field-initializers -Wno-unused -Wno-trigraphs 
-fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op   
-Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function 
-Wunused-label -Wunused-parameter  -Wno-overloaded-virtual -Wno-variadic-macros 
-O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing 
-fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT 
-fvisibility-inlines-hidden   -fno-exceptions -fPIC -fno-exceptions -include 
/<>/include/iprt/linux/symvers.h -fno-stack-protector -m64 
-I/<>/out/obj/pam_vbox/dtrace -I/<>/include 
-I/<>/out -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS 
-DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 
-DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING 
-DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" 
-DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" 
-DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" 
-DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE 
-DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 
-DPIC -DLOG_TO_BACKDOOR -DVBOX_WITH_HGCM -DVBOX_WITH_GUEST_PROPS -DLOG_USE_C99 
-DRT_WITHOUT_EXEC_ALLOC 
-Wp,-MD,/<>/out/obj/pam_vbox/pam_vbox.o.dep 
-Wp,-MT,/<>/out/obj/pam_vbox/pam_vbox.o -Wp,-MP -o 
/<>/out/obj/pam_vbox/pam_vbox.o 
/<>/src/VBox/Additions/common/pam/pam_vbox.cpp
In file included from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0:
/<>/src/VBox/Additions/common/crOpenGL/glx.c:766:28: error: 
conflicting types for ‘glXQueryGLXPbufferSGIX’
 DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)(Display *dpy, GLXPbuffer 
pbuf,
^
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in 
definition of macro ‘VBOXGLXTAG’
  #define VBOXGLXTAG(Func) Func
   ^~~~
In file included from /usr/include/GL/glx.h:328:0,
 from 
/<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99,
 from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:26:
/usr/include/GL/glxext.h:861:6: note: previous declaration of

[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Focal)
   Status: New => In Progress

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

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Description changed:

+ [ Impact ]
+ 
+ OSK doesn't appear in X11 when disabling physical keyboard
+ 
+ [ Test case ]
+ 
+ 1. Log into gnome-shell Xorg session ("Ubuntu")
+ 2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this
+disables the physical keyboard)
+ 3. Use touch screen to touch a (supported) text input field, such as
+gnome-shell > Activities > Search:
+- The OSK appear
+ 4. Swipe from bottom of screen in order to summon OSK on demand:
+- occurred on Ubuntu 18.04 through 19.10)
+ 
+ [ Regression potential ]
+ 
+ The OSK shows when not needed in setup with no touch-screen or with
+ touch screen but when not required.
+ 
+ ---
+ 
  Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
  Related upstream bugs:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
  
  [Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
  /gnome-shell/-/issues/2378. I set one for the other and then Launchpad
  somehow did not let me again]
  
  Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS 
9575 2-in-1:
  1. Log into gnome-shell Xorg session ("Ubuntu")
  2. Fold the display back, to switch to tablet mode. (On properly supported 
devices, this disables the physical keyboard)
  3. Use touch screen to touch a (supported) text input field, such as  
gnome-shell > Activities > Search
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text
  4. Swipe from bottom of screen in order to summon OSK on demand:
  -> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
  -> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text 
fields of foreign toolkits that are expected not to trigger the OSK 
automatically)
  
  Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
  the Xorg session is affected by the issue described in this bug.
  
  Also note that Accessibility was NOT necessary to be enabled in 19.10
  and before. (When enabling it in 20.04, the OSK does appear under Xorg,
  but this should not be necessary)
  
  (On Wayland there is a different changed behavior with the OSK not appearing 
in the device's laptop mode, i.e. with the physical keyboard enabled. This 
seems intended and a different issue as per 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
  
  This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
  I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this 
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
  It probably also worked with 19.04 and possibly 18.10, but I ran mostly 
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
  
  Other hardware reported to reproduce the issue (and in part are said to
  have been working in 19.10 and before, down to 18.04) include:
  
  In bug #1866556;
  Lenovo ThinkPad L390 Yoga
  Asus ZenBook UX370UAF
  Acer Switch 11 V sw5-173 (said to have worked with 18.04)
  (Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the 
tablet mode seems unsupported on these devices and so the issue might be 
different)
  
  In upstream bug:
  Dell Inspiron 15 700 2-in-1
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
+ ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 19:59:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-13 (619 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
- RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
- SourcePackage: gnome-shell
+ RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)

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

Title:
  [Focal regression] On-screen keyboard (OSK) does not appear on

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

2020-06-05 Thread Matt Hurd

Confirmed bug on 20.04 with Nvidia 440 here too on 970M. Noveau works
fine but the tablet is pretty unusable slow, so have to use NV440 with
an uncomfortable resolution on the main screen :-(

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

"-y" is not enough to install non-interactive under ansible.

Either specify debconf non-interactive frontened, or ask ansible to
preseed the debconf answer that you acknowledge the debconf note that
the package will provide.

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

** Description changed:

- https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
+ [ Impact ]
+ 
+ GNOME shell crashes on extensions loading / updates
+ 
+ [ Test case ]
+  - No clear test case, normally may happen during screen locking/unlocking
+  - But crashes should be monitored at
+https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
+ 
+ [ Regression potential ]
+ 
+ Stylesheet memory could be leaked
  
  ---
  
  Started the computer from suspend. Started Gmail from Dash to Panel.
  
- ProblemType: Crash
- DistroRelease: Ubuntu 20.10
+ ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 18:30:48 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu 
(%rdi),%ymm1
   PC (0x7fe9fdcc3e41) ok
   source "(%rdi)" (0xf0250) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading unknown VMA
- Signal: 11
- SourcePackage: gnome-shell
+ Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
   g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Started the computer from suspend. Started Gmail from Dash to Panel.

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 18:30:48 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu 
(%rdi),%ymm1
   PC (0x7fe9fdcc3e41) ok
   source "(%rdi)" (0xf0250) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
   g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1882242] [NEW] June 4th network-manager update kills wireless networking

2020-06-05 Thread Mark Drone

Public bug reported:

network-manager problems

June 4, 2020 apt update installed two networking packages:
network-manager_1.14.6-2+deb10u1_amd64.deb
libnm0_1.14.6-2+deb10u1_amd64.deb

System:
  Kernel: 5.4.0-33-generic x86_64 
  Desktop: MATE 1.24.0 
  Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:
  Type: Laptop System: Dell product: Latitude E6530 v: 01 

After rebooting the laptop, the wireless access point(s) are no longer
available in the Network Manager.  The "Enable Wi-Fi" is checked. "Wi-Fi
Networks" is grayed out.

Network:
  Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl 
  IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b

$ sudo ip addr

wlp2s0:  mtu 1500 qdisc fq_codel 
state DORMANT group default qlen 1000
link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff

$ sudo nmcli
wlp2s0: disconnected
"Broadcom and subsidiaries BCM43228"
wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500

$ sudo nmcli device show
GENERAL.DEVICE: wlp2s0
GENERAL.TYPE:   wifi
GENERAL.HWADDR: 3C:77:E6:7C:5D:7B
GENERAL.MTU:1500
GENERAL.STATE:  30 (disconnected)
GENERAL.CONNECTION: --
GENERAL.CON-PATH:   --

$ sudo nmcli radio wifi
enabled

$ sudo iwlist wlp2s0 scanning
wlp2s0No scan results

$ sudo iwlist wlp2s0 accesspoints
wlp2s0Interface doesn't have a list of Peers/Access-Points

$ sudo iwlist wlp2s0 ap
wlp2s0Interface doesn't have a list of Peers/Access-Points

$ sudo iwlist wlp2s0 wpakeys
wlp2s02 key sizes : 40, 104bits
  4 keys available :
Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported

$ sudo iwconfig wlp2s0
wlp2s0IEEE 802.11  ESSID:off/any  
  Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:on

$ sudo rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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

Title:
  June 4th network-manager update kills wireless networking

Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager problems

  June 4, 2020 apt update installed two networking packages:
  network-manager_1.14.6-2+deb10u1_amd64.deb
  libnm0_1.14.6-2+deb10u1_amd64.deb

  System:
Kernel: 5.4.0-33-generic x86_64 
Desktop: MATE 1.24.0 
Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:
Type: Laptop System: Dell product: Latitude E6530 v: 01 

  After rebooting the laptop, the wireless access point(s) are no longer
  available in the Network Manager.  The "Enable Wi-Fi" is checked. "Wi-
  Fi Networks" is grayed out.

  Network:
Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl 
IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b

  $ sudo ip addr

  wlp2s0:  mtu 1500 qdisc fq_codel 
state DORMANT group default qlen 1000
  link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff

  $ sudo nmcli
  wlp2s0: disconnected
  "Broadcom and subsidiaries BCM43228"
  wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500

  $ sudo nmcli device show
  GENERAL.DEVICE: wlp2s0
  GENERAL.TYPE:   wifi
  GENERAL.HWADDR: 3C:77:E6:7C:5D:7B
  GENERAL.MTU:1500
  GENERAL.STATE:  30 (disconnected)
  GENERAL.CONNECTION: --
  GENERAL.CON-PATH:   --

  $ sudo nmcli radio wifi
  enabled

  $ sudo iwlist wlp2s0 scanning
  wlp2s0No scan results

  $ sudo iwlist wlp2s0 accesspoints
  wlp2s0Interface doesn't have a list of Peers/Access-Points

  $ sudo iwlist wlp2s0 ap
  wlp2s0Interface doesn't have a list of Peers/Access-Points

  $ sudo iwlist wlp2s0 wpakeys
  wlp2s02 key sizes : 40, 104bits
4 keys available :
  Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported

  $ sudo iwconfig wlp2s0
  wlp2s0IEEE 802.11  ESSID:off/any  
Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Encryption key:off
Power Management:on

  $ sudo rfkill list
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  2: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage

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

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  App icon aspect ratio in the panel is broken

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

Bug description:
  [ Impact ]

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

  See attached screenshot.

  [ Test case ]

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

  [ Regression potential ]

  Icons may have wrong vertical aligment

  -

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

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

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

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

[Desktop-packages] [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Started the computer from suspend. Started Gmail from Dash to Panel.

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 18:30:48 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu 
(%rdi),%ymm1
   PC (0x7fe9fdcc3e41) ok
   source "(%rdi)" (0xf0250) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading unknown VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   __strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
   g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen]

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions

** Changed in: gnome-shell (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Do Not Disturb setting does not persist across login sessions

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

Bug description:
  [ Impact ]

  Selecting do not disturb from settings does not persist across login
  sessions.

  [ Test case ]

  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar

  [ Regresion potential ]

  Togglingg the do not disturb toggle doesn't work anymore

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  gnome-control-center:
    Installed: 1:3.36.1-1ubuntu5
    Candidate: 1:3.36.1-1ubuntu5
    Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  - Do Not Disturb is reset to disabled on each new login

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

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

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

[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions

** Description changed:

- Description:  Ubuntu 20.04 LTS
- Release:  20.04
- gnome-control-center:
-   Installed: 1:3.36.1-1ubuntu5
-   Candidate: 1:3.36.1-1ubuntu5
-   Version table:
-  *** 1:3.36.1-1ubuntu5 500
- 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+ [ Impact ]
  
  Selecting do not disturb from settings does not persist across login
  sessions.
  
- What I did
+ [ Test case ]
+ 
  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar
  
- What happens:
+ [ Regresion potential ]
+ 
+ Togglingg the do not disturb toggle doesn't work anymore
+ 
+ 
+ Description:  Ubuntu 20.04 LTS
+ Release:  20.04
+ gnome-control-center:
+   Installed: 1:3.36.1-1ubuntu5
+   Candidate: 1:3.36.1-1ubuntu5
+   Version table:
+  *** 1:3.36.1-1ubuntu5 500
+ 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ 
+ 
  - Do Not Disturb is reset to disabled on each new login
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
+ ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  LANGUAGE=en_CA:en
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
- SourcePackage: gnome-control-center
+  LANGUAGE=en_CA:en
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bashSourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Changed in: gnome-shell (Ubuntu Focal)
   Importance: Critical => 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/1873692

Title:
  Do Not Disturb setting does not persist across login sessions

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

Bug description:
  [ Impact ]

  Selecting do not disturb from settings does not persist across login
  sessions.

  [ Test case ]

  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar

  [ Regresion potential ]

  Togglingg the do not disturb toggle doesn't work anymore

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  gnome-control-center:
    Installed: 1:3.36.1-1ubuntu5
    Candidate: 1:3.36.1-1ubuntu5
    Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  - Do Not Disturb is reset to disabled on each new login

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

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

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

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

** Description changed:

+ [ Impact ]
+ 
  The aspect ratio of the icon on the top left of the screen (Activites
  bar?) is broken so it looks taller and thinner than normal.
  
  See attached screenshot.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
+ [ Test case ]
+ 
+ - Run an application such as update-manager
+ - The application icon on the top panel should have correct propotions
+ 
+ [ Regression potential ]
+ 
+ Icons may have wrong vertical aligment
+ 
+ -
+ 
+ ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:10:09 2020
  InstallationDate: Installed on 2020-01-24 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
- SourcePackage: ubuntu-release-upgrader
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
-  Log time: 2020-04-10 09:03:51.154471
-  Starting pkgProblemResolver with broken count: 0
-  Starting 2 pkgProblemResolver with broken count: 0
-  Done
+  Log time: 2020-04-10 09:03:51.154471
+  Starting pkgProblemResolver with broken count: 0
+  Starting 2 pkgProblemResolver with broken count: 0
+  Done
  VarLogDistupgradeTermlog:
-  
- mtime.conffile..etc.update-manager.release-upgrades: 
2020-04-03T20:22:43.358127
+ 
+ mtime.conffile..etc.update-manager.release-upgrades:
+ 2020-04-03T20:22:43.358127

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

Title:
  App icon aspect ratio in the panel is broken

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

Bug description:
  [ Impact ]

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

  See attached screenshot.

  [ Test case ]

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

  [ Regression potential ]

  Icons may have wrong vertical aligment

  -

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

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

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

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

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

The upstream submitted merge request seems to still been under
discussion, I don't think it's appropriate to merge that in the
packaging Vcs yet

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

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

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in pulseaudio source package in Focal:
  Incomplete
Status in pulseaudio source package in Groovy:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

** Description changed:

- https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda
+ [ Impact ]
+ 
+ GNOME shell crashes on extensions loading / updates
+ 
+ [ Test case ]
+  - No clear test case, normally may happen during screen locking/unlocking
+  - But crashes should be monitored at
+https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda
+ 
+ [ Regression potential ]
+ 
+ Stylesheet memory could be leaked
  
  ---
  
  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times
  
- ProblemType: Crash
- DistroRelease: Ubuntu 20.10
+ ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
- Signal: 11
- SourcePackage: gnome-shell
+ Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen]

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

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

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

Thank you for taking the time to report this bug and help 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: pulseaudio (Ubuntu Focal)
   Status: New => Incomplete

** Changed in: pulseaudio (Ubuntu Groovy)
   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/1882161

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

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in pulseaudio source package in Focal:
  Incomplete
Status in pulseaudio source package in Groovy:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

To reproduce

apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"

You can try it in a container. That's not exactly a chroot but...

docker run --rm -it ubuntu:latest /bin/bash
apt update && apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1882231] Re: Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish Bin ..."

2020-06-05 Thread Paul White

Thanks for your reply amejbil. The bug report that you referred to might
be specific to the Xfce desktop although what you're seeing appears to
be the same.

Now that you've provided a screenshot of the problem I can confirm that
I'm seeing the same as you are. I'm moving the bug report to the gnome-
shell-extension-desktop-icons package for an Ubuntu developer to review
the issue further.


** Package changed: ubuntu => gnome-shell-extension-desktop-icons (Ubuntu)

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

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

Title:
   Tooltip for Rubbish Bin displays "Wastebasket ..." instead of
  "Rubbish Bin ..."

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

Bug description:
   Tooltip for Rubbish Bin displays "Wastebasket ..." instead of
  "Rubbish Bin ..."

  This bug is in the Ubuntu desktop 20.04 LTS. Same issue reported
  before in 2016 release as above

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

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

[Desktop-packages] [Bug 1882231] [NEW] Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish Bin ..."

You have been subscribed to a public bug:

 Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish
Bin ..."

This bug is in the Ubuntu desktop 20.04 LTS. Same issue reported before
in 2016 release as above

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


** Tags: focal
-- 
 Tooltip for Rubbish Bin displays "Wastebasket ..." instead of "Rubbish Bin 
..." 
https://bugs.launchpad.net/bugs/1882231
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu.

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

I did install with "apt install chromium-browser -y" for the demonstration.
In my specific case, i use ansible so it is non interactive.

That task fails.

- name: install browsers
  apt:
state: latest
name:
  - firefox
  - firefox-locale-fr
  - chromium-browser
  - chromium-browser-l10n
  - adobe-flashplugin

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1882232] Re: install chromium-browser in a chroot fails

That's a debconf note. How did you invoke installation?

All package installation is interactive. If you want non-interactive
package installation one has to pass options to apt to "do not disturb
me" and accept defaults to any questions around installation or
upgrades.

DEBIAN_FRONTEND=noninteractive chroot $MY_CHROOT apt-get -y install
$packages

is the better way to install packages non-interactively. Does doing
something like that sufficient to complete chromium-browser package
installation?

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-06-05 Thread jman6495

Sadly, adding Option "EnablePageFlip" "off" doesn't appear to resolve
the issue on the 3500U, however i've made quite a few modifications on
this install.

I'll give it a go on a fresh install this evening and get back to you.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

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

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP:

[Desktop-packages] [Bug 1870847] Re: App grid has too many page dots on right

It's not clear what version of the dock are you using with gnome 3.36.2

However, Lukasz, as per the fact the reporter marked this as fixed
initially with the SRU'ed version, I don't see a reason to stop the
update, given that it also includes other fixes.

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

Title:
  App grid has too many page dots on right

Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2020-06-05 Thread agm97

Are you planing to patch ubuntu packages or waiting to be in upstream? 
I'm asking because in pulseaudio side I am watching no much interest at all in 
that changes.. and in the kernel's side the same, so I doubt if that will gonna 
be fixed or not, at least, in upstream.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-05 Thread dusk

profile hsp/hfp show - unavailable
microphone not working
play music well on - A2DP

Kubuntu 20.04 - Linux 5.4.0-33-generic
pulseaudio 1:13.99.1-1ubuntu3.2 amd64
bluez  5.53-0ubuntu3 amd64

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-06-05 Thread Till Kamppeter

** Changed in: cups (Ubuntu)
   Status: Expired => Triaged

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1882237] [NEW] Libre Office doesn't start at all (wrong library version)

2020-06-05 Thread Leo Cacciari

Public bug reported:

I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

hobbit:~ $ lowriter
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: 
libicui18n.so.63: cannot open shared object file: No such file or directory

Now, the libicu is (obviously) installed, but the installed version is
66, not 63. Version 66, BTW, is the one listed as dependency for the
libre office package.

I do not exactly know when libreoffice stopped working after the update
to focal, as I do not use it extensively

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Jun  5 12:49:19 2020
InstallationDate: Installed on 2019-02-09 (481 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "output of ldd /usr/lib/libreoffice/program/soffice.bin"
   
https://bugs.launchpad.net/bugs/1882237/+attachment/5380662/+files/soffice.ldd

** Description changed:

- I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a 
- file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message: 
+ I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
+ file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:
  
- hobbit:~ $ lowriter 
+ hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory
  
  Now, the libicu is (obviously) installed, but the installed version is
- 66, not 63.
+ 66, not 63. Version 66, BTW, is the one listed as dependency for the
+ libre office package.
  
  I do not exactly know when libreoffice stopped working after the update
  to focal, as I do not use it extensively
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu

[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

2020-06-05 Thread Till Kamppeter

** Summary changed:

- Since I upddated to Ubuntu 20.04 my HP printer doesn't print
+ Since I updated to Ubuntu 20.04 my HP printer doesn't print

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  New
Status in pillow-python2 package in Ubuntu:
  New
Status in python-reportlab package in Ubuntu:
  New

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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

[Desktop-packages] [Bug 1882232] [NEW] install chromium-browser in a chroot fails

Public bug reported:

Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

** Attachment added: "2020-06-05T12:44:39,434525754+02:00.png"
   
https://bugs.launchpad.net/bugs/1882232/+attachment/5380661/+files/2020-06-05T12%3A44%3A39%2C434525754+02%3A00.png

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

Title:
  install chromium-browser in a chroot fails

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since snapd integration, chromium-browser package fails to install in a post 
kickstart chroot.
  As APT obfuscate snap installation, I worry about auto installation off any 
other snap package.

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

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

[Desktop-packages] [Bug 1882047] Re: Screen locking issue

2020-06-05 Thread Tarmo

** Information type changed from Private Security to Public

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

Title:
  Screen locking issue

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  Screen locking restarts gnome shell. Result is the same whether clicking 
screen lock icon on top left menu, using Super + L or just screen lock timeout.
  I have same problem on my desktop and laptop. Screen isnt locked when waking 
from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 11:19:08 2020
  InstallationDate: Installed on 2019-05-07 (393 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=et_EE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-04-25 (39 days ago)

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

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

[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics

I don't wan't to advertise but just to give an impression what virtual hardware
we are talking about:
https://contabo.com/?show=vps

Both VPS are the SSD models. The interesting thing is that the problems
started with Ubuntu 20.04. - I already used gnome on Ubuntu 18.04. Now I
installed ubuntu-desktop and as far as I can remember I used gnome-
desktop with 18.04. - basically both should use the same base if I'm not
wrong.

So the problem is not that big because XRDP is working and also X2GO.
The VNC direct connection to GUI is my last option if everything else is
not working.

After Upgrade I also hat some problems with missing mouuse and keyboard
in GUI. I used apt install xserver-xorg-input-evdev which solved this
problem.

Due to the several graphic modes which are tested at boot I thought
maybe that this testing takes to long or something like this. But up to
know I found no way to skip this resolution / graphic modes testing. If
I use startx this process is much shorter.

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

Title:
[bochs_drm] Booting gets stuck with corrupt graphics

Status in mutter package in Ubuntu:
Incomplete

Bug description:
When booting on a VPS connected via VNC at first the text messages via
boot are displayed. Then the resolution changes several times (VNC
size changes) and after a lot of resolution changes it gets stuck in a
corrupd graphic design. The cursor is still blinking but alt+Fx does
also not work.

Using sudo service gdm3 stop and sudo startx is working. Due to the
fact that the VNC console is completely frozen and this is hosted at a
provider I have to use a separate putty session to stop gdm and
starting a new gui session which is then displayed in the VNC.

This problem does not exist with Ubuntu 18.04 LTS. It does not matter
if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to
20.04 LTS. On a second VPS the problem is similar but not the same.
The second one does not get totally frozen. There is still no GUI when
booting but it ends up in a purple uniform screen even the text mode
is purple (the first VPS ends up a blueish screen with blue vertical
lines).

On the second VPS it is possible to switch to shell (purple style) and
executing the abovementioned commands directly without a second putty
session. But the behavior is basically similar for both VPS.

When using sudo reboot the second VPS displays text again and the
first only some graphic trash. So basically they have both the same
behavior but on the first the graphics are totally destroyed even text
is not working anymore. The Funny thing is that startx is still
working but after clothng the startx session the graphic trash is
shown again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun 5 10:39:59 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem
anderen Prozess verwendet?)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Device [1234:] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Device [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version:

[Desktop-packages] [Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

* Disabling fractional scaling in Settings.
- Did not solve the issue

* Using a scaling factor of 100%, briefly.
- Did not solve the issue and makes the built-in monitor unusable as text size 
is too small

* Selecting 'Ubuntu on Wayland' from the login screen.
- Solves the flickering but makes text on built-in monitor too small
- If I change scaling for the built-in monitor some inconsistencies are 
produced:
- Application scaling is ok
- Icons on the desktop don't change scaling

All the testing has been done by logging out and back in after every
change

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

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference

  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON

  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON

  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
  Expected behavior: Pointer doesn't blink
  Current behavior: Pointer blinks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics

Thanks.

I think I have tried both before but just to be sure I changed both
settings and rebooted. Now the screen is not bluish with blue lines
anymore it is black and I can switch to shell. So that's more or less
like on VPS2 but without purple look.

After that I returned to  #WaylandEnable=false and the result after
reboot is also the black screen. Seems to remove nomodeset is making the
minimal difference.

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

Title:
  [bochs_drm] Booting gets stuck with corrupt graphics

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When booting on a VPS connected via VNC at first the text messages via
  boot are displayed. Then the resolution changes several times (VNC
  size changes) and after a lot of resolution changes it gets stuck in a
  corrupd graphic design. The cursor is still blinking but alt+Fx does
  also not work.

  Using sudo service gdm3 stop and sudo startx is working. Due to the
  fact that the VNC console is completely frozen and this is hosted at a
  provider I have to use a separate putty session to stop gdm and
  starting a new gui session which is then displayed in the VNC.

  This problem does not exist with Ubuntu 18.04 LTS. It does not matter
  if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to
  20.04 LTS. On a second VPS the problem is similar but not the same.
  The second one does not get totally frozen. There is still no GUI when
  booting but it ends up in a purple uniform screen even the text mode
  is purple (the first VPS ends up a blueish screen with blue vertical
  lines).

  On the second VPS it is possible to switch to shell (purple style) and
  executing the abovementioned commands directly without a second putty
  session. But the behavior is basically similar for both VPS.

  When using sudo reboot the second VPS displays text again and the
  first only some graphic trash. So basically they have both the same
  behavior but on the first the graphics are totally destroyed even text
  is not working anymore. The Funny thing is that startx is still
  working but after clothng the startx session the graphic trash is
  shown again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun  5 10:39:59 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Device [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau

[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics

It seems like the (Wayland-based) login screen is failing to start. One
reason is the unusual (virtual?) hardware, but the bigger reason is
probably just that the 'nomodeset' kernel parameter explicitly prevents
Wayland from working.

A secondary problem is that gdm3 should detect the failure and revert to
a Xorg-based login screen. That's also not working, but one problem at a
time...

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

Title:
  [bochs_drm] Booting gets stuck with corrupt graphics

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When booting on a VPS connected via VNC at first the text messages via
  boot are displayed. Then the resolution changes several times (VNC
  size changes) and after a lot of resolution changes it gets stuck in a
  corrupd graphic design. The cursor is still blinking but alt+Fx does
  also not work.

  Using sudo service gdm3 stop and sudo startx is working. Due to the
  fact that the VNC console is completely frozen and this is hosted at a
  provider I have to use a separate putty session to stop gdm and
  starting a new gui session which is then displayed in the VNC.

  This problem does not exist with Ubuntu 18.04 LTS. It does not matter
  if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to
  20.04 LTS. On a second VPS the problem is similar but not the same.
  The second one does not get totally frozen. There is still no GUI when
  booting but it ends up in a purple uniform screen even the text mode
  is purple (the first VPS ends up a blueish screen with blue vertical
  lines).

  On the second VPS it is possible to switch to shell (purple style) and
  executing the abovementioned commands directly without a second putty
  session. But the behavior is basically similar for both VPS.

  When using sudo reboot the second VPS displays text again and the
  first only some graphic trash. So basically they have both the same
  behavior but on the first the graphics are totally destroyed even text
  is not working anymore. The Funny thing is that startx is still
  working but after clothng the startx session the graphic trash is
  shown again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun  5 10:39:59 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Device [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage

[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics

Oops. Before you edit that file please try just removing the kernel
parameter 'nomodeset'.

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

Title:
  [bochs_drm] Booting gets stuck with corrupt graphics

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When booting on a VPS connected via VNC at first the text messages via
  boot are displayed. Then the resolution changes several times (VNC
  size changes) and after a lot of resolution changes it gets stuck in a
  corrupd graphic design. The cursor is still blinking but alt+Fx does
  also not work.

  Using sudo service gdm3 stop and sudo startx is working. Due to the
  fact that the VNC console is completely frozen and this is hosted at a
  provider I have to use a separate putty session to stop gdm and
  starting a new gui session which is then displayed in the VNC.

  This problem does not exist with Ubuntu 18.04 LTS. It does not matter
  if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to
  20.04 LTS. On a second VPS the problem is similar but not the same.
  The second one does not get totally frozen. There is still no GUI when
  booting but it ends up in a purple uniform screen even the text mode
  is purple (the first VPS ends up a blueish screen with blue vertical
  lines).

  On the second VPS it is possible to switch to shell (purple style) and
  executing the abovementioned commands directly without a second putty
  session. But the behavior is basically similar for both VPS.

  When using sudo reboot the second VPS displays text again and the
  first only some graphic trash. So basically they have both the same
  behavior but on the first the graphics are totally destroyed even text
  is not working anymore. The Funny thing is that startx is still
  working but after clothng the startx session the graphic trash is
  shown again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun  5 10:39:59 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Device [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882216] Re: [bochs_drm/VESA] Xorg freeze

Please try editing /etc/gdm3/custom.conf and uncomment:

  #WaylandEnable=false

so it is:

  WaylandEnable=false

Then reboot.

** Summary changed:

- Xorg freeze
+ [bochs_drm/VESA] Xorg freeze

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

** Summary changed:

- [bochs_drm/VESA] Xorg freeze
+ [bochs_drm] Booting gets stuck with corrupt graphics

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

** Changed in: mutter (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/1882216

Title:
  [bochs_drm] Booting gets stuck with corrupt graphics

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When booting on a VPS connected via VNC at first the text messages via
  boot are displayed. Then the resolution changes several times (VNC
  size changes) and after a lot of resolution changes it gets stuck in a
  corrupd graphic design. The cursor is still blinking but alt+Fx does
  also not work.

  Using sudo service gdm3 stop and sudo startx is working. Due to the
  fact that the VNC console is completely frozen and this is hosted at a
  provider I have to use a separate putty session to stop gdm and
  starting a new gui session which is then displayed in the VNC.

  This problem does not exist with Ubuntu 18.04 LTS. It does not matter
  if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to
  20.04 LTS. On a second VPS the problem is similar but not the same.
  The second one does not get totally frozen. There is still no GUI when
  booting but it ends up in a purple uniform screen even the text mode
  is purple (the first VPS ends up a blueish screen with blue vertical
  lines).

  On the second VPS it is possible to switch to shell (purple style) and
  executing the abovementioned commands directly without a second putty
  session. But the behavior is basically similar for both VPS.

  When using sudo reboot the second VPS displays text again and the
  first only some graphic trash. So basically they have both the same
  behavior but on the first the graphics are totally destroyed even text
  is not working anymore. The Funny thing is that startx is still
  working but after clothng the startx session the graphic trash is
  shown again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun  5 10:39:59 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Device [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1

[Desktop-packages] [Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

It appears you're using Intel graphics with the modesetting driver, so
you should always have a hardware cursor.

It also appears you're using 200% scaling on one monitor. Could you
please try:

 * Disabling fractional scaling in Settings.

 * Using a scaling factor of 100%, briefly.

 * Selecting 'Ubuntu on Wayland' from the login screen.

** Tags added: cursor xrandr-scaling

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

** Changed in: mutter (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/1882212

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference

  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON

  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON

  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
  Expected behavior: Pointer doesn't blink
  Current behavior: Pointer blinks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

2020-06-05 Thread Timo Suoranta

I am affected as well:

$ uname -a
Linux tsuoranta-lnx 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 
1060 6GB] [10de:1c03] (rev a1)

$ lsb_release -d
Description:Ubuntu 20.04 LTS

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

Title:
  On-screen text disappears after suspend

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  WORKAROUND / 'FIX' (added on March 9, 2017)
  Several people have mentioned upgrading to kernel 4.8 or higher solves the 
issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 
16.04, that is) by running

  sudo apt install linux-generic-hwe-16.04

  If you are still experiencing this issue after upgrading to kernel
  4.8, please share your system details in the comments.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx

[Desktop-packages] [Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

** Summary changed:

- Cursor blinks on screen refresh (only on built in monitor)
+ Cursor blinks/flickers on screen refresh (only on built in monitor)

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

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference

  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON

  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON

  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
  Expected behavior: Pointer doesn't blink
  Current behavior: Pointer blinks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1881175] Re: nautilus doesnt start

2020-06-05 Thread Michael Arnold

I can't start nautilus at all.
It came on slowly I keep clicking in ubuntu to "Yes" submit the bug report.
Rebooted many times however now few days later I can't even open the files 
browser.
*I've even reformatted and installed on a 2nd mostly brand new pc too and the 
same issue started coming up.

Tried
xdg-open .
and
nautilus .


ANYWAYS I will generate a stacktrace
(outlined here https://wiki.ubuntu.com/Backtrace)
from my current installation then re-install and wait for it to happen again 
without any packages installed maybe besides nautilus-admin which it's just 
unusable without IMO.

Would you still need a "journalctl -b 0" or would the above cover more
then everything?

Again note that for me rebooting did nothing.

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

Title:
  nautilus doesnt start

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  for an unknown cause nautilus does not want to start, after a reboot
  it works

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 20:01:29 2020
  InstallationDate: Installed on 2020-01-14 (135 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-05-12 (16 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

Ah, that makes much sense. If you are having problems you could help
yourself. ;)

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  All files in home folder are owned by the user. startx is only working
  with root rights.

  xinit: connection to X server lost/usr/bin/gnome-session: 29: exec:
  /usr/libexec/gnome-session-binary: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jun  4 16:25:19 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset 
rootflags=subvol=ROOT
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882212] Re: Cursor blinks on screen refresh (only on built in monitor)

** Summary changed:

- Arrow blinks on screen refresh (only on built in monitor)
+ Cursor blinks on screen refresh (only on built in monitor)

** Description changed:

  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
- When I use the mouse on the external screen the arrow indicator has no 
problem but when I go on the built-in monitor the arrow indicator will blink 
(disappear and reappear) every time there is some kind of refresh on either 
screen (e.g. I type something or something is displaying text in the terminal).
+ When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).
  
  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference
  
  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON
  
  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON
  
  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
- Expected behavior: Arrow doesn't blink
- Current behavior: Arrow blinks
+ Expected behavior: Pointer doesn't blink
+ Current behavior: Pointer blinks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
-  nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
+  nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
+  nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
-Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
-Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
+  Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
+    Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
+    Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  Cursor blinks on screen refresh (only on built in monitor)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the

[Desktop-packages] [Bug 1882216] [NEW] Xorg freeze

Public bug reported:

When booting on a VPS connected via VNC at first the text messages via
boot are displayed. Then the resolution changes several times (VNC size
changes) and after a lot of resolution changes it gets stuck in a
corrupd graphic design. The cursor is still blinking but alt+Fx does
also not work.

Using sudo service gdm3 stop and sudo startx is working. Due to the fact
that the VNC console is completely frozen and this is hosted at a
provider I have to use a separate putty session to stop gdm and starting
a new gui session which is then displayed in the VNC.

This problem does not exist with Ubuntu 18.04 LTS. It does not matter if
I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04
LTS. On a second VPS the problem is similar but not the same. The second
one does not get totally frozen. There is still no GUI when booting but
it ends up in a purple uniform screen even the text mode is purple (the
first VPS ends up a blueish screen with blue vertical lines).

On the second VPS it is possible to switch to shell (purple style) and
executing the abovementioned commands directly without a second putty
session. But the behavior is basically similar for both VPS.

When using sudo reboot the second VPS displays text again and the first
only some graphic trash. So basically they have both the same behavior
but on the first the graphics are totally destroyed even text is not
working anymore. The Funny thing is that startx is still working but
after clothng the startx session the graphic trash is shown again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun  5 10:39:59 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
 rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Device [1234:] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Device [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.1
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages 
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/1882216

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When booting on a VPS connected via VNC at first the text messages via
  boot are displayed. Then the resolution changes several times (VNC
  size changes) and after a lot of resolution changes it gets stuck in a
  corrupd graphic design. The cursor is still blinking but alt+Fx does
  also not work.

  Using sudo service gdm3 stop and sudo startx is working. Due to the
  fact that the VNC console is completely frozen and

[Desktop-packages] [Bug 1882212] [NEW] Cursor blinks on screen refresh (only on built in monitor)

Public bug reported:

I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
When I use the mouse on the external screen the arrow indicator has no problem 
but when I go on the built-in monitor the arrow indicator will blink (disappear 
and reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

My current display settings are:
Display Mode: Join Displays
Primary Display: either doesn't make any difference

Built in display:
- Orientation: Landscape
- Resolution: 3840x2160
- Refresh Rate: 60,00Hz
- Scale: 200%
- Fractional Scaling: ON

External Display:
- Orientation: Landscape
- Resolution: 1920x1080
- Refresh Rate: 60,00Hz
- Scale: 100%
- Fractional Scaling: ON

Ubuntu release: 20.04 LTS
Xorg version: 1:7.7+19ubuntu14
Expected behavior: Arrow doesn't blink
Current behavior: Arrow blinks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  5 10:27:31 2020
DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2019-07-04 (336 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
dmi.bios.date: 04/17/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N501VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1882212

Title:
  Cursor blinks on screen refresh (only on built in monitor)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
  When I use the mouse on the external screen the arrow indicator has no 
problem but when I go on the built-in monitor the arrow indicator will blink 
(disappear and reappear) every time there is some kind of refresh on either 
screen (e.g. I type something or something is displaying text in the terminal).

  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference

  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON

  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON

  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
  Expected behavior: Arrow doesn't blink
  Current behavior: Arrow blinks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14

[Desktop-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

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

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in linux package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

I am using multi-user.target because I am compiling gnome-shell from
scratch, for development. So also run it manually.

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  All files in home folder are owned by the user. startx is only working
  with root rights.

  xinit: connection to X server lost/usr/bin/gnome-session: 29: exec:
  /usr/libexec/gnome-session-binary: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Jun  4 16:25:19 2020
  DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
   rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset 
rootflags=subvol=ROOT
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights