date:20210303

Thanks for the bug report. Can you explain what you mean, maybe with a
screenshot or photo?

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

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

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

Title:
  Cannot render files

Status in Ubuntu:
  Incomplete

Bug description:
  Cannot render files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  4 11:48:53 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Core Processor Integrated Graphics Controller 
[8086:0036]
  InstallationDate: Installed on 2021-03-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=UUID=56c99f13-306c-47ad-8775-8757bfcdf115 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0037.2010.0614.1712
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55TC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70932-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0037.2010.0614.1712:bd06/14/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104+git2103030500.7d6a17~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2103031800.69f3d3~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1917710/+subscriptions

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

[Desktop-packages] [Bug 1917713] [NEW] [snap] Logged out of Chromium after latest update to 89

2021-03-03 Thread Efthimios Chaskaris

Public bug reported:

It seems I haven't lost anything, but on the top right corner it shows a
person, as well as that I'm not logged in. What is happening? I'm
worried I may lose something if I mess with it.

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

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

Title:
  [snap] Logged out of Chromium after latest update to 89

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  It seems I haven't lost anything, but on the top right corner it shows
  a person, as well as that I'm not logged in. What is happening? I'm
  worried I may lose something if I mess with it.

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

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

[Desktop-packages] [Bug 1917710] [NEW] Cannot render files

2021-03-03 Thread Utkarsh Moholkar

Public bug reported:

Cannot render files

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  4 11:48:53 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Core Processor Integrated Graphics Controller 
[8086:0036]
InstallationDate: Installed on 2021-03-04 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=UUID=56c99f13-306c-47ad-8775-8757bfcdf115 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TCIBX10H.86A.0037.2010.0614.1712
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH55TC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70932-302
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0037.2010.0614.1712:bd06/14/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104+git2103030500.7d6a17~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2103031800.69f3d3~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 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/1917710

Title:
  Cannot render files

Status in xorg package in Ubuntu:
  New

Bug description:
  Cannot render files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  4 11:48:53 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Core Processor Integrated Graphics Controller 
[8086:0036]
  InstallationDate: Installed on 2021-03-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=UUID=56c99f13-306c-47ad-8775-8757bfcdf115 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0037.2010.0614.1712
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55TC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70932-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0037.2010.0614.1712:bd06/14/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104+git2103030500.7d6a17~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2103031800.69f3d3~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1917710/+subscriptions

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

[Desktop-packages] [Bug 1917705] Re: profile will be deleted

2021-03-03 Thread Christian Hujer

BTW even if this is deprecation and removal, this is severely broken: It
deletes a user's profile data without asking the user for consent to the
deletion of the same. A hypothetical argument that stuff can be restored
because the account is synchronized is invalid: recent local profile
data that was not synchronized yet, for example from being offline, is
also deleted in the process, without the user's consent. In some
countries, this is actually rated a criminal offence by cybercrime laws.

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

Title:
  profile will be deleted

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

[Desktop-packages] [Bug 1917705] Re: profile will be deleted

2021-03-03 Thread Christian Hujer

@guiverc It may indeed be deprecations and removals, which sucks. I just
think that 88 isn't the first version with the problem, it's 89.

* snap 1497 is chromium 88 and works fine.
* snap 1506 is chromium 89 has the issue.
* chrome 89 on Linux works fine.

I've just downloaded and installed Chromium build 659458 for Windows 10.
That is Chromium 91. And it has the same issue.

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

Title:
  profile will be deleted

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: High => Medium

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Medium => Undecided

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Importance: High => Medium

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Status: Incomplete => Confirmed

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
   Status: Invalid

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders (when ubuntu-dock is loaded)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Hirsute:
  Invalid

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

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1917705] Re: profile will be deleted

2021-03-03 Thread Chris Guiver

I fear this is the consequence of an announced google chrome/chromium
change, and will not be changed (in fact the API is being removed in the
not too distant future and this is just the start of the the changes
announced with
https://developers.google.com/web/updates/2020/12/chrome-88-deps-rems)

Note - this is opinion only.

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

Title:
  profile will be deleted

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

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

Lorenzo (comment #153), that is bug 1910235 you are experiencing, not
this one. Please help to verify the fix in bug 1910235.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

There are enough comments above suggesting the bug also occurs in Xorg
sessions. Wayland does not seem to be the cause.

That said, this bug is now 8 years old so it's reasonably likely that it
has had multiple different causes (really multiple different bugs) over
the years.

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1917705] [NEW] profile will be deleted

2021-03-03 Thread Christian Hujer

Public bug reported:

After updating the chromium-browser snap from 1497 to 1506, Chromium
refuses to work with profiles that are linked to Google accounts. Each
of them is deleted whenever first opening it. And turning on profile
synchronization does not work.

See the attached file for a screenshot of the issue.

Workaround:
1. Kill the current chromium process.
2. Revert the snap back to an older version.
Warning 1: Running on an older version of Chromium comes at its own issues.
Warning 2: Any already deleted profile will not be restored by going back to an 
older version of Chromium. You will have to create and link the profile again.

This bug is severe and means that Chromium has become unusable in a
professional environment.

"We also need:"

1) The release of Ubuntu you are using
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

2) The version of the package you are using
$ snap list chromium
Name  VersionRev   Tracking   Publisher   Notes
chromium  89.0.4389.72   1506  latest/stable  canonical*  -

3) What you expected to happen
Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

4) What happened instead
Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

** Attachment added: "Screenshot of chromium snap 1506 after start, about to 
delete a profile that is linked for sync with a Google account"
   
https://bugs.launchpad.net/bugs/1917705/+attachment/5472318/+files/chromium-bug.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/1917705

Title:
  profile will be deleted

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

[Desktop-packages] [Bug 1917674] Re: Freeze when resuming from automatic suspension to RAM

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

Title:
  Freeze when resuming from automatic suspension to RAM

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Ubuntu 20.04 still has this issue and they want to make wayland default.

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко, 
а три файла _usr_bin_gnome-shell.1000*были созданы в каталоге var/crash/.
  We'll probably be saying goodbye to ubuntu soon.

  
  ProblemType: Ошибка
  DistroRelease: Ubuntu 20.04
  Пакет: gnome-shell 3.36.4 -1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-Общие сведения 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  Аппортверсия: 2.20.11-0ubuntu27.16
  Архитектура: amd64
  CasperMD5CheckResult: пропустить
  CurrentDesktop: ubuntu:GNOME
  Дата: СР 3 Марта 21:58:59 2021
  DisplayManager: gdm3
  Дата установки: установлен на 2021-02-28 (3 дня назад)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - релиз amd64 (20200731)
  Проценвирон:
   Терм=xterm-256color
   PATH=(пользовательский, без пользователя)
   XDG_RUNTIMEDIR= < set > 
   LANG=ru_RU.UTF-8
   SHELL= / bin / bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123 -0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: журнал обновления отсутствует (вероятно, новая установка)

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

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

[Desktop-packages] [Bug 1917066] Re: windows and popups in gnome become unresponsive

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

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


** This bug has been marked a duplicate of bug 1181666
   gnome-shell randomly blocks mouse clicks from working in app windows

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes because Xorg crashes after running `apt upgrade`

** Summary changed:

- [nvidia] gnome crashes after running `apt upgrade`
+ [nvidia] gnome crashes because Xorg crashes after running `apt upgrade`

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- [nvidia] gnome crashes because Xorg crashes after running `apt upgrade`
+ [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after 
running `apt upgrade`

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

Title:
  [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg)
  after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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

[Desktop-packages] [Bug 1685542] Re: xserver libinput and synaptics conflict on mouse/touchpad settings

2021-03-03 Thread Luiz Carlos Maciel Franco

why MatchIsTouchpad "on" for both???

synaptics and libinput xorg config at /usr/share/X11/xorg.conf.d/

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

Title:
  xserver libinput and synaptics conflict on mouse/touchpad settings

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  xserver-xorg-input-all was installed. As a result, both xserver-xorg-
  input synaptics and xserver-xorg-input-libinput got installed.

  This breaks usage for both natural scrolling *and* moving the primary
  button of the mouse/touchpad to the right (a.k.a. typing while being
  left-handed).

  Purging xserver-xorg-input-synaptics resolves it, with both natural
  scrolling and left-handedness now working.

  This bug only affects Gnome; KDE and Unity work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 22 14:44:44 2017
  DistUpgraded: 2016-12-02 17:02:11,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0655]
  InstallationDate: Installed on 2016-02-08 (439 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  MachineType: System76, Inc. Gazelle Professional
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2016-12-02 (140 days ago)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.05RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.05RS76:bd08/15/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 22 14:35:09 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context

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

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000

[Desktop-packages] [Bug 1916716] Re: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()

There are no updates that fix this bug yet. Please don't change the
status unless you know what you're doing.

** Changed in: pipewire (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  pipewire-media-session crashed with SIGSEGV in
  refresh_auto_default_nodes()

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: pipewire-bin 0.3.22-1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb 24 13:34:26 2021
  ExecutablePath: /usr/bin/pipewire-media-session
  InstallationDate: Installed on 2018-03-12 (1079 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcCmdline: /usr/bin/pipewire-media-session
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x563fdf54ea83:mov0x10(%rdx),%rax
   PC (0x563fdf54ea83) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: pipewire
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
  Title: pipewire-media-session crashed with SIGSEGV
  UpgradeStatus: Upgraded to hirsute on 2020-11-22 (94 days ago)
  UserGroups: N/A
  separator:

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

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

[Desktop-packages] [Bug 1916827] Re: Update libgweather to v40

I'm not in a hurry. This was intended more for 21.10, not 21.04. We are
on 3.36.1 right now which is the latest stable release. But
unfortunately the diff from that to master is huge, so I don't think
it's something we should force into hirsute.

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

Title:
  Update libgweather to v40

Status in libgweather package in Ubuntu:
  New

Bug description:
  Without the latest gweather v40, gnome-shell 40 fails to start:

  (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No 
property application_id on GWeatherInfo
  WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29
  _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31
  _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29
  _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25
  _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34
  _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14
  _init@resource:///org/gnome/shell/ui/panel.js:778:14
  _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13
  start@resource:///org/gnome/shell/ui/main.js:169:5
  @:1:47

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

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

We are waiting for either:

* A Mesa developer to cherry pick the fix into 20.2; or

* Mesa 22.0 to reach a future version of Ubuntu.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1917324] Re: right click on desktop 'open in terminal' option missing

Remember to enable the new extension using the 'Extensions' app.

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

Title:
  right click on desktop 'open in terminal' option missing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  right click on desktop displays a small window with just 'change background' 
'display settings' and 'settings' but 'open in terminal' is missing. see 
attachment.
  many other options appear only if I enable 
gnome-shell-extension-desktop-icons-ng
  Problem happens in both sessions Wayland and Xorg.
  Ubuntu just installed from Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 
(20210228)
  corrado@corrado-x6-hh-0228:~$ inxi -SCGx
  System:
Host: corrado-x6-hh-0228 Kernel: 5.10.0-14-generic x86_64 bits: 64 
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.3 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 3-1.3:3 
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: 
loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.4 
direct render: Yes 
  corrado@corrado-x6-hh-0228:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 15:47:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1917324] Re: right click on desktop 'open in terminal' option missing

I didn't realize Ubuntu had switched to gnome-shell-extension-desktop-
icons-ng while I was away, but it's disabled by default after upgrades.
So yes "Open in Terminal" does exist there.

It still makes no sense for the case without extensions (gnome-shell
task) because there is no context to be opened in a terminal there. The
'Desktop' folder is meaningless in that case so opening it in a terminal
is also meaningless.

I will update all the tasks with the correct status at the top of this
page now...


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

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

** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  right click on desktop 'open in terminal' option missing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  right click on desktop displays a small window with just 'change background' 
'display settings' and 'settings' but 'open in terminal' is missing. see 
attachment.
  many other options appear only if I enable 
gnome-shell-extension-desktop-icons-ng
  Problem happens in both sessions Wayland and Xorg.
  Ubuntu just installed from Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 
(20210228)
  corrado@corrado-x6-hh-0228:~$ inxi -SCGx
  System:
Host: corrado-x6-hh-0228 Kernel: 5.10.0-14-generic x86_64 bits: 64 
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.3 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 3-1.3:3 
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: 
loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.4 
direct render: Yes 
  corrado@corrado-x6-hh-0228:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 15:47:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

** Tags added: hirsute

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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

[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-03 Thread handsome_feng

** Changed in: ukui-control-center (Ubuntu)
   Status: New => Triaged

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in ukui-control-center package in Ubuntu:
  Triaged

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It must be something else.

  The difference were ~340 packages I was upgrading them to spot what broke it.
  I eventually found glib 2.66 -> 2.67 to break it.

  libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
  libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

  Old:
  /*
   * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
   * __typeof__ is used in a few places in GLib, provide a pre-processor symbol
   * to factor the check

[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`

2021-03-03 Thread Walt Mankowski

This is the output of journalctl -b0 > journal.txt after a recent crash
of gnome-shell after I ran `sudo apt upgrade`. The problems start at
roughly Mar 03 19:15:58.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5472270/+files/journal.txt

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

Title:
  [nvidia] gnome crashes after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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

[Desktop-packages] [Bug 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`

2021-03-03 Thread Walt Mankowski

I just had gnome crash on me again while running `sudo apt upgrade`.
Only 3 packages were updated. Here's the latest entry in
/var/log/apt/history.log:

Start-Date: 2021-03-03  19:16:46
Commandline: apt upgrade
Requested-By: waltman (1000)
Upgrade: python3-twisted:amd64 (18.9.0-11, 18.9.0-11ubuntu0.20.10.1), 
python3-twisted-bin:amd64 (18.9.0-11, 18.9.0-11ubuntu0.20.10.1), 
wpasupplicant:amd64 (2:2.9-1ubuntu8.1, 2:2.9-1ubuntu8.2)
End-Date: 2021-03-03  19:17:23

And here's the latest entry in /var/log/apt/term.log:

Log started: 2021-03-03  19:16:46
(Reading database ... 479992 files and directories currently installed.)
Preparing to unpack .../python3-twisted-bin_18.9.0-11ubuntu0.20.10.1_amd64.deb 
...
Unpacking python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) 
...
Preparing to unpack .../python3-twisted_18.9.0-11ubuntu0.20.10.1_all.deb ...
Unpacking python3-twisted (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) ...
Preparing to unpack .../wpasupplicant_2%3a2.9-1ubuntu8.2_amd64.deb ...
Unpacking wpasupplicant (2:2.9-1ubuntu8.2) over (2:2.9-1ubuntu8.1) ...
Setting up python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) ...
Setting up wpasupplicant (2:2.9-1ubuntu8.2) ...
Setting up python3-twisted (18.9.0-11ubuntu0.20.10.1) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for dbus (1.12.20-1ubuntu1) ...
Log ended: 2021-03-03  19:17:23

I'll attach the output of journalctl -b0 > journal.txt

Note that the times seem a bit off to me. They seem to say I started the
update at 19:16:46, but according to journal.txt I ran `apt update` at
19:15:52. I think I ran `apt upgrade` earlier than 19:16:46 because the
first stack trace for gnome-shell is at 19:16:21.

One other odd thing is that while I got a new gnome login prompt fairly
quickly, it took me about half a dozen login attempts before I could
successfully login. I didn't get any errors; rather, the screen would go
blank and then I'd get the login prompt again.

There was nothing new under /var/crash, nor under
https://errors.ubuntu.com/user/ID.

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

Title:
  [nvidia] gnome crashes after running `apt upgrade`

Status in gnome-shell package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  This is the second time this week this has happened, and perhaps the
  tenth time in the past few months. This time the packages it was
  updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
  libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
  libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64
  (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2,
  0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8,
  2:2.9-1ubuntu8.1)

  When it happened on Tuesday, the packages that were upgraded were:
  friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64
  (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10,
  2.48.3+20.10), openjdk-11-jre-headless:amd64
  (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10),
  openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10,
  11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10,
  2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02,
  1.21.3.4021-5a0a3e4b2)

  When it happens the screen goes blank, and in about 10-15 seconds I'm
  back at a gnome login prompt. Sometimes it kills my tmux session, but
  this time it didn't.

  Also about 24 hours after it happens I will suddenly start
  experiencing network issues. I'll need to restart NetworkManager and
  then it will be OK.

  I created a gist with the contents of /var/log/syslog when it happened
  at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.14
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 20:27:58 2021
  InstallationDate: Installed on 2016-12-27 (1507 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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

[Desktop-packages] [Bug 1917674] [NEW] Freeze when resuming from automatic suspension to RAM

2021-03-03 Thread Douglas Silva

Public bug reported:

Automatic suspension causes the system to freeze on resume. This doesn't
happen if I suspend it manually by opening the system menu and pressing
the suspend button. Suspension works flawlessly when it is triggered
manually.

When the system resumes from automatic suspension, the lock screen is
visible but does not respond. It's frozen. A notification says something
like "system will suspend shortly due to inactivity". It never goes
away.

The keyboard responds during this (at least for a while). The CAPS LOCK
LED turns on and off as I press it (with no delay). Sometimes I can even
switch to another TTY and kill the X server, which is why I'm reporting
it against gnome-shell. When switching TTY is impossible, I use the
"REISUB" combination to shut down. Either way, I always lose the running
session.

This is reproducible about 60% of the time. Eventually I ended up
disabling it and relying only on manual suspension.

# Additional information:
1) Ubuntu 20.04.2 LTS / Release: 20.04
2) gnome-shell 3.36.4-1ubuntu1~20.04.2

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  3 16:56:01 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-01-31 (31 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

  Automatic suspension causes the system to freeze on resume. This doesn't
  happen if I suspend it manually by opening the system menu and pressing
  the suspend button. Suspension works flawlessly when it is triggered
  manually.
  
  When the system resumes from automatic suspension, the lock screen is
- visible but does not respond. It's frozen. A notification says "system
- will suspend shortly due to inactivity". It never goes away.
+ visible but does not respond. It's frozen. A notification says something
+ like "system will suspend shortly due to inactivity". It never goes
+ away.
  
  The keyboard responds during this (at least for a while). The CAPS LOCK
  LED turns on and off as I press it (with no delay). Sometimes I can even
  switch to another TTY and kill the X server, which is why I'm reporting
  it against gnome-shell. When switching TTY is impossible, I use the
  "REISUB" combination to shut down. Either way, I always lose the running
  session.
  
  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.
  
  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Freeze when resuming from automatic suspension to RAM

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual susp

[Desktop-packages] [Bug 1192599]

2021-03-03 Thread Alex

Hey folks,

Is there any progress on this issue? It's 2021, the COVID era, and the
10-year old problem still exists and continue harming LibreOffice
usability.

Can anybody from developers take a look at it please?
Just adding an option to disable context sensitive behavior would help a lot.

The user story is simple:

   "I as a user, want my toolbars ALWAYS stay where I put them, no
matter what my mouse is doing on the rest of the screen."

Thank you very much!

Alex.

-- 
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 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb

2021-03-03 Thread Heather Ellsworth

The fix for both the focal and groovy branch has been committed and will
be picked up in the next SRU for each release.

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

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

Title:
  weak dependency to libreoffice-sdbc-hsqldb

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  The user can't create a new Base file with the wizard if the
  libreoffice-sdbc-hsqldb package isn't installed. The package
  libreoffice-base-drivers has only a "suggests" dependency to
  libreoffice-sdbc-hsqldb. It should have a "depends" dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 24 18:32:22 2021
  InstallationDate: Installed on 2020-10-12 (134 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959

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

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski

Thanks a lot, Heather! Experience tells me the likelihood that patch
will easily apply to older major versions is extremely small. That said,
I'm looking towards the future. Having this report "live" will help us
keep track of things until that time comes. Thanks again!

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1883886/+subscriptions

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Heather Ellsworth

No worries. I changed it to Triaged so we keep it more visible (good
point) and if it seems like an "easy" fix that would still apply to 6.4,
then we would consider backporting it.

** Changed in: libreoffice (Ubuntu)
   Status: Won't Fix => Triaged

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1883886/+subscriptions

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

[Desktop-packages] [Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

** Attachment removed: "monitors.xml.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472220/+files/monitors.xml.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472218/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ShellJournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472219/+files/ShellJournal.txt

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472217/+files/GsettingsChanges.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472216/+files/Dependencies.txt

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

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко, 
а три файла _usr_bin_gnome-shell.1000*были созданы в каталоге var/crash/.
  We'll probably be saying goodbye to ubuntu soon.

  
  ProblemType: Ошибка
  DistroRelease: Ubuntu 20.04
  Пакет: gnome-shell 3.36.4 -1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-Общие сведения 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  Аппортверсия: 2.20.11-0ubuntu27.16
  Архитектура: amd64
  CasperMD5CheckResult: пропустить
  CurrentDesktop: ubuntu:GNOME
  Дата: СР 3 Марта 21:58:59 2021
  DisplayManager: gdm3
  Дата установки: установлен на 2021-02-28 (3 дня назад)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - релиз amd64 (20200731)
  Проценвирон:
   Терм=xterm-256color
   PATH=(пользовательский, без пользователя)
   XDG_RUNTIMEDIR= < set > 
   LANG=ru_RU.UTF-8
   SHELL= / bin / bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123 -0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: журнал обновления отсутствует (вероятно, новая установка)

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

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

[Desktop-packages] [Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

** Description changed:

- Now it seemed that my device would take off. The fan was spinning for a
- long time and loudly, and three files _usr_bin_gnome-shell.1000*were
- created in the var/crash/ directory.
+ Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко, 
а три файла _usr_bin_gnome-shell.1000*были созданы в каталоге var/crash/.
+ We'll probably be saying goodbye to ubuntu soon.
  
- ProblemType: Bug
+ 
+ ProblemType: Ошибка
  DistroRelease: Ubuntu 20.04
- Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
- ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
+ Пакет: gnome-shell 3.36.4 -1ubuntu1~20.04.2
+ ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-Общие сведения 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27.16
- Architecture: amd64
- CasperMD5CheckResult: skip
+ Аппортверсия: 2.20.11-0ubuntu27.16
+ Архитектура: amd64
+ CasperMD5CheckResult: пропустить
  CurrentDesktop: ubuntu:GNOME
- Date: Wed Mar  3 21:58:59 2021
+ Дата: СР 3 Марта 21:58:59 2021
  DisplayManager: gdm3
- InstallationDate: Installed on 2021-02-28 (3 days ago)
- InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
+ Дата установки: установлен на 2021-02-28 (3 дня назад)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - релиз amd64 (20200731)
+ Проценвирон:
+  Терм=xterm-256color
+  PATH=(пользовательский, без пользователя)
+  XDG_RUNTIMEDIR= < set > 
   LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
- RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
+  SHELL= / bin / bash
+ RelatedPackageVersions: mutter-common 3.36.7+git20201123 -0.20.04.1
  SourcePackage: gnome-shell
- UpgradeStatus: No upgrade log present (probably fresh install)
+ UpgradeStatus: журнал обновления отсутствует (вероятно, новая установка)

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

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко, 
а три файла _usr_bin_gnome-shell.1000*были созданы в каталоге var/crash/.
  We'll probably be saying goodbye to ubuntu soon.

  
  ProblemType: Ошибка
  DistroRelease: Ubuntu 20.04
  Пакет: gnome-shell 3.36.4 -1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-Общие сведения 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  Аппортверсия: 2.20.11-0ubuntu27.16
  Архитектура: amd64
  CasperMD5CheckResult: пропустить
  CurrentDesktop: ubuntu:GNOME
  Дата: СР 3 Марта 21:58:59 2021
  DisplayManager: gdm3
  Дата установки: установлен на 2021-02-28 (3 дня назад)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - релиз amd64 (20200731)
  Проценвирон:
   Терм=xterm-256color
   PATH=(пользовательский, без пользователя)
   XDG_RUNTIMEDIR= < set > 
   LANG=ru_RU.UTF-8
   SHELL= / bin / bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123 -0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: журнал обновления отсутствует (вероятно, новая установка)

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

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

[Desktop-packages] [Bug 1917660] [NEW] This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

Public bug reported:

Now it seemed that my device would take off. The fan was spinning for a
long time and loudly, and three files _usr_bin_gnome-shell.1000*were
created in the var/crash/ directory.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  3 21:58:59 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-28 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Now it seemed that my device would take off. The fan was spinning for
  a long time and loudly, and three files _usr_bin_gnome-shell.1000*were
  created in the var/crash/ directory.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 21:58:59 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski

Of course making it Won't Fix will render this bug all but invisible,
though, and there are future release versions to consider. I don't want
to get into a status war especially given I'm not in the LibreOffice
team, but I'm sure this won't ever come up on my radar again given that
status. Even just setting it as Triaged or Confirmed would be
sufficient.

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1883886/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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 (Bluetooth A2DP codecs).

2021-03-03 Thread Jeff Nappi

For those following along - it appears that the future of Linux audio
servers will likely be PipeWire:

https://lwn.net/SubscriberLink/847412/d7826b1353e33734/

-- 
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 (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
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 1905122] Re: firefox xubuntu.20.04.1 don`t work localization

2021-03-03 Thread Alex_ander

Hi, there it is
olex@olex-VB:~/.mozilla/firefox/281v459m.default-release/extensions$ ls
langpack...@firefox.mozilla.org.xpi  r...@dictionaries.addons.mozilla.org.xpi

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

Title:
  firefox xubuntu.20.04.1 don`t work localization

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I install Xubuntu-20-04-1.iso with russian language for OS jn
  Virtualbox Computer, Firefox don`t have russian locale. I install all
  localization files and set in Firefox russian language manually. But
  anytime when I install firefox updates language settings automatically
  sets to english.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olex782 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Nov 21 12:33:07 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:354
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-21 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  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:354
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=83.0/20201112153044
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Heather Ellsworth

If the fix gets backported to the 6.4 branch in the upstream source,
then we can do an SRU but it is doubtful that will happen. (see above
comments about this fix being available in 7.2)

** Changed in: libreoffice (Ubuntu)
   Status: In Progress => Won't Fix

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

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1883886/+subscriptions

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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-03-03 Thread paquin pierre

Hi,

Last message seems to indicate that a fix is found, good news! Anything
to do to get the fix?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1917650] Re: FTBFS on riscv64 because tests are disabled by default

And this is the fix:

--- libsndfile-1.0.31/debian/rules  2021-01-29 22:05:07.0 +
+++ libsndfile-1.0.31/debian/rules  2021-03-03 16:53:14.0 +
@@ -4,6 +4,11 @@
 
 DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+# Forcefully enable tests (they are disabled by default on riscv64 in Ubuntu,
+# see https://launchpad.net/bugs/1891686) because libsndfile1-dev wants to
+# install test binaries (https://launchpad.net/bugs/1917650).
+DEB_BUILD_OPTIONS := $(filter-out nocheck,$(DEB_BUILD_OPTIONS))
+
 %:
dh $@

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

Title:
  FTBFS on riscv64 because tests are disabled by default

Status in libsndfile package in Ubuntu:
  Fix Committed

Bug description:
  dpkg defaults to nocheck on riscv64 (see bug #1891686), and as a
  consequence libsndfile fails to build from source, because
  libsndfile1-dev wants to install test binaries that weren't built:

  dh: command-omitted: The call to "dh_auto_test -a" was omitted due to 
"DEB_BUILD_OPTIONS=nocheck"
  dh_install: warning: Cannot find (any matches for) "tests/.libs/*" (tried in 
., debian/tmp)
  dh_install: error: missing files, aborting

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

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

[Desktop-packages] [Bug 1917650] Re: FTBFS on riscv64 because tests are disabled by default

Uploaded https://launchpad.net/ubuntu/+source/libsndfile/1.0.31-1ubuntu1
to fix the build failure.

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

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

Title:
  FTBFS on riscv64 because tests are disabled by default

Status in libsndfile package in Ubuntu:
  Fix Committed

Bug description:
  dpkg defaults to nocheck on riscv64 (see bug #1891686), and as a
  consequence libsndfile fails to build from source, because
  libsndfile1-dev wants to install test binaries that weren't built:

  dh: command-omitted: The call to "dh_auto_test -a" was omitted due to 
"DEB_BUILD_OPTIONS=nocheck"
  dh_install: warning: Cannot find (any matches for) "tests/.libs/*" (tried in 
., debian/tmp)
  dh_install: error: missing files, aborting

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

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

[Desktop-packages] [Bug 1917650] [NEW] FTBFS on riscv64 because tests are disabled by default

Public bug reported:

dpkg defaults to nocheck on riscv64 (see bug #1891686), and as a
consequence libsndfile fails to build from source, because
libsndfile1-dev wants to install test binaries that weren't built:

dh: command-omitted: The call to "dh_auto_test -a" was omitted due to 
"DEB_BUILD_OPTIONS=nocheck"
dh_install: warning: Cannot find (any matches for) "tests/.libs/*" (tried in ., 
debian/tmp)
dh_install: error: missing files, aborting

** Affects: libsndfile (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: Fix Committed

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

Title:
  FTBFS on riscv64 because tests are disabled by default

Status in libsndfile package in Ubuntu:
  Fix Committed

Bug description:
  dpkg defaults to nocheck on riscv64 (see bug #1891686), and as a
  consequence libsndfile fails to build from source, because
  libsndfile1-dev wants to install test binaries that weren't built:

  dh: command-omitted: The call to "dh_auto_test -a" was omitted due to 
"DEB_BUILD_OPTIONS=nocheck"
  dh_install: warning: Cannot find (any matches for) "tests/.libs/*" (tried in 
., debian/tmp)
  dh_install: error: missing files, aborting

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

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

[Desktop-packages] [Bug 1905122] Re: firefox xubuntu.20.04.1 don`t work localization

Alex_ander, after a problematic update, can you confirm that there is an
upstream langpack in your profile directory?
(/home/olex/.mozilla/firefox/281v459m.default-release/extensions
/langpack...@firefox.mozilla.org.xpi)

If so, we need to determine where it comes from.

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

Title:
  firefox xubuntu.20.04.1 don`t work localization

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I install Xubuntu-20-04-1.iso with russian language for OS jn
  Virtualbox Computer, Firefox don`t have russian locale. I install all
  localization files and set in Firefox russian language manually. But
  anytime when I install firefox updates language settings automatically
  sets to english.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olex782 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Nov 21 12:33:07 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:354
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-21 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  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:354
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=83.0/20201112153044
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1917066] Re: windows and popups in gnome become unresponsive

Extra data was during another broken UI, and I have recently restarted
due to a kernel update;

uname -r
5.6.0-1048-oem

uptime
11:28:47 up 1 day, 53 min,  2 users,  load average: 0.67, 0.35, 0.18

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1917066] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1917066/+attachment/5472186/+files/ProcEnviron.txt

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1917066] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1917066/+attachment/5472187/+files/ShellJournal.txt

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1917066] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1917066/+attachment/5472184/+files/GsettingsChanges.txt

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1917066] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1917066/+attachment/5472185/+files/ProcCpuinfoMinimal.txt

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1917066] Re: windows and popups in gnome become unresponsive

apport information

** Tags added: apport-collected

** Description changed:

  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit
  
  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  
  uname -r
  5.6.0-1047-oem
  
  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-11-13 (110 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
+ RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
+ Tags:  focal
+ Uname: Linux 5.6.0-1048-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1917066/+attachment/5472183/+files/Dependencies.txt

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-13 (110 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.6.0-1048-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

2021-03-03 Thread Bug Watch Updater

** Changed in: appstream (Debian)
   Status: Unknown => Fix Released

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+subscriptions

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

[Desktop-packages] [Bug 1917324] Re: right click on desktop 'open in terminal' option missing

2021-03-03 Thread corrado venturini

as I said above if gnome-shell-extension-desktop-icons-ng is activated the 
option appears.
but 'open in terminal' does not use an icon on desktop but just opens a 
terminal, and ctrl+alt+t works fine to open the the terminal also if 
gnome-shell-extension-desktop-icons-ng is not activated.

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

Title:
  right click on desktop 'open in terminal' option missing

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  right click on desktop displays a small window with just 'change background' 
'display settings' and 'settings' but 'open in terminal' is missing. see 
attachment.
  many other options appear only if I enable 
gnome-shell-extension-desktop-icons-ng
  Problem happens in both sessions Wayland and Xorg.
  Ubuntu just installed from Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 
(20210228)
  corrado@corrado-x6-hh-0228:~$ inxi -SCGx
  System:
Host: corrado-x6-hh-0228 Kernel: 5.10.0-14-generic x86_64 bits: 64 
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.3 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 3-1.3:3 
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: 
loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.4 
direct render: Yes 
  corrado@corrado-x6-hh-0228:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 15:47:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-03-03 Thread Sebastien Bacher

** Tags removed: block-proposed

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

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

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

[Desktop-packages] [Bug 1917629] [NEW] Nautilus doesn't work correctly for touch screens

Public bug reported:

This error is not caused by additional software, it occurs in the file manager 
even before installing ubuntu in trial mode.
These are black pop-ups that block subsequent input of commands, and that 
remain on the screen for too long.
These windows are descriptions of functions or folders, for example: Downloads 
(window: "/home/user/Downloads").
The window (/home/user/Downloads) remains on the screen even when you touch to 
any other area of the screen.

In addition, you need to click on the folders several times to open them and 
this happens randomly, sometimes just one touch is enough to open any of the 
folders, but most often three or four times.
And so, it can't be used correctly on my device.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  3 16:53:38 2021
InstallationDate: Installed on 2021-02-28 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  Nautilus doesn't work correctly for touch screens

Status in nautilus package in Ubuntu:
  New

Bug description:
  This error is not caused by additional software, it occurs in the file 
manager even before installing ubuntu in trial mode.
  These are black pop-ups that block subsequent input of commands, and that 
remain on the screen for too long.
  These windows are descriptions of functions or folders, for example: 
Downloads (window: "/home/user/Downloads").
  The window (/home/user/Downloads) remains on the screen even when you touch 
to any other area of the screen.

  In addition, you need to click on the folders several times to open them and 
this happens randomly, sometimes just one touch is enough to open any of the 
folders, but most often three or four times.
  And so, it can't be used correctly on my device.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:53:38 2021
  InstallationDate: Installed on 2021-02-28 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

Re: [Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

2021-03-03 Thread John F. Godfrey

Thanks for the update.

On Wed, Mar 3, 2021, 7:20 AM Olivier Tilloy <1917...@bugs.launchpad.net>
wrote:

> > Is there a bug fix out there?
>
> The beta builds (for the upcoming 87.0 release) contain the fix, if
> you're comfortable with adding a PPA and installing a beta version, you
> could try that (your confirmation that the bug is indeed fixed would be
> very valuable). The PPA is
> https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next/, and
> I'd recommend disabling it after you get a chance to test and confirm,
> because it's not recommended for normal use.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1917191
>
> Title:
>   firefox will not start after it crashed unexpectedly
>
> Status in Mozilla Firefox:
>   Fix Released
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   firefox crashed unexpectedly, and it will not start or restart.  I am
> running the latest ubuntu-20.04.2 LTS, all updates applied.  firefox
> 86.0+build3
>   ---
>   ProblemType: Bug
>   AddonCompatCheckDisabled: False
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  johnfg 1725 F pulseaudio
>/dev/snd/controlC1:  johnfg 1725 F pulseaudio
>   BuildID: 20210222142601
>   CasperMD5CheckResult: skip
>   Channel: Unavailable
>   CurrentDesktop: ubuntu:GNOME
>   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:348
>   DefaultProfilePrefSources: prefs.js
>   DefaultProfileThemes: extensions.sqlite corrupt or missing
>   DistroRelease: Ubuntu 20.04
>   ForcedLayersAccel: False
>   InstallationDate: Installed on 2020-02-22 (371 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   IpRoute:
>default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600
>10.8.0.0/24 via 10.8.0.17 dev tun0
>10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18
>169.254.0.0/16 dev wlp10s0 scope link metric 1000
>192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8
> metric 600
>   NonfreeKernelModules: openafs
>   Package: firefox 86.0+build3-0ubuntu0.20.04.1
>   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-66.74-generic 5.4.86
>   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:348
>   Profile0PrefSources: prefs.js
>   Profile0Themes: extensions.sqlite corrupt or missing
>   Profiles:
>Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date)
>Profile0 - LastVersion=86.0/20210222142601
>   RunningIncompatibleAddons: False
>   Tags:  focal
>   Uname: Linux 5.4.0-66-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 07/05/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V4.00L12
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: CF52-4
>   dmi.board.vendor: Panasonic Corporation
>   dmi.board.version: 1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Panasonic Corporation
>   dmi.chassis.version: 001
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001:
>   dmi.product.family: CF52-4
>   dmi.product.name: CF-52SLGDD1M
>   dmi.product.sku: CF-52SLGDD1M
>   dmi.product.version: 004
>   dmi.sys.vendor: Panasonic Corporation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions
>

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

Title:
  firefox will not start after it crashed unexpectedly

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

Bug description:
  firefox crashed unexpectedly, and it will not start or restart.  I am running 
the latest ubuntu-20.04.2 LTS, all updates applied.  firefox 86.0+build3
  --- 
  Problem

[Desktop-packages] [Bug 1916827] Re: Update libgweather to v40

2021-03-03 Thread Treviño

FFe I  meant

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

Title:
  Update libgweather to v40

Status in libgweather package in Ubuntu:
  New

Bug description:
  Without the latest gweather v40, gnome-shell 40 fails to start:

  (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No 
property application_id on GWeatherInfo
  WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29
  _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31
  _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29
  _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25
  _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34
  _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14
  _init@resource:///org/gnome/shell/ui/panel.js:778:14
  _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13
  start@resource:///org/gnome/shell/ui/main.js:169:5
  @:1:47

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

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

[Desktop-packages] [Bug 1916827] Re: Update libgweather to v40

2021-03-03 Thread Treviño

Not sure, but do we need a FF for this? Is it retro-compatible, I guess,
right?

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

Title:
  Update libgweather to v40

Status in libgweather package in Ubuntu:
  New

Bug description:
  Without the latest gweather v40, gnome-shell 40 fails to start:

  (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No 
property application_id on GWeatherInfo
  WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29
  _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31
  _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29
  _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25
  _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34
  _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14
  _init@resource:///org/gnome/shell/ui/panel.js:778:14
  _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13
  start@resource:///org/gnome/shell/ui/main.js:169:5
  @:1:47

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

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

[Desktop-packages] [Bug 1917066] Re: windows and popups in gnome become unresponsive

Thanks for answering Daniel.

  1. Only the default Ubuntu AppIndicators and Dock are enabled in the
'Extensions' app.

  2. ~/.local/share/gnome-shell/extensions No such file or directory

  3. Reboot and the problem happens again every few weeks or months

  4. should I run "apport-collect 1917066" any time or only via ssh when
the UI is broken?

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

Title:
  windows and popups in gnome become unresponsive

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  windows and popups in gnome become unresponsive.
  I can start and quit apps from the bar but can not interact with them (no 
action on x button or capslock on the keyboard)
  I am forced to ssh in to run apport-cli gnome-session-quit

  lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS

  uname -r
  5.6.0-1047-oem

  I'm not sure what pkgname is at fault but let me know if there is any
  info or testing I can do to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19
  Uname: Linux 5.6.0-1047-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:27:16 2021
  ExecutablePath: /usr/lib/gdm3/gdm-wayland-session
  InstallationDate: Installed on 2020-11-13 (105 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

> Is there a bug fix out there?

The beta builds (for the upcoming 87.0 release) contain the fix, if
you're comfortable with adding a PPA and installing a beta version, you
could try that (your confirmation that the bug is indeed fixed would be
very valuable). The PPA is
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next/, and
I'd recommend disabling it after you get a chance to test and confirm,
because it's not recommended for normal use.

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

Title:
  firefox will not start after it crashed unexpectedly

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

Bug description:
  firefox crashed unexpectedly, and it will not start or restart.  I am running 
the latest ubuntu-20.04.2 LTS, all updates applied.  firefox 86.0+build3
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnfg 1725 F pulseaudio
   /dev/snd/controlC1:  johnfg 1725 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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:348
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-22 (371 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 
   10.8.0.0/24 via 10.8.0.17 dev tun0 
   10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 
   169.254.0.0/16 dev wlp10s0 scope link metric 1000 
   192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600
  NonfreeKernelModules: openafs
  Package: firefox 86.0+build3-0ubuntu0.20.04.1
  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-66.74-generic 5.4.86
  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:348
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date)
   Profile0 - LastVersion=86.0/20210222142601
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.00L12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CF52-4
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CF52-4
  dmi.product.name: CF-52SLGDD1M
  dmi.product.sku: CF-52SLGDD1M
  dmi.product.version: 004
  dmi.sys.vendor: Panasonic Corporation

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

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

[Desktop-packages] [Bug 1917624] [NEW] no sound at all

2021-03-03 Thread W.R. Irsyad Hamda

Public bug reported:

1. 
Description:Ubuntu 20.04.2 LTS
Release:20.04

2. 
alsa-base 1.0.25+dfsg-0ubuntu5

3. I hope can hear sound from my laptop speaker

4. I can not hear any sound from my speaker

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  no sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1. 
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  2. 
  alsa-base 1.0.25+dfsg-0ubuntu5

  3. I hope can hear sound from my laptop speaker

  4. I can not hear any sound from my speaker

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

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

[Desktop-packages] [Bug 1914077] Re: [snap] Add Greek langpack to LibreOffice snap package

2021-03-03 Thread Tijn Boissevain

I would like te ask for a Dutch (NL) language pack - and UI pack - in
the Snap version of LibreOffice.

But I think it is more universal to make and publish a tutorial for Snap
users how to add any desired (UI) language pack to the package. The
locales itself are available in the regular LibreOffice packages, so
that cannot be an obstacle.

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

Title:
  [snap] Add Greek langpack to LibreOffice snap package

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Currently, the Libreoffice snap package supports the following UI
  languages:

  English (USA)
  Catalan
  Chinese (Traditional)
  French (France)
  German
  Hungarian
  Italian
  Japanese
  Polish
  Portuguese (both Portugal and Brazil)
  Russian
  Spanish (Spain)
  Turkish

  Greek is spoken by 11.1m people, which is a similar number for Catalan and 
Hundarian.
  In the Greek Public Service (for example, the judicial system), there are 
many Ubuntu laptops with no upgrade path for the latest version of LibreOffice.

  Can you please add Greek to the list?

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

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

[Desktop-packages] [Bug 1916716] Re: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()

2021-03-03 Thread Jangila Brahma

** Changed in: pipewire (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pipewire-media-session crashed with SIGSEGV in
  refresh_auto_default_nodes()

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/e118c16c7af628a69e39bc59672e7a25ecdc8e6e

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: pipewire-bin 0.3.22-1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb 24 13:34:26 2021
  ExecutablePath: /usr/bin/pipewire-media-session
  InstallationDate: Installed on 2018-03-12 (1079 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcCmdline: /usr/bin/pipewire-media-session
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x563fdf54ea83:mov0x10(%rdx),%rax
   PC (0x563fdf54ea83) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: pipewire
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so
  Title: pipewire-media-session crashed with SIGSEGV
  UpgradeStatus: Upgraded to hirsute on 2020-11-22 (94 days ago)
  UserGroups: N/A
  separator:

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

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

[Desktop-packages] [Bug 1872870] Re: When zoom is enabled, mouse pointer leaves square trails on desktop

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

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

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

Title:
  When zoom is enabled, mouse pointer leaves square trails on desktop

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Problem:

  When you turn on Zoom from the Accessibility menu, the mouse leaves
  square shaped trails as it moves.

  Steps to Reproduce:

  1. Under the Settings applet's Accessibility menu, turn on Zoom.
  2. Observe the mouse cursor leaving little square patterns wherever it goes, 
obscuring whatever you're trying to work on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  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-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 21:50:16 2020
  InstallationDate: Installed on 2020-01-09 (96 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to focal on 2020-01-24 (82 days ago)

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

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

[Desktop-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

** Summary changed:

- Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)
+ Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

** Description changed:

- Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver).
+ Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).
  
  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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

Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-03-03 Thread Coiby Xu

On Tue, Mar 02, 2021 at 01:40:54AM -, Helmut Stult wrote:
>Works again - have to set CONFIG_I2C_HID_ACPI=m in config

Well done!

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType

[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2

The fixes for focal are:

gnome-shell: upstream, scheduled for release in future version 3.36.9

gnome-shell-extension-desktop-icons: patch proposed in comment #28

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

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]

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

Bug description:
  [Impact]

  Gnome Shell crashes at random times when the Desktop or home directory
  is modified, and the desktop-icons extension tries to refresh.

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

  [Test Case]

  Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell
  should not crash or freeze.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading, like this bug.

  [Other Info]

  See also bug 1898910

  ---

  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  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-shell/+bug/1898005/+subscriptions

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

[Desktop-packages] [Bug 1917212] Re: Text in interface gone

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

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


** Tags added: amdgpu

** Summary changed:

- Text in interface gone
+ [amdgpu] Text in interface gone

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

** This bug has been marked a duplicate of bug 1774053
   Missing characters in gnome-shell after lock screen

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

Title:
  [amdgpu] Text in interface gone

Status in mutter package in Ubuntu:
  New

Bug description:
  Text in interface in general is lost. Back after reboot. I have
  noticed it after been playing Valheim. Dunno if it's connected tho. I
  have a few screenshots here:

  https://drive.benis.se/s/co6Z3cWDaDCpJ9N

  Thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  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: Sun Feb 28 13:20:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver, 2.5.0, 5.8.0-43-generic, x86_64: installed
   openrazer-driver, 2.5.0, 5.8.0-44-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Vega 10 XL/XT [Radeon RX Vega 
56/64] [148c:2388]
  InstallationDate: Installed on 2020-10-13 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. Z490M
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.ppfeaturemask=0x 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z490M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/17/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490M:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490M:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Z490 MB
  dmi.product.name: Z490M
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~f~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
21.0.0~rc4+git2102262047.10611abc193~f~mesarc1
  version.libgl1-mesa-glx: libgl1-mesa-glx 
21.0.0~rc4+git2102262047.10611abc193~f~mesarc1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1917212/+subscriptions

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

[Desktop-packages] [Bug 1917218] Re: X Crash appears to happen when using Zoom

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

Thanks for the bug report. I can actually see two unrelated crashes
here.

1. XorgLogOld.txt is showing what looks like bug 1871959.

2. CurrentDmesg.txt is showing a kernel crash in nvkm_pmu_init [nouveau]

So I'm guessing you mostly want to subscribe to bug 1871959. But I will
also make this bug about the kernel crash. Although installing the
official Nvidia driver via the 'Additional Drivers' app should avoid
that.

** Summary changed:

- X Crash appears to happen when using Zoom
+ [nouveau] Repeated crashes in nvkm_pmu_init

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

** Tags added: nouveau

** This bug has been marked a duplicate of bug 1895502
   nouveau keeps crashing in nvkm_pmu_init

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

Title:
  [nouveau] Repeated crashes in nvkm_pmu_init

Status in linux package in Ubuntu:
  New

Bug description:
  Suddenly end up looking a black screen with number indicating that it cleared 
blocks.
  =>This *usually* happens when using Zoom screen share or watching Zoom video 
recording.
  =>Last X crash was about 5:03 am US Central Time Feb 28, 2021, approximately 
90 mins ago.
  =>Crash frequency is about 2-4 times a week as an estimate.
  =>If check up time, I get the time of last system reboot (so not whole system 
being restarted):
  ==>  07:41:21 up 2 days, 10:14,  1 user,  load average: 3.87, 5.35, 6.88
  ==>  This was probably the correct time for the last full system restart 
after applying OS patches
  =>After crash, immediately takes me to login screen for X within 10 secs (no 
Ubuntu boot screen)
  =>Initially this system was 18.04 updated regularly. It was upgraded to 20.04 
(using software update process - upgraded in place) about a month ago when this 
restart situation started.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 28 07:32:13 2021
  DistUpgraded: 2021-01-17 00:24:49,141 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 5.4.0-65-generic, x86_64: installed
   evdi, 1.7.0, 5.4.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:15ae]
 Subsystem: ASUSTeK Computer Inc. GP108M [GeForce MX150] [1043:15ae]
  InstallationDate: Installed on 2018-09-09 (902 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. X411UN
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=3288b326-8ac0-4e55-b66d-4b09be14341b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-01-17 (42 days ago)
  dmi.bios.date: 06/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X411UN.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X411UN
  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.:bvrX411UN.307:bd06/04/2018:svnASUSTeKCOMPUTERINC.:pnX411UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook S
  dmi.product.name: X411UN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-vide

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

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

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

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1917222] Re: [ASUS Z97-P] Some videos play sound some dont. Web browsers fail to play sound

Do other apps like audio players or video players have sound? Is it only
web browsers that are affected? What happens if you click 'Test' in
Settings > Sound ?

** Summary changed:

- Some videos play sound some dont. Web browsers fail to play sound
+ [ASUS Z97-P] Some videos play sound some dont. Web browsers fail to play sound

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

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

Title:
  [ASUS Z97-P] Some videos play sound some dont. Web browsers fail to
  play sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 is clean install. some of the videos play sound and some
  do not. I have no deep knowledge.  In the web browsers both firefox
  and chrome browser you in you tube  normally no sound but one or two
  play sound but not clear.I am not able to solve this issue . Due this
  problem I have stopped using Ubuntu and use only windows 10 in dual
  boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  murtyvonna   1708 F pulseaudio
   /dev/snd/controlC1:  murtyvonna   1708 F pulseaudio
   /dev/snd/controlC0:  murtyvonna   1708 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 28 20:40:24 2021
  InstallationDate: Installed on 2021-02-02 (26 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2907
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1917324] Re: right click on desktop 'open in terminal' option missing

I don't think that feature makes sense in gnome-shell which has no
desktop icons at all.

If you would like it added to gnome-shell-extension-desktop-icons or
gnome-shell-extension-desktop-icons-ng then please let us know.

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

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

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

Title:
  right click on desktop 'open in terminal' option missing

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  right click on desktop displays a small window with just 'change background' 
'display settings' and 'settings' but 'open in terminal' is missing. see 
attachment.
  many other options appear only if I enable 
gnome-shell-extension-desktop-icons-ng
  Problem happens in both sessions Wayland and Xorg.
  Ubuntu just installed from Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 
(20210228)
  corrado@corrado-x6-hh-0228:~$ inxi -SCGx
  System:
Host: corrado-x6-hh-0228 Kernel: 5.10.0-14-generic x86_64 bits: 64 
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.3 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 3-1.3:3 
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: 
loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.3.4 
direct render: Yes 
  corrado@corrado-x6-hh-0228:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  1 15:47:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-28 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1906243] Re: Audio comes out through system speakers when headset autoconnects

2021-03-03 Thread Sujit Kumar

@sheghembekassim please click "this bug affects me too", otherwise this
bug will always remain Unconfirmed.

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

Title:
  Audio comes out through system speakers when headset autoconnects

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it
  automatically (Or at least it appears to be connected to it). It says
  connected and the switch is in the ON position in Bluetooth settings,
  however the audio still comes out of the speakers, the icon next to
  the volume bar in the top-right menu shows the speaker icon instead of
  the headphone icon. I have to disconnect the headset and re-connect it
  from Bluetooth settings for the audio to go to the headset.

  It doesn't work only when it connects automatically. Always works when I 
connect it manually.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sujit  1394 F pulseaudio
   /dev/snd/controlC0:  sujit  1394 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-28 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3.8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0JKRPT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3446
  dmi.product.sku: 0662
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2021-03-03 Thread Sujit Kumar

I also face this issue and have opened a bug here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243
(Please click "I'm facing this bug too" if you are facing this issue).

This exact same bug has been marked as a duplicate here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1874513 (The
one @nivg mentioned). This was marked as a duplicate to the bug in this
page, but I don't think these bugs are the same.

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in pulseaudio source package in Groovy:
Fix Released

Bug description:
[Impact]

Selected audio output device in Settings is ignored after upgrading to
Ubuntu 20.04.

[Test Case]

Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
to 20.04. When done, attempt to connect a Bluetooth or USB audio
device and use it via Settings.

[Regression Potential]

Unknown/low. The fix is from upstream and has already been released to
Ubuntu 20.10 without any problems. Only worth noting it works by
detecting and removing audio configurations made via older versions of
PulseAudio. So upon upgrading some old settings may be reset to
defaults, but the idea is that's less bad than audio devices being
unusable (this bug).

[Original Bug Report]

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1917334] Re: Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling)

Please try some older/newer kernel versions so that we can figure out
when the problem started, or if it's already been fixed...

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

** Summary changed:

- Xorg freeze on a Dell 7240
+ Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from 
i915_gem_object_set_tiling)

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

** Summary changed:

- Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from 
i915_gem_object_set_tiling)
+ [i915] Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from 
i915_gem_object_set_tiling)

** Tags added: 5.8-gfx

** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (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/1917334

Title:
  [i915] Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from
  i915_gem_object_set_tiling)

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New

Bug description:
  New Dell laptop, fresh 20.04 install, 5.8.0-44-generic
  #50~20.04.1-Ubuntu SMP, had two xorg freezes the same day. Managed to
  grab dmesg from one where I got a text console:

  [12775.113344] BUG: unable to handle page fault for address: e6787008
  [12775.113347] #PF: supervisor read access in kernel mode
  [12775.113347] #PF: error_code(0x) - not-present page
  [12775.113348] PGD 0 P4D 0 
  [12775.113349] Oops:  [#1] SMP NOPTI
  [12775.113351] CPU: 0 PID: 2107 Comm: gnome-shell Tainted: G   O  
5.8.0-44-generic #50~20.04.1-Ubuntu
  [12775.113351] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 
01/18/2021
  [12775.113355] RIP: 0010:kfree+0x55/0x250
  [12775.113355] Code: 80 49 01 dc 0f 82 03 02 00 00 48 c7 c0 00 00 00 80 48 2b 
05 c5 d9 1e 01 49 01 c4 49 c1 ec 0c 49 c1 e4 06 4c 03 25 a3 d9 1e 01 <49> 8b 44 
24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d
  [12775.113356] RSP: 0018:a4cfc2bebcb0 EFLAGS: 00010286
  [12775.113357] RAX: 6c3b8000 RBX: 0020 RCX: 
93cc1c11d238
  [12775.113358] RDX: 0001 RSI: 00106e56 RDI: 
0020
  [12775.113358] RBP: a4cfc2bebcd0 R08: 93cc5fa5f4a8 R09: 
00106e77
  [12775.113359] R10:  R11: 0001 R12: 
e6787000
  [12775.113359] R13: 9e345309 R14: 0002 R15: 
93cb5060e800
  [12775.113360] FS:  7fdebf4b9cc0() GS:93cc6f60() 
knlGS:
  [12775.113361] CS:  0010 DS:  ES:  CR0: 80050033
  [12775.113361] CR2: e6787008 CR3: 00081c144006 CR4: 
00760ef0
  [12775.113362] PKRU: 5554
  [12775.113362] Call Trace:
  [12775.113366]  bitmap_free+0x9/0x10
  [12775.113390]  i915_gem_object_set_tiling+0x1db/0x480 [i915]
  [12775.113406]  i915_gem_set_tiling_ioctl+0x146/0x240 [i915]
  [12775.113420]  ? i915_gem_object_set_tiling+0x480/0x480 [i915]
  [12775.113429]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [12775.113431]  ? ___sys_recvmsg+0x8d/0xc0
  [12775.113437]  drm_ioctl+0x234/0x3d0 [drm]
  [12775.113450]  ? i915_gem_object_set_tiling+0x480/0x480 [i915]
  [12775.113452]  ? __fget_light+0x62/0x80
  [12775.113454]  ? fput+0x13/0x20
  [12775.113455]  ? __sys_recvmsg+0x94/0xb0
  [12775.113456]  ksys_ioctl+0x9d/0xd0
  [12775.113456]  __x64_sys_ioctl+0x1a/0x20
  [12775.113458]  do_syscall_64+0x49/0xc0
  [12775.113460]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [12775.113461] RIP: 0033:0x7fdec490d50b
  [12775.113462] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
  [12775.113462] RSP: 002b:7fff93f0ee88 EFLAGS: 0246 ORIG_RAX: 
0010
  [12775.113463] RAX: ffda RBX: 55f90aa9b4f0 RCX: 
7fdec490d50b
  [12775.113464] RDX: 7fff93f0eee0 RSI: c0106461 RDI: 
000d
  [12775.113464] RBP: 7fff93f0ef60 R08:  R09: 
55f90aa9bc80
  [12775.113465] R10: 55f90aa97dd0 R11: 0246 R12: 
55f91177efe0
  [12775.113465] R13: 55f90aa9b4f0 R14: 7fff93f0eee0 R15: 
c0106461
  [12775.113467] Modules linked in: cdc_ether usbnet r8152 mii rfcomm 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm cmac algif_hash algif_skcipher 
af_alg bnep snd_sof_pci snd_hda_codec_hdmi snd_sof_intel_byt snd_sof_intel_ipc 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda 
snd_sof snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi binfmt_misc 
snd_hda_codec_realtek mei_hdcp snd_hda_codec_generic dell_laptop intel_rapl_msr 
nls_iso8859_1 ledtrig_audio snd_soc_core x86_pkg_temp_thermal intel_powerclamp 
snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_hda_intel kvm_intel btusb 
btrtl btbcm snd_intel_dspcfg btintel kvm snd_hda_codec snd_hda_core snd_hwdep 
bluetooth dell_wmi uvcvideo s

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

Thanks for the bug report.

The attached files seem to show the nouveau kernel driver is crashing,
so you will probably experience a freeze when that happens. This is a
somewhat common problem and the best we can suggest is to use the
official Nvidia driver instead. It seems driver version 340 is the
correct one for your GPU so to install that you can run:

  sudo apt install nvidia-340

and then reboot.

** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

** Summary changed:

- [nouveau] Xorg freeze
+ [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

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

Title:
  [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Random freezes often using browsers like Chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 02:28:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: LG Electronics, Inc. GT218M [GeForce 310M] [1854:0847]
  InstallationDate: Installed on 2021-02-28 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LG Electronics A410-K.BE47P1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=d6b46107-6275-4957-9374-b6594451e87a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: QL7L3G11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrQL7L3G11:bd05/25/2011:svnLGElectronics:pnA410-K.BE47P1:pvrTBD:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: A410-K.BE47P1
  dmi.product.sku: Calpella_CRB
  dmi.product.version: TBD
  dmi.sys.vendor: LG Electronics
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux/+bug/1917415/+subscriptions

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

[Desktop-packages] [Bug 1874513] Re: No sound through bluetooth headphones

2021-03-03 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  No sound through bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Headphones are paired and connected, presented in Output device list.
  Selected as output device but still sound is played through laptop speakers.

  Help the following workaround:
  install pavucontrol
  in pavucontrol select Headphones(not plugged in) as port in Output Devices tab
  after disconnecting and reconnecting BT headphones you have to make this 
procedure again manually everytime.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stas   2878 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 21:13:57 2020
  InstallationDate: Installed on 2019-10-19 (186 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-21 (2 days ago)
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0Y9N5X
  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.:rn0Y9N5X: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/pulseaudio/+bug/1874513/+subscriptions

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

[Desktop-packages] [Bug 1917554] Re: VGA driver not available for download

The attached files seem to show the correct and only drivers are already
active. You cannot replace or upgrade them.

If you are experiencing an actual problem then please describe it.

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

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

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

Title:
  VGA driver not available for download

Status in Ubuntu:
  Invalid

Bug description:
  as VGA driver not available for download for dell latitude 3410 please
  help me to install VGA driver for the same laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Mar  3 08:24:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09ec]
  InstallationDate: Installed on 2021-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3410
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=46ff8419-3c77-44f1-833c-0dbf4a00389b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0J6VTW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/17/2020:br1.3:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3410
  dmi.product.sku: 09EC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1917554/+subscriptions

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

[Desktop-packages] [Bug 1917129] Re: startx error

There are no errors in that log file. Instead of focusing on that,
please try to describe the problem you are trying to solve...

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

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

Title:
  startx error

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 1285.878] X Protocol Version 11, Revision 0
  [ 1285.878] Build Operating System: Linux 4.15.0-124-generic x86_64 Ubuntu
  [ 1285.878] Current Operating System: Linux ubuntu 4.4.0-87-generic 
#110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64
  [ 1285.878] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=535b2e54-2659-4d31-904f-fe8fc83565a9 ro
  [ 1285.878] Build Date: 30 November 2020 08:01:56PM
  [ 1285.878] xorg-server 2:1.19.6-1ubuntu4.8 (For technical support please see 
http://www.ubuntu.com/support)
  [ 1285.878] Current version of pixman: 0.34.0
  [ 1285.878] Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  [ 1285.878] Markers: (--) probed, () from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 1285.879] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 27 02:20:48 
2021
  [ 1285.882] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 1285.884] (==) No Layout section. Using the first Screen section.
  [ 1285.884] (==) No screen section available. Using defaults.
  [ 1285.884] () |-->Screen "Default Screen Section" (0)
  [ 1285.884] (**) | |-->Monitor ""
  [ 1285.885] (==) No monitor specified for screen "Default Screen Section".
  Using a default monitor configuration.
  [ 1285.885] (==) Automatically adding devices
  [ 1285.885] (==) Automatically enabling devices
  [ 1285.885] (==) Automatically adding GPU devices
  [ 1285.885] (==) Automatically binding GPU devices
  [ 1285.885] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 1285.890] Entry deleted from font path.
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [ 1285.890] Entry deleted from font path.
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [ 1285.890] Entry deleted from font path.
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
  [ 1285.890] Entry deleted from font path.
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [ 1285.890] Entry deleted from font path.
  [ 1285.890] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [ 1285.890] Entry deleted from font path.
  "/var/log/Xorg.0.log" 227L, 14930C

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

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

[Desktop-packages] [Bug 1872870] Re: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop

** Package changed: meta-gnome3 (Ubuntu) => mutter (Ubuntu)

** Tags added: hirsute

** Summary changed:

- Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop
+ When zoom is enabled, mouse pointer leaves square trails on desktop

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1678
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1678

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

** Tags added: cursor

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

Title:
  When zoom is enabled, mouse pointer leaves square trails on desktop

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Problem:

  When you turn on Zoom from the Accessibility menu, the mouse leaves
  square shaped trails as it moves.

  Steps to Reproduce:

  1. Under the Settings applet's Accessibility menu, turn on Zoom.
  2. Observe the mouse cursor leaving little square patterns wherever it goes, 
obscuring whatever you're trying to work on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  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-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 21:50:16 2020
  InstallationDate: Installed on 2020-01-09 (96 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to focal on 2020-01-24 (82 days ago)

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

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

[Desktop-packages] [Bug 1874856] Re: Unwanted square mouse trail

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

** Summary changed:

- Unwanted mouse trail
+ Unwanted square mouse trail

** This bug has been marked a duplicate of bug 1872870
   When zoom is enabled, mouse pointer leaves square trails on desktop

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

Title:
  Unwanted square mouse trail

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Moving mouse leaves a trail of squares for a few seconds on a fresh
  20.04 install. This happens with proprietary nvidia 440 drivers on my
  GeForce GTX 1050 mobile.

  Could be related to my submission
  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/1874819

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 17:59:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  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.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X580VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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
  xserver.bootTime: Fri Apr 24 16:45:55 2020
  xserver.configfile: default
  xserver.errors:
   NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver
   NVIDIA(G0): Failing initialization of X screen
   systemd-logind: failed to release device: Device not taken
   systemd-logind: failed to release device: Device not taken
   modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1879237] Re: Lines appear on Desktop when moving mouse around.

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

** This bug is no longer a duplicate of bug 1874856
   Unwanted square mouse trail
** This bug has been marked a duplicate of bug 1872870
   When zoom is enabled, mouse pointer leaves square trails on desktop

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

Title:
  Lines appear on Desktop when moving mouse around.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS
  Release:  20.04
  It is not related to Xorg.
  After upgrade to 20.04.
  Not with any previous version.
  It happens only on the Desktop, never in any other programs.
  Lines stay on screen between 1 and 2 seconds.
  It happens on my laptop hp probook 450-G1 (under wayland), dell inspiron 7773 
(under wayland) and pc built box (GPU radeon under Xorg).

  Posted the issue on Ask Ubuntu, but no answer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 06:47:50 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 
5600 OEM/5600 XT / 5700/5700 XT] [1462:3811]
  InstallationDate: Installed on 2020-04-24 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=97a84f93-4387-4b54-bdc6-7e20b816ecb9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS PRO
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS PRO
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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
  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/1879237/+subscriptions

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

[Desktop-packages] [Bug 1917073] Re: Internal laptop speakers after connecting other sound devices

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1917073

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: focal

** Summary changed:

- Internal laptop speakers after connecting other sound devices
+ [Dell Latitude E5570] Internal laptop speakers after connecting other sound 
devices

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

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

Title:
  [Dell Latitude E5570] Internal laptop speakers after connecting other
  sound devices

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  If I use another output device than "Headphones - internal audio", the
  sound comes out of the internal laptop speakers.

  I tried with headphones in usb or in bluetooth, the output device is
  well set but the sound is only on the laptop speakers.

  So the only way to get sound is to use headphones on the jack port.

  
  I'm on Ubuntu 20.04.2 with pulseaudio 1:13.99.1-1ubuntu3.10 on a Dell 
Latitude E5570.

  Thank you

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

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

[Desktop-packages] [Bug 1917103] Re: Accessibility: Zoom: Mouse pointer leaves square trails as it moves across the screen

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

** This bug has been marked a duplicate of bug 1872870
   Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop

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

Title:
  Accessibility: Zoom: Mouse pointer leaves square trails as it moves
  across the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to Reproduce:

  In the Settings applet choose Accessibility -> Zoom. Toggle the switch
  on. This happens whether or not you actually magnify the screen.

  When the mouse is moved anywhere on the screen, it leaves behind
  repeated partial square trails in its path.

  This is the same issue reported in:
  https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: skip
  CasperVersion: 1.456
  Date: Sat Feb 27 00:06:13 2021
  DisplayManager: gdm3
  GsettingsChanges:

  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1917066] Re: windows and popups in gnome become unresponsive