date:20201207

Maybe a couple would be most helpful, please.

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

Also proposed to Debian:

https://salsa.debian.org/gnome-team/shell-extensions/gnome-shell-
extension-desktop-icons/-/merge_requests/10

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed

Bug description:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell in Ubuntu 20.10 (beta).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

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

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

[Desktop-packages] [Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

I still don't have any data to analyse here but the test case sounds
similar to my test case for bug 1898005. So I am guessing this will be a
duplicate of that.

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

2020-12-07 Thread Arvind

Additionally, I noticed this issue on Linuxmint 20 (Ulayana) release
installed on a Lenovo T580 Thinkpad. The displays attached via USB3.0
(dell D3100) totally become stuttery and unusable. The Xserver fix
provided by DisplayLink makes it useable
(https://www.displaylink.com/downloads/file?d=310) (without and with
laptop lid closed) but there are still a lot of stutters/lag overall.

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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

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

[Desktop-packages] [Bug 1897454] Re: [snap] Chromium dev cuts off Wayland display

2020-12-07 Thread Alberto Donato

I did a quick test by unpacking the current stable snap (87.0.4280.88,
rev. 1421)

After removing DISABLE_WAYLAND, adding wayland plug, I copied missing
/usr/lib/x86_64-linux-gnu/libEGL* and /usr/lib/x86_64-linux-
gnu/libGLESv2* to the unpacked snap.

I now get the following errors:

[1709538:1709538:1207/111235.153734:ERROR:gl_surface_egl.cc(1297)] EGL display 
query failed with error EGL_BAD_PARAMETER
[1709538:1709538:1207/111235.153855:ERROR:gl_surface_egl.cc(1322)] 
eglInitialize Default failed with error EGL_BAD_DISPLAY
[1709538:1709538:1207/111235.154551:ERROR:gl_ozone_egl.cc(20)] 
GLSurfaceEGL::InitializeOneOff failed.
[1709538:1709538:1207/111235.170003:ERROR:viz_main_impl.cc(150)] Exiting GPU 
process due to errors during initialization
[1709560:1709560:1207/111235.252396:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.


The process doesn't die and it seems it creates an invisible window (it shows 
in the app switcher), but nothing shows on screen

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

Title:
  [snap] Chromium dev cuts off Wayland display

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item&px=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

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

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

[Desktop-packages] [Bug 1878547] Re: "Quit %d Windows" not localized to non-English

2020-12-07 Thread Amr Ibrahim

Please nominate to Focal so the bug stays open in Focal. I don't have
the necessary permission to do it.

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

Title:
  "Quit %d Windows" not localized to non-English

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  If I have more than 1 application windows open, the 'quit 2 windows' command 
is not localized (not in italian at least).
  See attachemnt

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 09:01:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-08 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1878547/+subscriptions

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

[Desktop-packages] [Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-07 Thread abcdef

A glance through journal.txt did not give me confidence that it wasn't
bleeding all sorts of info, since my name was on every line.

Here's a relevant excerpt:

```
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: libinput error: event5  - 
bcm5974: client bug: event processing lagging behind by 17ms, your system is 
too slow
dec 07 11:53:27 computer-name gnome-shell[1606]: JS ERROR: TypeError: fileItem 
is undefined
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: **
dec 07 11:53:28 computer-name gnome-shell[1606]: 
St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child 
== NULL)
dec 07 11:53:28 computer-name gnome-shell[1606]: Bail out! 
St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child 
== NULL)
dec 07 11:53:28 computer-name gnome-shell[1606]: GNOME Shell crashed with 
signal 6
dec 07 11:53:28 computer-name gnome-shell[1606]: == Stack trace for context 
0x55789c2411b0 ==
dec 07 11:53:28 computer-name gnome-shell[1606]: #0   55789c6da140 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 
(aa6a22a0420 @ 10)
dec 07 11:53:28 computer-name gnome-shell[1606]: #1   7ffdd4d298e0 b   
self-hosted:225 (39bd78b6a100 @ 273)
dec 07 11:53:28 computer-name gnome-shell[1606]: #2   55789c6da0a8 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 
(aa6a22a0470 @ 43)
dec 07 11:53:28 computer-name gnome-shell[1606]: #3   55789c6da018 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:209 
(aa6a22a05b0 @ 32)
d

[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash

2020-12-07 Thread Harald Sitter

Tested 8.59+17.10.20170606-0ubuntu2.20.10.1 on groovy and the test
scenario outlined in the description is working now. The auth dialog no
longer crashes singond.

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

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Desktop-packages] [Bug 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta

2020-12-07 Thread lizhiyuan

I found a solution: install TopIcons Plus gnome plugin. Plug address:
https://extensions.gnome.org/extension/1031/topicons/

After installing the plug-in, these software can display the icon after 
booting. I assume this a problem caused by the gnome api?
Ubuntu 20.04/20.10

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

Title:
  Nextcloud client app indicator icon not visible in 19.10 Eoan Beta

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

Bug description:
  When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its
  app indicator icon is never displayed in the notification area. Other
  apps sch as Steam and Skype have their indicator icons displayed fine.

  Output from the command line when running the flatpak produces the
  following error:

  Qt: Session management error: None of the authentication protocols
  specified are supported

  I can duplicate this issue 100% of the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-appindicator 30-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 13:35:44 2019
  InstallationDate: Installed on 2019-09-23 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago)

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

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

[Desktop-packages] [Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-07 Thread abcdef

So where can one find the desktopManager.js file that would need the
fix? I can't find a single mention online of where system bundled gnome
extensions are located.

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Confirming as I'm seeing this on a machine running 16.04 amd64, fully
up-to-date. According to the owner of that machine, it started happening
fairly recently (in the last few months, trying to get a more accurate
date and I will report here).

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

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

>From comment #2 in duplicate bug #1712991, a user reported that deleting
~/.cache/simple-scan makes the problem go away.

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1330121] Re: simple scan crashes on startup

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

** This bug has been marked a duplicate of bug 1620720
   
/usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

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

Title:
  simple scan crashes on startup

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  Mint 17 + cinnamon 64 bit, up to date levels 1 to 3
  Intel core 2 Duo CPU E8500, 4Gb RAM, ATI Radeon HD 3450 graphics card.
  Cinnamon ver 2.2.13, kernel 3.13.0-24-generic

  When starting simple scan a window is briefly displayed on the screen
  before disapearing, the window should stay open so I can use the
  application.  Happens each time simple scan is run.

  Removing and reinstalling had the same result.

  Worked on the same computer with Mint 14 + cinnamon 64 bit.

  Removing simple scan and installing version 2.31.1 works as expected.

  Thanks to all the developers,
  Tim

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

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

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

2020-12-07 Thread Bartosz Kosiorek

I'm an Simple-scan developer:
https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/simple-scan.doap#L27
Can I have access to these bug reports?

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

2020-12-07 Thread zaf

Hi everyone,
I just had the issue described here : 
https://bugs.launchpad.net/ubuntu/+bug/1901222 with citrix and ended up on this 
page. I added the ppa and updated gnome and it looks like it's working. My IT 
person also did an upgrade of Citrix on the distant machine so I'm not 100% but 
I'm pretty sure the issue was gnome-related.
Thanks for the fix, just a quick question, is there any downside in using your 
ppa Ernst ? (stability issues for instance). Should I remove it when this is 
merged in the main ubuntu repo ?

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

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
  https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Access to errors.ubuntu.com requires a Launchpad account (and I'm not sure if 
an extra permission).
For convenience, I'm attaching the stacktrace here.

** Attachment added: "simple-scan-crash-stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1620720/+attachment/5441656/+files/simple-scan-crash-stacktrace.txt

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

And I'm also copying the relevant parts of the description of bug
#1712991, which is private (not sure why but it's not up to me to decide
whether it should be made public):

===

1. Laptop switched of (no power) after scanning document
2. After restart can not start star simple-scan
simple-scan

(simple-scan:3519): Gtk-WARNING **: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client
Segmentation fault (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: simple-scan 3.25.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 25 09:41:56 2017
ExecutablePath: /usr/bin/simple-scan

===

That plus the comment about deleting the cache makes me think that an
abrupt shutdown (e.g. a power outage) can result in a corrupted cache,
which simple-scan isn't able to gracefully handle.

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1881197] Re: No network usage info presented, always 0 bytes/s.

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: gnome-system-monitor (Ubuntu Focal)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

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

Title:
  No network usage info presented, always 0 bytes/s.

Status in Gnome System Monitor:
  Unknown
Status in gnome-system-monitor package in Ubuntu:
  Fix Released
Status in gnome-system-monitor source package in Focal:
  In Progress

Bug description:
  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04

  2) gnome-system-monitor:
Instalado: 3.36.0-1
Candidato: 3.36.0-1
Tabela de versão:
   *** 3.36.0-1 500
  500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
   3.28.1-1 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) There should be a graph drawn with the info about my network usage,
  as well as number on the download/upload speeds.

  4) Pretty much nothing happens. It calculates how much data I've
  downloaded/uploaded since the OS was booted, but that's it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 17:51:55 2020
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2019-12-06 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions

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

[Desktop-packages] [Bug 1871069] Re: Speed in network history grossly exaggerated

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

** This bug has been marked a duplicate of bug 1881197
   No network usage info presented, always 0 bytes/s.

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

Title:
  Speed in network history grossly exaggerated

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I'm downloading at ~7-8 Mbit/s, and uploading at ~140 kbit/s (reported
  by iftop, connection is limited to about 10 Mbit/s), yet gnome-system-
  monitor shows me 15.6 Mbit/s download and 485 kbit/s upload speed.

  I don't remember seeing this before focal.

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

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

[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

2020-12-07 Thread Ernst Sjöstrand

@zaf Yes, please ppa-purge my ppa when the fix is merged to the ubuntu
main repo.

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

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
  https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

in the current setup without nvidia driver, x11 session works perfectly
with the external monitors.

when I use pop-os, nvidia driver was installed but renoir integrated gpu
or hybrid mode doesnt work at all. but nvidia mode works with x11.

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902244] Please test proposed package

2020-12-07 Thread Łukasz Zemczak

Hello Timo, or anyone else affected,

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

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

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

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

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

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

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

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

[Desktop-packages] [Bug 1907114] [NEW] Audio popping at low volumes

2020-12-07 Thread Dustin Nisbet-Jones

Public bug reported:

My AMD Renoir-powered machine has audio popping at low volumes and when
sound stops briefly.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  dustin15118 F pulseaudio
 /dev/snd/controlC1:  dustin15118 F pulseaudio
 /dev/snd/controlC2:  dustin15118 F pulseaudio
 /dev/snd/controlC0:  dustin15118 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  7 07:47:38 2020
InstallationDate: Installed on 2020-07-15 (144 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2020
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Kona_RN
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.4
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-42
dmi.product.sku: 
dmi.product.version: V1.04
dmi.sys.vendor: Acer
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370

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


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

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

Title:
  Audio popping at low volumes

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My AMD Renoir-powered machine has audio popping at low volumes and
  when sound stops briefly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  Uname: Linux 5.8.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dustin15118 F pulseaudio
   /dev/snd/controlC1:  dustin15118 F pulseaudio
   /dev/snd/controlC2:  dustin15118 F pulseaudio
   /dev/snd/controlC0:  dustin15118 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 07:47:38 2020
  InstallationDate: Installed on 2020-07-15 (144 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370

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

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

https://forum.manjaro.org/t/desktop-environment-with-nvidia-and-wayland-
support/35485/2

based on this thread, I am trying to stay away from kernel 5.9 and
nvidia driver.

Since x11 session works perfectly with ryzen renoir gpu, nvidia driver
isnt really needed for the gpu to access external monitors.

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

I have also tried the latest kernel 5.9, the external monitors still
dont work but the flickering isnt as bad.

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

2020-12-07 Thread Brian Murray

On Mon, Dec 07, 2020 at 02:03:43PM -, Bartosz Kosiorek wrote:
> I'm an Simple-scan developer:
> https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/simple-scan.doap#L27
> Can I have access to these bug reports?

You an request access to crash reports in the Ubuntu Error Tracker via
the following link:

https://forms.canonical.com/reports/

--
Brian Murray

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1902244] Autopkgtest regression report (mesa/20.2.1-1~ubuntu0.20.04.1)

2020-12-07 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted mesa (20.2.1-1~ubuntu0.20.04.1) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

wlroots/0.10.0-2 (amd64, s390x, arm64, armhf)


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

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

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

Thank you!

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

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

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

[Desktop-packages] [Bug 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

2020-12-07 Thread Amr Ibrahim

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

Status in ATK:
  Unknown
Status in atk1.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  == Test Case ==
  1. Boot to ubiquity-dm
  2. Enable the screenreader (Alt+Super+S)
  3. Select "Install Ubuntu"
  4. Proceed with all the steps of the installer

  = Actual Result = 
  During installation, when the slideshow is running, this crash occurs.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:55:58 2020
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1585729537
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcCwd: /
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7fbd15f8f16a :   
mov%rax,-0x20(%rsp)
   PC (0x7fbd15f8f16a) ok
   source "%rax" ok
   destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
  Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  separator:

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

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

[Desktop-packages] [Bug 1907121] [NEW] simple-scan unable to connect scanner HP 2630

Public bug reported:

simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
corrado@corrado-x4-focal:~$ scanimage -L
device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
corrado@corrado-x4-focal:~$ apt policy simple-scan
simple-scan:
  Installed: 3.36.3-0ubuntu0.20.04.0
  Candidate: 3.36.3-0ubuntu0.20.04.0
  Version table:
 *** 3.36.3-0ubuntu0.20.04.0 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.36.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
corrado@corrado-x4-focal:~$ inxi -Fx
System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
   Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
   date: 05/11/2017 
CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
   Speed: 801 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 
   Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
   bus ID: 00:1f.3 
   Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-2:3 
   Sound Server: ALSA v: k5.4.0-56-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
   IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) 
   ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
   ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
   ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: 
/dev/nvme0n1p4 
   ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 27.0 C mobo: 31.0 C 
   Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 
fan-6: 0 
   Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 
Info:  Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
   Shell: bash v: 5.0.17 inxi: 3.0.38 
corrado@corrado-x4-focal:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: simple-scan 3.36.3-0ubuntu0.20.04.0
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  7 17:16:02 2020
ExecutablePath: /usr/bin/simple-scan
InstallationDate: Installed on 2020-04-29 (222 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash
SimpleScanLog:
 
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-12-07 17-27-15.png"
   
https://bugs.launchpad.net/bugs/1907121/+attachment/5441706/+files/Screenshot%20from%202020-12-07%2017-27-15.png

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

[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630

2020-12-07 Thread Bartosz Kosiorek

Please try to run application in debug mode, and attach the logs:

 $ simple-scan -d


Please try to build the latest version according to instruction:

  https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/README.md
#building-from-source

and check if the issue is existing in latest version.

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

Title:
  simple-scan unable to connect scanner HP 2630

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
  corrado@corrado-x4-focal:~$ scanimage -L
  device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
  corrado@corrado-x4-focal:~$ apt policy simple-scan
  simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
   *** 3.36.3-0ubuntu0.20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  corrado@corrado-x4-focal:~$ inxi -Fx
  System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 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 
 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-2:3 
 Sound Server: ALSA v: k5.4.0-56-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: 
/dev/nvme0n1p4 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 27.0 C mobo: 31.0 C 
 Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 
0 fan-6: 0 
 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 
  Info:  Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
 Shell: bash v: 5.0.17 inxi: 3.0.38 
  corrado@corrado-x4-focal:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.3-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 17:16:02 2020
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2020-04-29 (222 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH1

[Desktop-packages] [Bug 1620720] Re: /usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

I don't have physical access to the machine I was mentioning in comment
#1, but I had the owner delete the cache, and the crash went away, so
this confirms my suspicion that simple-scan isn't able to gracefully
handle a corrupted cache.

That user also confirmed that the problem first happened after a power
outage resulted in an abrupt shutdown while they were using simple-scan
to scan documents.

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

Title:
  /usr/bin/simple-
  
scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding simple-scan.  This problem was most recently seen with
  version 3.20.0-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e
  contains more details.

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

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

[Desktop-packages] [Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-07 Thread Sebastien Bacher

Thanks Brian, the fix makes sense!

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

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

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

Title:
  diagnostics panel can leave automatic crash reporting enabled

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  New

Bug description:
  * Impact

  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not
  removed but the panel continues to show "Never".

  * Test case

  - change the automatic report option in settings to automatic and then
  to never, the /var/lib/apport/autoreport file should be removed

  * Regression potential

  The patch modifies the whoopsie configuration, check that the service
  status is right for the 3 auto/manual/never options

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

2020-12-07 Thread Sebastien Bacher

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

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

** Description changed:

+ * Impact
+ 
  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not removed
  but the panel continues to show "Never".
+ 
+ * Test case
+ 
+ - change the automatic report option in settings to automatic and then
+ to never, the /var/lib/apport/autoreport file should be removed
+ 
+ * Regression potential
+ 
+ The patch modifies the whoopsie configuration, check that the service
+ status is right for the 3 auto/manual/never options
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-control-center
  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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1906877

Title:
  diagnostics panel can leave automatic crash reporting enabled

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  New

Bug description:
  * Impact

  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not
  removed but the panel continues to show "Never".

  * Test case

  - change the automatic report option in settings to automatic and then
  to never, the /var/lib/apport/autoreport file should be removed

  * Regression potential

  The patch modifies the whoopsie configuration, check that the service
  status is right for the 3 auto/manual/never options

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1881197] Re: No network usage info presented, always 0 bytes/s.

I uploaded 3.36.1-0ubuntu0.20.04.1 to the focal queue, it's now in the
hands of the SRU team.

** Description changed:

+ [Impact]
+ 
+  * gnome-system-monitor 3.36.1 is the latest minor update in the 3.36
+ series
+ 
+  * it fixes one bug (https://gitlab.gnome.org/GNOME/gnome-system-
+ monitor/-/issues/142), and includes translation updates for a few
+ languages, but these won't impact the package in Ubuntu because it uses
+ the gnome language packs
+ 
+ [Test Case]
+ 
+  * In gnome-system-monitor's preferences window, in the resources tab, set 
the update interval to 0.5 seconds
+  * Open the resources tab and watch the network traffic graph while 
generating incoming and outgoing traffic (for example by running speedtest-cli)
+  * Expected result: outgoing and incoming traffic on the graph is consistent 
with the actual traffic
+  * Actual result without the bugfix in 3.36.1: the graph shows null outgoing 
and incoming traffic, even though the totals seem to be updated in the labels 
below the graph
+ 
+ [Where problems could occur]
+ 
+  * Given the one and only code change in this update is a one-liner that
+ adds a cast to double (https://gitlab.gnome.org/GNOME/gnome-system-
+ monitor/-/commit/3e916c4ee21cede8465e9378fa07e9a71a472c2f), regression
+ potential seems fairly limited. Looking at the code in more details, the
+ change is in a function that is used only to draw the network traffic
+ graph, it's not common code used to draw other graphs. So verifying that
+ the bug is indeed fixed should be enough to be confident there are no
+ regressions. Testing should be carried out with various values for the
+ update interval, both integers and non-integers.
+ 
+  * As mentioned in the impact section, this update includes translation
+ updates, but those shouldn't apply because translations for gnome-
+ system-monitor are shipped externally as part of the language-pack-
+ gnome-*-base packages
+ 
+ [Original description]
+ 
  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04
  
  2) gnome-system-monitor:
-   Instalado: 3.36.0-1
-   Candidato: 3.36.0-1
-   Tabela de versão:
-  *** 3.36.0-1 500
- 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
-  3.28.1-1 500
- 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Instalado: 3.36.0-1
+   Candidato: 3.36.0-1
+   Tabela de versão:
+  *** 3.36.0-1 500
+ 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  3.28.1-1 500
+ 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  3) There should be a graph drawn with the info about my network usage,
  as well as number on the download/upload speeds.
  
  4) Pretty much nothing happens. It calculates how much data I've
  downloaded/uploaded since the OS was booted, but that's it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-system-monitor 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 17:51:55 2020
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2019-12-06 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago)

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

Title:
  No network usage info presented, always 0 bytes/s.

Status in Gnome System Monitor:
  Unknown
Status in gnome-system-monitor package in Ubuntu:
  Fix Released
Status in gnome-system-monitor source package in Focal:
  In Progress

Bug description:
  [Impact]

   * gnome-system-monitor 3.36.1 is the latest minor update in the 3.36
  series

   * it fixes one bug (https://gitlab.gnome.org/GNOME/gnome-system-
  monitor/-/issues/142), and includes translation updates for a few
  languages, but these won't impact the package in Ubuntu because it
  uses the gnome language packs

  [Test Case]

   * In gnome-system-monitor's preferences window, in the resources tab, set 
the update interval to 0.5 seconds
   * Open the resources tab and watch the network traffic graph while 
generating incoming and outgoing traffic (for example by running speedtest-cli)
   * Expected result: outgoing and incoming traffic on the graph is consistent 
with the actual traffic
   * Actual result without the bugfix in 3.36.1: the graph shows null outgoing

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

2020-12-07 Thread albertvaka

I'm still affected by this. Only happens in one computer, a rather slow
one with a spinning hard drive. Is there a fix/workaround?

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

Title:
  Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

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

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

2020-12-07 Thread albertvaka

Icons are missing most times for me. Logging out and back in always
fixes it, as well as Alt+F2 -> 'r', but it's annoying. It might be a
race condition since it seems to only happen on slow computers and on
first boot (when the computer is under load, which makes it slower).

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

Title:
Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
In Progress

Bug description:
OS: Ubuntu 20.04
GNOME: 3.36.2
Extension: 3.36.2

Sometimes, some icons in my Desktop folder just don't appear on the
desktop. The missing icons aren't invisible, it's like they're not in
the folder. Clicking on the empty space where they should be does
nothing. Mousing over the empty space does nothing. See attached
screenshot. As you can see, there are many missing.

Not consistently reproducible, but frequent.

This isn't great info, I know. Let me know what else I can provide.

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

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

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

2020-12-07 Thread Sergio Costas

Can you try this patch? https://gitlab.gnome.org/World/ShellExtensions
/desktop-icons/-/merge_requests/184

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

Title:
  Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

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

[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630

Same problem on Ubuntu 21.04 with a new version:

corrado@corrado-x7-hh-1201:~$ apt policy simple-scan
simple-scan:
  Installed: 3.38.1-1
  Candidate: 3.38.1-1
  Version table:
 *** 3.38.1-1 500
500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-x7-hh-1201:~$ simple-scan -d
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=9389
[+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
[+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
[+0,03s] DEBUG: app-window.vala:1990: Loading state from 
/home/corrado/.cache/simple-scan/state
[+0,03s] DEBUG: app-window.vala:1969: Restoring window to 600x400 pixels
[+0,07s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,07s] DEBUG: scanner.vala:1554: SANE version 1.0.31
[+0,07s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,07s] DEBUG: scanner.vala:828: Processing request
[+0,44s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state
[+7,72s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,72s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:60001"; 
vendor="HP" model="DeskJet 2600 series [665032] (USB 1)" type="flatbed scanner"
[+7,72s] DEBUG: scanner.vala:353: Device: 
name="hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS" 
vendor="Hewlett-Packard" model="DeskJet_2600_series" type="all-in-one"
[+8,03s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state
[+10,96s] DEBUG: simple-scan.vala:1817: Requesting scan at 300 dpi from device 
'hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS'
[+10,96s] DEBUG: scanner.vala:1683: Scanner.scan 
("hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS", dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, paper_height=0, 
brightness=0, contrast=0, delay=3000ms)
[+10,96s] DEBUG: scanner.vala:828: Processing request
[+11,00s] DEBUG: scanner.vala:889: sane_open 
("hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS") -> SANE_STATUS_IO_ERROR
[+11,00s] WARNING: scanner.vala:893: Unable to open device: Error during device 
I/O
[+11,25s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state
[+11,76s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state
[+214,30s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state
[+217,01s] DEBUG: app-window.vala:2065: Saving state to 
/home/corrado/.cache/simple-scan/state


/home/corrado/.cache/simple-scan/state

[window]
width=600
height=400
is-maximized=false
is-fullscreen=false

[scanner]
scan-type=single

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

Title:
  simple-scan unable to connect scanner HP 2630

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
  corrado@corrado-x4-focal:~$ scanimage -L
  device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
  corrado@corrado-x4-focal:~$ apt policy simple-scan
  simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
   *** 3.36.3-0ubuntu0.20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  corrado@corrado-x4-focal:~$ inxi -Fx
  System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 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 
 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driv

[Desktop-packages] [Bug 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded

2020-12-07 Thread Gregor Jasny

Hi,

the issue is the same as in LP #1903966. The following commit should fix
it also for the 1.18 version:

https://salsa.debian.org/debian/libv4l/-/commit/e12bd27aa844663601d81c99ecbdff33c9b5e9f3


Until the version in focal is fixed, you could use the v4l-utils-stable PPA: 

  https://code.launchpad.net/~libv4l/+archive/ubuntu/stable

The (pending) Build recipe is here:
https://code.launchpad.net/~libv4l/+recipe/v4l-utils-stable-1.20

Thanks,
Gregor

** Changed in: v4l-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

Status in v4l-utils package in Ubuntu:
  Confirmed

Bug description:
  ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-
  keytable.rules containing the following rule:

  ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
  /etc/rc_maps.cfg -s $name"

  After upgrading to Focal, this does not get triggered at boot, nor if
  I (re)insert my receiver when the system is running. Therefore, the
  custom keytable does not get loaded.

  This is the udev events that occur when I insert the receiver:

  $ sudo udevadm monitor
  monitor will print the received events for:
  UDEV - the event which udev sends out after rule processing
  KERNEL - the kernel uevent

  KERNEL[1195.829011] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  KERNEL[1195.834989] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1195.874055] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  KERNEL[1195.875019] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  KERNEL[1195.875183] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  KERNEL[1196.134164] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  KERNEL[1196.134448] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.158923] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.174559] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.194750] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  UDEV  [1196.196268] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  UDEV  [1196.197180] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  UDEV  [1196.224577] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  UDEV  [1196.231346] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)

  Note how there's no «(rc)» displayed on any of the lines, which means
  that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
  the above events.

  I found a rule that works at https://www.mail-archive.com/linux-
  me...@vger.kernel.org/msg117165.html:

  ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
  ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg
  -s $env{.rc_sysdev}"

  Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file
  containing this rule solves the problem; now my custom keymap is
  loaded at boot, as it did before (when I was running Bionic).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec  6 18:05:06 2020
  SourcePackage: v4l-utils
  UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630

Note: I have a similar(?) problem with xsane: 
https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1907113

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

Title:
  simple-scan unable to connect scanner HP 2630

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
  corrado@corrado-x4-focal:~$ scanimage -L
  device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
  corrado@corrado-x4-focal:~$ apt policy simple-scan
  simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
   *** 3.36.3-0ubuntu0.20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  corrado@corrado-x4-focal:~$ inxi -Fx
  System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 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 
 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-2:3 
 Sound Server: ALSA v: k5.4.0-56-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: 
/dev/nvme0n1p4 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 27.0 C mobo: 31.0 C 
 Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 
0 fan-6: 0 
 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 
  Info:  Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
 Shell: bash v: 5.0.17 inxi: 3.0.38 
  corrado@corrado-x4-focal:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.3-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 17:16:02 2020
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2020-04-29 (222 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M

[Desktop-packages] [Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions

2020-12-07 Thread buchs

I can also confirm the work around via @Gunnar's PPA also fixes this
problem for me: https://askubuntu.com/questions/1294774/swapping-
control-and-caps-lock-on-dell-xps-on-20-04-used-to-work-with-gnome-tw .
Thanks, people!

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

Title:
  Input device settings not applied on hotplug/reconnect/resume in Xorg
  sessions

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
  seems to have been introduced within the past couple of weeks. I have
  a couple custom keyboard settings configured in Tweaktool "Additional
  Layout Options". These settings work great.

  I have a USB keyboard plugged into the machine. If I have the keyboard
  plugged in when I start my Gnome session, the customized keyboard
  layout options are correctly applied to the USB keyboard. If I unplug
  and reconnect the keyboard, the keyboard does will _NOT_ have the
  customized keyboard settings.

  If I restart my Gnome session (using Alt-F2 -> "r"), the customized
  settings are applied to the keyboard.

  I think this behavior is something new. Before, I was able to
  unplug/reconnect my keyboard and it would apply my customized keyboard
  settings on reconnect. Is there anything I can do to force the
  application of the custom keyboard tweaks on USB keyboard reconnect?

  Is anyone else able to reproduce this? I don't have any other machines
  with Ubuntu 20.04.1 to test with.

  Thanks!

  (This is also cross-posted at askubuntu:
  https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
  layout-options-not-working)

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

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

[Desktop-packages] [Bug 1907142] [NEW] Rather regular crashes, about twice per day

2020-12-07 Thread udippel

Public bug reported:

Since my upgrade from 18.04 to 20.04 I experience rather frequent
crashes of the X server. Nothing specific of applications running,
presumably at videos (VLC, Youtube in a browser tab ...).

If not yet attached, I'll attach the *.old log with the most recent
trace.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Dec  7 22:15:34 2020
DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
InstallationDate: Installed on 2019-02-16 (660 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: LENOVO 20CHS10P02
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ETB2W (2.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CHS10P02
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
dmi.product.family: ThinkPad Helix 2nd
dmi.product.name: 20CHS10P02
dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
dmi.product.version: ThinkPad Helix 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Rather regular crashes, about twice per day

Status in xorg package in Ubuntu:
  New

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnL

[Desktop-packages] [Bug 1907154] [NEW] application menu of pdf and text documents is not visible when the window is resized and made smaller

2020-12-07 Thread Vincenzo Tamborino Frisari

Public bug reported:

1. When opening a text document (with standard text editor) or a pdf with "Pdf 
viewer" and clicking on the "menu" icon at the top right of the window, the 
menu shows up correctly. 
2.If I resize the window making it shorter than the menu itself, I would expect 
the menu to remain fully visible or at least in some way graphically accessible 
(resized or scrollable).
3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  7 23:33:35 2020
DistUpgraded: 2020-12-01 09:42:59,803 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:
 btusb, 4.0, 5.4.0-54-generic, x86_64: installed
 btusb, 4.0, 5.4.0-56-generic, x86_64: installed
 digimend, 10, 5.4.0-54-generic, x86_64: installed
 digimend, 10, 5.4.0-56-generic, x86_64: installed
 rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
InstallationDate: Installed on 2020-03-23 (259 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: TOSHIBA SATELLITE L750D
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
dmi.bios.date: 11/23/2011
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.50
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Torpedo
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE L750D
dmi.product.sku: PSK36E-05P00LIT
dmi.product.version: PSK36E-05P00LIT
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  application menu of pdf and text documents is not visible when the
  window is resized and made smaller

Status in xorg package in Ubuntu:
  New

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  Distr

[Desktop-packages] [Bug 1878547] Re: "Quit %d Windows" not localized to non-English

** Tags added: rls-ff-incoming

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute)
   Importance: Low
   Status: Fix Released

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

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

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

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

Title:
  "Quit %d Windows" not localized to non-English

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Hirsute:
  Fix Released

Bug description:
  If I have more than 1 application windows open, the 'quit 2 windows' command 
is not localized (not in italian at least).
  See attachemnt

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 09:01:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-08 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1878547/+subscriptions

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

[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

Thanks for providing people with the PPA, Ernst. Only one suggestion is
that next time use the version prefix of the old version, not the future
version. So then when an official update is available with a higher
version number people would get it automatically.

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

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
  https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

Please:

1. Stick with the supported Ubuntu kernel 5.8.

2. Open the Additional Drivers app and install the official Nvidia
driver.

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1907142] Re: Rather regular crashes, about twice per day

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

Looks like the issue is:

[ 15285.452] (EE) Backtrace:
[ 15285.453] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55b0f2a4952c]
[ 15285.455] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f1c35a1241f]
[ 15285.458] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f1c3584f18b]
[ 15285.462] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7f1c3582e859]
[ 15285.465] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.465] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) 
[0x7f1c33a4d3a9]
[ 15285.466] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(nouveau_drm_screen_create+0x2038c7) [0x7f1c346405f7]
[ 15285.468] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x24f35) [0x7f1c33a9d6a5]
[ 15285.470] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x24fa4) [0x7f1c33a9d7a4]
[ 15285.472] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.472] (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f1c36368c90]
[ 15285.474] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.474] (EE) 9: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f1c3636b8f0]
[ 15285.474] (EE) 10: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x55b0f28ec995]
[ 15285.475] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x122) 
[0x55b0f2a42ba2]
[ 15285.475] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) 
[0x55b0f28e7cf7]
[ 15285.476] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55b0f28ebfc4]
[ 15285.479] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f1c358300b3]
[ 15285.479] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2e) [0x55b0f28d5a2e]

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

Title:
  Rather regular crashes, about twice per day

Status in xorg package in Ubuntu:
  New

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907142/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1907114] Re: [Acer Swift 3 SF314-42] Audio popping at low volumes

Can you please attach a copy of your /etc/pulse/default.pa ?

** Summary changed:

- Audio popping at low volumes
+ [Acer Swift 3 SF314-42] Audio popping at low volumes

** Also affects: alsa-lib (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: alsa-lib (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Acer Swift 3 SF314-42] Audio popping at low volumes

Status in alsa-lib package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My AMD Renoir-powered machine has audio popping at low volumes and
  when sound stops briefly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  Uname: Linux 5.8.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dustin15118 F pulseaudio
   /dev/snd/controlC1:  dustin15118 F pulseaudio
   /dev/snd/controlC2:  dustin15118 F pulseaudio
   /dev/snd/controlC0:  dustin15118 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 07:47:38 2020
  InstallationDate: Installed on 2020-07-15 (144 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370

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

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

[Desktop-packages] [Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

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

Thanks for that. It confirms this is a duplicate of bug 1898005.

** This bug has been marked a duplicate of bug 1898005
   gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: 
(priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1907142] Re: Rather regular crashes, about twice per day

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

This appears to be the same as bug 1906642.

** This bug has been marked a duplicate of bug 1906642
   Xorg crashes with abort in iris_dri.so

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

Title:
  Rather regular crashes, about twice per day

Status in xorg package in Ubuntu:
  New

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907142/+subscriptions

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

[Desktop-packages] [Bug 1906642] Re: Xorg crashes with abort in iris_dri.so

Also seen with Mesa 20.0.8-0ubuntu1~20.04.1 (bug 1907142)

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

Title:
  Xorg crashes with abort in iris_dri.so

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  System is crashing, logging out and i am constantly losing all my work
  if it's not saved

  Description:  Ubuntu 20.04 LTS (fossa-beric-icl X31)
  Release:  20.04

  N: Unable to locate package pkgname

  I expect not to happen (crash->log out)

  Instead, it happened

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
  Uname: Linux 5.6.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 12:33:11 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a2a]
  InstallationDate: Installed on 2020-09-19 (74 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 3501
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem 
root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.name: 01D26F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3501
  dmi.product.sku: 0A2A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/mesa/+bug/1906642/+subscriptions

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

[Desktop-packages] [Bug 1907154] Re: Application menu of GTK apps is not visible when the window is resized and made smaller

** Summary changed:

- application menu of pdf and text documents is not visible when the window is 
resized and made smaller
+ Application menu of GTK apps is not visible when the window is resized and 
made smaller

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

Title:
  Application menu of GTK apps is not visible when the window is resized
  and made smaller

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 23:33:35 2020
  DistUpgraded: 2020-12-01 09:42:59,803 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:
   btusb, 4.0, 5.4.0-54-generic, x86_64: installed
   btusb, 4.0, 5.4.0-56-generic, x86_64: installed
   digimend, 10, 5.4.0-54-generic, x86_64: installed
   digimend, 10, 5.4.0-56-generic, x86_64: installed
   rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
  InstallationDate: Installed on 2020-03-23 (259 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE L750D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
  dmi.bios.date: 11/23/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Torpedo
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L750D
  dmi.product.sku: PSK36E-05P00LIT
  dmi.product.version: PSK36E-05P00LIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/gtk+3.0/+bug/1907154/+subscriptions

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

[Desktop-packages] [Bug 1907154] Re: Application menu of GTK apps is not visible when the window is resized and made smaller

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

** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu)

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

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

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

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

Title:
  Application menu of GTK apps is not visible when the window is resized
  and made smaller

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 23:33:35 2020
  DistUpgraded: 2020-12-01 09:42:59,803 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:
   btusb, 4.0, 5.4.0-54-generic, x86_64: installed
   btusb, 4.0, 5.4.0-56-generic, x86_64: installed
   digimend, 10, 5.4.0-54-generic, x86_64: installed
   digimend, 10, 5.4.0-56-generic, x86_64: installed
   rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
  InstallationDate: Installed on 2020-03-23 (259 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE L750D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
  dmi.bios.date: 11/23/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Torpedo
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L750D
  dmi.product.sku: PSK36E-05P00LIT
  dmi.product.version: PSK36E-05P00LIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/gtk+3.0/+bug/1907154/+subscriptions

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

[Desktop-packages] [Bug 1907154] Re: Application menu of GTK apps is not visible when the window is resized and made smaller

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

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

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

Title:
  Application menu of GTK apps is not visible when the window is resized
  and made smaller

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 23:33:35 2020
  DistUpgraded: 2020-12-01 09:42:59,803 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:
   btusb, 4.0, 5.4.0-54-generic, x86_64: installed
   btusb, 4.0, 5.4.0-56-generic, x86_64: installed
   digimend, 10, 5.4.0-54-generic, x86_64: installed
   digimend, 10, 5.4.0-56-generic, x86_64: installed
   rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
  InstallationDate: Installed on 2020-03-23 (259 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE L750D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
  dmi.bios.date: 11/23/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Torpedo
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L750D
  dmi.product.sku: PSK36E-05P00LIT
  dmi.product.version: PSK36E-05P00LIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/gtk+3.0/+bug/1907154/+subscriptions

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

[Desktop-packages] [Bug 1907154] Re: Application menu of GTK apps is cut off when the window is resized and made smaller

** Summary changed:

- Application menu of GTK apps is not visible when the window is resized and 
made smaller
+ Application menu of GTK apps is cut off when the window is resized and made 
smaller

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

Title:
  Application menu of GTK apps is cut off when the window is resized and
  made smaller

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 23:33:35 2020
  DistUpgraded: 2020-12-01 09:42:59,803 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:
   btusb, 4.0, 5.4.0-54-generic, x86_64: installed
   btusb, 4.0, 5.4.0-56-generic, x86_64: installed
   digimend, 10, 5.4.0-54-generic, x86_64: installed
   digimend, 10, 5.4.0-56-generic, x86_64: installed
   rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
  InstallationDate: Installed on 2020-03-23 (259 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE L750D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
  dmi.bios.date: 11/23/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Torpedo
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L750D
  dmi.product.sku: PSK36E-05P00LIT
  dmi.product.version: PSK36E-05P00LIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/gtk+3.0/+bug/1907154/+subscriptions

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

[Desktop-packages] [Bug 1907114] Re: [Acer Swift 3 SF314-42] Audio popping at low volumes

2020-12-07 Thread Dustin Nisbet-Jones

Thank you for the response. See attached

** Attachment added: "default.pa"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1907114/+attachment/5441830/+files/default.pa

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

Title:
  [Acer Swift 3 SF314-42] Audio popping at low volumes

Status in alsa-lib package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My AMD Renoir-powered machine has audio popping at low volumes and
  when sound stops briefly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  Uname: Linux 5.8.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dustin15118 F pulseaudio
   /dev/snd/controlC1:  dustin15118 F pulseaudio
   /dev/snd/controlC2:  dustin15118 F pulseaudio
   /dev/snd/controlC0:  dustin15118 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 07:47:38 2020
  InstallationDate: Installed on 2020-07-15 (144 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370

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

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

[Desktop-packages] [Bug 1907154] Re: Application menu of GTK apps is cut off when the window is resized and made smaller

It appears the problem only happens in Xorg sessions, not Wayland
sessions. And it happens with a bare Xorg server too, so it's not
mutter/shell bug.

** No longer affects: mutter (Ubuntu)

** Summary changed:

- Application menu of GTK apps is cut off when the window is resized and made 
smaller
+ Application menu of GTK apps is cut off when the window is resized and made 
smaller in Xorg sessions

** Changed in: gtk+3.0 (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/1907154

Title:
  Application menu of GTK apps is cut off when the window is resized and
  made smaller in Xorg sessions

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  1. When opening a text document (with standard text editor) or a pdf with 
"Pdf viewer" and clicking on the "menu" icon at the top right of the window, 
the menu shows up correctly. 
  2.If I resize the window making it shorter than the menu itself, I would 
expect the menu to remain fully visible or at least in some way graphically 
accessible (resized or scrollable).
  3. Instead, I can no more see some options of the menu: a part of it is not 
visible (as it was graphically cut). So you can't see nor select with the mouse 
the non-visible part of the menu.
  4. I noticed you can navigate and select the options (both visible or 
non-visible) of the menu using arrows and Enter from the keyboard. However this 
is not a solution because you still cannot see a part of the menu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 23:33:35 2020
  DistUpgraded: 2020-12-01 09:42:59,803 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:
   btusb, 4.0, 5.4.0-54-generic, x86_64: installed
   btusb, 4.0, 5.4.0-56-generic, x86_64: installed
   digimend, 10, 5.4.0-54-generic, x86_64: installed
   digimend, 10, 5.4.0-56-generic, x86_64: installed
   rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52]
  InstallationDate: Installed on 2020-03-23 (259 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE L750D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago)
  dmi.bios.date: 11/23/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Torpedo
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L750D
  dmi.product.sku: PSK36E-05P00LIT
  dmi.product.version: PSK36E-05P00LIT
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/gtk+3.0/+bug/1907154/+subscriptions

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

[Desktop-packages] [Bug 1907114] Re: [Acer Swift 3 SF314-42] Audio popping at low volumes

Thanks. I just wanted to check the changes made in that file, which turn
out to be irrelevant:

-#load-module module-alsa-source device=hw:1,0
+#load-module module-alsa-source device=hw:0,0


** Changed in: alsa-lib (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [Acer Swift 3 SF314-42] Audio popping at low volumes

Status in alsa-lib package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My AMD Renoir-powered machine has audio popping at low volumes and
  when sound stops briefly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  Uname: Linux 5.8.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dustin15118 F pulseaudio
   /dev/snd/controlC1:  dustin15118 F pulseaudio
   /dev/snd/controlC2:  dustin15118 F pulseaudio
   /dev/snd/controlC0:  dustin15118 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 07:47:38 2020
  InstallationDate: Installed on 2020-07-15 (144 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370

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

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

[Desktop-packages] [Bug 1900454]

2020-12-07 Thread Ming-v-hua

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

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

Title:
  Calc doesn't recalculate formulas on cell content changes

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

Bug description:
  libreoffice-calc 1:7.0.2-0ubuntu1 (Groovy)

  The problem is better explained via steps to reproduce:

  1. Start calc; you'll get a new spreadsheet.
  2. Fill in the following in cells A1-A3:

A1: 1
A2: =A1+1
A3: =A1-1

  As expected: A2 is calculated as 2, A3 is calculated as 0.

  3. Change A1 to 2 and press enter.

  A2 is autocalculated to 3, but A3 remains at 0 (wrong!).

  Now for the fun part: switch to a different application so LibreOffice
  window loses focus, the put it back in focus. A3 is now recalculated
  to 1.

  (Partially taken from:
  https://ask.libreoffice.org/en/question/271324/calc-v7022-cell-
  autocalculate-not-working-while-window-has-focus/)

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

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

[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

This bug was fixed in the package gnome-shell-extension-desktop-icons -
20.04.0+git20200908-5

---
gnome-shell-extension-desktop-icons (20.04.0+git20200908-5) unstable; 
urgency=medium

  [ Daniel van Vugt ]
  * Add fix-lp1898462.patch to fix broken drag-and-drop (LP: #1898462)

  [ Iain Lane ]
  * Rename fix-*.patch to more descriptive names following their commit
subjects

 -- Iain Lane   Mon, 07 Dec 2020 18:16:04 +

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

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

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

Bug description:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell in Ubuntu 20.10 (beta).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

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

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

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

This bug was fixed in the package gnome-shell-extension-desktop-icons -
20.04.0+git20200908-5

---
gnome-shell-extension-desktop-icons (20.04.0+git20200908-5) unstable; 
urgency=medium

  [ Daniel van Vugt ]
  * Add fix-lp1898462.patch to fix broken drag-and-drop (LP: #1898462)

  [ Iain Lane ]
  * Rename fix-*.patch to more descriptive names following their commit
subjects

 -- Iain Lane   Mon, 07 Dec 2020 18:16:04 +

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

-- 
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()

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

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

  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 1899011] Re: Multiple maintainer

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

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

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

Title:
  Multiple maintainer

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

Bug description:
  https://packages.ubuntu.com/bionic/gnome/gnome-shell-extension-
  dashtodock

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

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

[Desktop-packages] [Bug 1891305] Re: evince annotate

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

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

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

Title:
  evince annotate

Status in evince package in Ubuntu:
  Expired

Bug description:
  enhancement request:

  transparency should effect colour not text
  currently both text and highlight are effected.

  evince 3.18.2

  Gallium 16.04 xenial uptodate on Chromebook

  shall update to Gallium 3.0

  please confirm

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

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

[Desktop-packages] [Bug 1877428] Re: Graphical glitches

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

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

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

Title:
  Graphical glitches

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  On a newly upgraded Ubuntu 20.04 on a Lenovo Yoga 370, the Gnome
  background screen is constellated with graphical glitches. Icons on
  the taskbar are affected too but not the inner part of the windows.

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

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

[Desktop-packages] [Bug 1898849] Re: Ubuntu Mate freezes when I run Facebook on Firefox

[Expired for Ubuntu MATE because there has been no activity for 60
days.]

** Changed in: ubuntu-mate
   Status: Incomplete => Expired

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

Title:
  Ubuntu Mate freezes when I run Facebook on Firefox

Status in Ubuntu MATE:
  Expired
Status in firefox package in Ubuntu:
  Expired

Bug description:
  Running Facebook normally in Firefox or Chrome the computer slows and
  freezes.  Mouse still moves but the system will not accept clicks or
  keyboard in put.

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

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

[Desktop-packages] [Bug 1898849] Re: Ubuntu Mate freezes when I run Facebook on Firefox

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

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

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

Title:
  Ubuntu Mate freezes when I run Facebook on Firefox

Status in Ubuntu MATE:
  Expired
Status in firefox package in Ubuntu:
  Expired

Bug description:
  Running Facebook normally in Firefox or Chrome the computer slows and
  freezes.  Mouse still moves but the system will not accept clicks or
  keyboard in put.

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

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

[Desktop-packages] [Bug 1539999] Re: Omnikey Cardreader not working

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

** Changed in: pcsc-lite (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Omnikey Cardreader not working

Status in pcsc-lite package in Ubuntu:
  Expired

Bug description:
  On my desktop & sony vaio laptop, Alpha 2 Ubuntu-mate does not start my usb 
Omnikey 3121 card reader.
  The 3121 is listed in terminal when I perform 'lsusb'. The reader does work 
under concurrent devuan 1. I have installed pcscd (which drags in libccid 
correctly) & pcsc-tools but this hasn't corrected the problem even with a 
reboot.

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

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

[Desktop-packages] [Bug 1907190] [NEW] package chromium-browser (not installed) failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do statu

2020-12-07 Thread Evaldo Junior

Public bug reported:

The software Chromium is not install or reinstall for the apt command,
the repository is correct.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
AptOrdering:
 chromium-browser:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Dec  8 00:55:24 2020
ErrorMessage: o subprocesso do pacote chromium-browser, novo script 
pre-installation retornou erro do status de saída 1
InstallationDate: Installed on 2020-12-05 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: chromium-browser
Title: package chromium-browser (not installed) failed to install/upgrade: o 
subprocesso do pacote chromium-browser, novo script pre-installation retornou 
erro do status de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package chromium-browser (not installed) failed to install/upgrade: o
  subprocesso do pacote chromium-browser, novo script pre-installation
  retornou erro do status de saída 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The software Chromium is not install or reinstall for the apt command,
  the repository is correct.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Dec  8 00:55:24 2020
  ErrorMessage: o subprocesso do pacote chromium-browser, novo script 
pre-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-12-05 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: o 
subprocesso do pacote chromium-browser, novo script pre-installation retornou 
erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1907189] [NEW] Xorg freeze when split screen

2020-12-07 Thread Yuchen Liu

Public bug reported:

When I open an application like Firefox, I split them into 2 windows and
place one to the left and place the other to the right. So each window
gets half of the monitor. The right window gets slow when clicking and
lags for 2 seconds. But the left window is normal. This happens to all
applications when I have 2 windows. (When 1 window only, even if I put
it to the right side of the monitor, it still works fine, no lag). Thank
you!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  7 19:33:24 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
 nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2020-06-23 (167 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications 
 Bus 001 Device 002: ID 2f68:0082 Hoksi Technology DURGOD Taurus K320
 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=30757229-adcc-4567-bf22-0a375e36d51d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.20.0
dmi.board.name: 0JHP5H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
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 false-gpu-hang focal freeze 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/1907189

Title:
  Xorg freeze when split screen

Status in xorg package in Ubuntu:
  New

Bug description:
  When I open an application like Firefox, I split them into 2 windows
  and place one to the left and place the other to the right. So each
  window gets half of the monitor. The right window gets slow when
  clicking and lags for 2 seconds. But the left window is normal. This
  happens to all applications when I have 2 windows. (When 1 window
  only, even if I put it to the right side of the monitor, it still
  works fine, no lag). Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 19:33:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1

[Desktop-packages] [Bug 1907189] Re: Apps become unresponsive and lag when multiple windows opened

I can't seem to reproduce any such problem with Firefox. Can you please
list the affected apps and maybe provide a more detailed test case?

Although I am reminded of bug 1906792, it's probably different.

** Summary changed:

- Xorg freeze when split screen
+ Apps become unresponsive and lag when multiple windows opened

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

** Tags added: performance

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

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

Title:
  Apps become unresponsive and lag when multiple windows opened

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I open an application like Firefox, I split them into 2 windows
  and place one to the left and place the other to the right. So each
  window gets half of the monitor. The right window gets slow when
  clicking and lags for 2 seconds. But the left window is normal. This
  happens to all applications when I have 2 windows. (When 1 window
  only, even if I put it to the right side of the monitor, it still
  works fine, no lag). Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 19:33:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2020-06-23 (167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 2f68:0082 Hoksi Technology DURGOD Taurus K320
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=30757229-adcc-4567-bf22-0a375e36d51d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907189/+subscriptions

-- 
Mailing list: https://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 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

By installing nvidia driver, ubuntu will switch back to nvidia gpu and x11
will be used. The point of using wayland is to apply different scaling for
4k external monitor.

On Tue, Dec 8, 2020, 10:00 Daniel van Vugt <1905...@bugs.launchpad.net>
wrote:

> Please:
>
> 1. Stick with the supported Ubuntu kernel 5.8.
>
> 2. Open the Additional Drivers app and install the official Nvidia
> driver.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1905270
>
> Title:
>   [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
>   monitors, wayland session has a white block on most part of the
>   screen.
>
> Status in Mutter:
>   Unknown
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   on any external monitors, wayland session has a white block on most
>   part of the screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: mutter 3.38.1-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
>   Uname: Linux 5.8.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu50.1
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 23 20:16:15 2020
>   InstallationDate: Installed on 2020-09-16 (67 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
>   SourcePackage: mutter
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions
>

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902244] Autopkgtest regression report (mesa/20.2.1-1~ubuntu0.20.04.2)

2020-12-07 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted mesa (20.2.1-1~ubuntu0.20.04.2) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u275-b01-0ubuntu1~20.04 (armhf)
wlroots/0.10.0-2 (amd64, ppc64el, s390x, armhf, arm64)


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

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

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

Thank you!

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

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

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

Sorry, those most recent comments led to me forget that this is about
Wayland. But actually you can use Wayland with the official Nvidia
driver, and it might resolve the bug. You need to make a couple of
tweaks to reveal the Wayland login option after installing the Nvidia
driver:

1. In /etc/default/grub add the kernel parameter:  nvidia-drm.modeset=1

2. Comment out the Nvidia rule that is disabling Wayland in
/usr/lib/udev/rules.d/61-gdm.rules

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1907194] [NEW] /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_finish

2020-12-07 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.20.9-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: focal groovy

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

Title:
  
/usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_finish

Status in xorg-server package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1907194] Re: /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_finish

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

** This bug has been marked a duplicate of bug 1871959
   Xorg crashed with SIGABRT in _iris_batch_flush.cold() from 
iris_fence_flush() from st_glFlush() from dri2_make_current()

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

Title:
  
/usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_finish

Status in xorg-server package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1906642] Re: Xorg crashes with abort in iris_dri.so

The only other similar crash I can find is bug 1871959.

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

Title:
  Xorg crashes with abort in iris_dri.so

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  System is crashing, logging out and i am constantly losing all my work
  if it's not saved

  Description:  Ubuntu 20.04 LTS (fossa-beric-icl X31)
  Release:  20.04

  N: Unable to locate package pkgname

  I expect not to happen (crash->log out)

  Instead, it happened

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
  Uname: Linux 5.6.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 12:33:11 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0a2a]
  InstallationDate: Installed on 2020-09-19 (74 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 3501
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem 
root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.name: 01D26F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3501
  dmi.product.sku: 0A2A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/mesa/+bug/1906642/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()

** Description changed:

  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

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush() from dri2_make_current()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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'
  Distribution

[Desktop-packages] [Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command

Never mind... Just `ubuntu-drivers install` did the trick.. LOL

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

Title:
  `ubuntu-drivers list` output doesn't bear any relation to the input to
  the install command

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  As a user, I would like to decide on one of the drivers available to
  me and then install it.  So I list my options:

  ```
  $ ubuntu-drivers list
  nvidia-driver-410
  nvidia-driver-390
  ```

  Great, I'll install 410:

  ```
  $ ubuntu-drivers install --gpgpu nvidia-driver-410
  No drivers found for installation.
  ```

  This is confusing; I think the `list` output format should be aligned
  with the input format for install.

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

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

[Desktop-packages] [Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command

I totally agree with this!

The Additional Drivers doesn't work if your Netplan uses rendered:
networked.

Then, the command line is useless too... How does it work?

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

Title:
  `ubuntu-drivers list` output doesn't bear any relation to the input to
  the install command

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  As a user, I would like to decide on one of the drivers available to
  me and then install it.  So I list my options:

  ```
  $ ubuntu-drivers list
  nvidia-driver-410
  nvidia-driver-390
  ```

  Great, I'll install 410:

  ```
  $ ubuntu-drivers install --gpgpu nvidia-driver-410
  No drivers found for installation.
  ```

  This is confusing; I think the `list` output format should be aligned
  with the input format for install.

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

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

[Desktop-packages] [Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages

Never mind... Just `ubuntu-drivers install` did the trick.. LOL

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

Title:
  `ubuntu-drivers install --gpgpu` could have more informative error
  messages

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

Bug description:
  It would be good if:

  ```
  $ ubuntu-drivers install --gpgpu amd
  No drivers found for installation.
  ```

  listed the available drivers (if any) and:

  ```
  $ ubuntu-drivers install --gpgpu nvidia:370
  No drivers found for installation.
  ```

  listed the available versions for the nvidia driver.

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

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

[Desktop-packages] [Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  `ubuntu-drivers install --gpgpu` could have more informative error
  messages

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

Bug description:
  It would be good if:

  ```
  $ ubuntu-drivers install --gpgpu amd
  No drivers found for installation.
  ```

  listed the available drivers (if any) and:

  ```
  $ ubuntu-drivers install --gpgpu nvidia:370
  No drivers found for installation.
  ```

  listed the available versions for the nvidia driver.

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

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

[Desktop-packages] [Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages

I totally agree with this!

The Additional Drivers doesn't work if your Netplan uses rendered:
networked.

Then, the command line is useless too... How does it work?

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

Title:
  `ubuntu-drivers install --gpgpu` could have more informative error
  messages

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

Bug description:
  It would be good if:

  ```
  $ ubuntu-drivers install --gpgpu amd
  No drivers found for installation.
  ```

  listed the available drivers (if any) and:

  ```
  $ ubuntu-drivers install --gpgpu nvidia:370
  No drivers found for installation.
  ```

  listed the available versions for the nvidia driver.

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

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

[Desktop-packages] [Bug 1902801] Re: Encrypted attachments cannot be opened or saved as decrypted files

2020-12-07 Thread Bug Watch Updater

** Changed in: archlinux
   Status: Confirmed => Fix Released

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Confirmed
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1902801]

2020-12-07 Thread Kai Engert

(In reply to Magnus Melin [:mkmelin] from comment #15)
> Kai, should we just hide this menu until it's working? Or you you have code 
> pointers to how to fix it?

Looks like I restored the functionality with the attached patch.

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Confirmed
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1902801]

2020-12-07 Thread Kai Engert

Comment on attachment 9191067
Bug 1663169 - Restore decrypt and save/open right click action for attachments. 
r=PatrickBrunschwig

[Approval Request Comment]
Regression caused by (bug #): none
User impact if declined: nonworking decrypt feature that's offered in UI
Testing completed (on c-c, etc.): 
Risk to taking this patch (and alternatives if risky): low

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Confirmed
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1902801]

2020-12-07 Thread Pulsebot

Pushed by k...@kuix.de:
https://hg.mozilla.org/comm-central/rev/b98061eb01ee
Restore decrypt and save/open right click action for attachments. 
r=PatrickBrunschwig DONTBUILD

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Confirmed
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1902801]

2020-12-07 Thread Kai Engert

Created attachment 9191067
Bug 1663169 - Restore decrypt and save/open right click action for attachments. 
r=PatrickBrunschwig

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Confirmed
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1907189] Re: Apps become unresponsive and lag when multiple windows opened

2020-12-07 Thread Yuchen Liu

It's fixed. I have two screens (one monitor on the left and one laptop
display on the right). So the lag of the window on the right side of
monitor was caused by setting laptop display to 125%. When I set the
laptop display to 100%, the right side of the larger monitor no longer
lags.

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

Title:
  Apps become unresponsive and lag when multiple windows opened

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I open an application like Firefox, I split them into 2 windows
  and place one to the left and place the other to the right. So each
  window gets half of the monitor. The right window gets slow when
  clicking and lags for 2 seconds. But the left window is normal. This
  happens to all applications when I have 2 windows. (When 1 window
  only, even if I put it to the right side of the monitor, it still
  works fine, no lag). Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 19:33:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2020-06-23 (167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 2f68:0082 Hoksi Technology DURGOD Taurus K320
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=30757229-adcc-4567-bf22-0a375e36d51d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907189/+subscriptions

-- 
Mailing list: https://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 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

I tried your suggestion and added the nvidia modeset and commented out  the
61 nvidia wayland. Then the system becomes very unstable. For example, the
laptop froze just before the login screen if external monitor are plugged
in. Without the monitors plugged in, if I use wayland, the system will only
use renoir and won't use nvidia gpu at all.

On Tue, Dec 8, 2020, 13:50 Daniel van Vugt <1905...@bugs.launchpad.net>
wrote:

> Sorry, those most recent comments led to me forget that this is about
> Wayland. But actually you can use Wayland with the official Nvidia
> driver, and it might resolve the bug. You need to make a couple of
> tweaks to reveal the Wayland login option after installing the Nvidia
> driver:
>
> 1. In /etc/default/grub add the kernel parameter:  nvidia-drm.modeset=1
>
> 2. Comment out the Nvidia rule that is disabling Wayland in
> /usr/lib/udev/rules.d/61-gdm.rules
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1905270
>
> Title:
>   [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
>   monitors, wayland session has a white block on most part of the
>   screen.
>
> Status in Mutter:
>   Unknown
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   on any external monitors, wayland session has a white block on most
>   part of the screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: mutter 3.38.1-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
>   Uname: Linux 5.8.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu50.1
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 23 20:16:15 2020
>   InstallationDate: Installed on 2020-09-16 (67 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
>   SourcePackage: mutter
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions
>

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1907189] Re: Apps become unresponsive and lag when multiple windows opened

** Tags added: xrandr-scaling

** Summary changed:

- Apps become unresponsive and lag when multiple windows opened
+ Apps become unresponsive and lag when multiple windows opened and fractional 
scaling enabled

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

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

Title:
  Apps become unresponsive and lag when multiple windows opened and
  fractional scaling enabled

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When I open an application like Firefox, I split them into 2 windows
  and place one to the left and place the other to the right. So each
  window gets half of the monitor. The right window gets slow when
  clicking and lags for 2 seconds. But the left window is normal. This
  happens to all applications when I have 2 windows. (When 1 window
  only, even if I put it to the right side of the monitor, it still
  works fine, no lag). Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 19:33:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2020-06-23 (167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 2f68:0082 Hoksi Technology DURGOD Taurus K320
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=30757229-adcc-4567-bf22-0a375e36d51d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907189/+subscriptions

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

[Desktop-packages] [Bug 1907189] Re: Apps become unresponsive and lag when multiple windows opened and fractional scaling enabled

This might not be a bug... Because X11 fractional scaling is implemented
using an extra-large screen buffer and copying it (scaled down) to the
real framebuffer. Both of those facts make Xorg fractional scaling much
slower than integer scaling. Wayland fractional scaling has no such
performance problems but the Nvidia driver is not well supported with
Wayland :(

I suggest your best options are either:

* Don't use fractional scaling at all; or

* Enable experimental Nvidia Wayland support:

  1. In /etc/default/grub add the kernel parameter:  nvidia-
drm.modeset=1

  2. Comment out the Nvidia rule that is disabling Wayland in
/usr/lib/udev/rules.d/61-gdm.rules


** Changed in: mutter (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Apps become unresponsive and lag when multiple windows opened and
  fractional scaling enabled

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When I open an application like Firefox, I split them into 2 windows
  and place one to the left and place the other to the right. So each
  window gets half of the monitor. The right window gets slow when
  clicking and lags for 2 seconds. But the left window is normal. This
  happens to all applications when I have 2 windows. (When 1 window
  only, even if I put it to the right side of the monitor, it still
  works fine, no lag). Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 19:33:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2020-06-23 (167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 2f68:0082 Hoksi Technology DURGOD Taurus K320
   Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=30757229-adcc-4567-bf22-0a375e36d51d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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/1907189/+subscriptions

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

[Desktop-packages] [Bug 1905270] Re: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.

Sorry to hear that. Most people seem to find that the nouveau driver
(which this bug is about) is actually less stable than the proprietary
Nvidia driver. Although Wayland support in the proprietary Nvidia driver
is also relatively new and may have problems.


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

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

Title:
  [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external
  monitors, wayland session has a white block on most part of the
  screen.

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

Bug description:
  on any external monitors, wayland session has a white block on most
  part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 23 20:16:15 2020
  InstallationDate: Installed on 2020-09-16 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630

Same problem with the new version from gitlab.

** Attachment added: "installation from gitlab"
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1907121/+attachment/5441905/+files/scan-install.txt

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

Title:
  simple-scan unable to connect scanner HP 2630

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
  corrado@corrado-x4-focal:~$ scanimage -L
  device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
  corrado@corrado-x4-focal:~$ apt policy simple-scan
  simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
   *** 3.36.3-0ubuntu0.20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  corrado@corrado-x4-focal:~$ inxi -Fx
  System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 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 
 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-2:3 
 Sound Server: ALSA v: k5.4.0-56-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: 
/dev/nvme0n1p4 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 27.0 C mobo: 31.0 C 
 Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 
0 fan-6: 0 
 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 
  Info:  Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
 Shell: bash v: 5.0.17 inxi: 3.0.38 
  corrado@corrado-x4-focal:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.3-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 17:16:02 2020
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2020-04-29 (222 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To

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

** Description changed:

+ [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:

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy)
   Status: Triaged => In Progress

-- 
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()

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Triaged
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  In Progress
Status in gnome-shell source package in Hirsute:
  Fix Committed
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://lau

[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630

test with debug

** Attachment added: "test new scan with debug"
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1907121/+attachment/5441906/+files/scan-test.txt

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

Title:
  simple-scan unable to connect scanner HP 2630

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan 
with a message "unable to connect to scanner" 
  corrado@corrado-x4-focal:~$ scanimage -L
  device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a 
Hewlett-Packard DeskJet_2600_series all-in-one
  corrado@corrado-x4-focal:~$ apt policy simple-scan
  simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
   *** 3.36.3-0ubuntu0.20.04.0 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  corrado@corrado-x4-focal:~$ inxi -Fx
  System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 
 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 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 
 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.0.8 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-2:3 
 Sound Server: ALSA v: k5.4.0-56-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: 
/dev/nvme0n1p4 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 27.0 C mobo: 31.0 C 
 Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 
0 fan-6: 0 
 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 
  Info:  Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) 
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
 Shell: bash v: 5.0.17 inxi: 3.0.38 
  corrado@corrado-x4-focal:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.3-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  7 17:16:02 2020
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2020-04-29 (222 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.

[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
   Importance: High
 Assignee: Daniel van Vugt (vanvugt)
   Status: Fix Released

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

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy)
   Importance: Undecided => High

** Description changed:

- [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
- shell in Ubuntu 20.10 (beta).
+ [Impact]
+ 
+ Drag and drop files from Desktop to Nautilus freezes gnome-shell in
+ Ubuntu 20.10. There is no way to recover without killing gnome-shell
+ externally or rebooting.
+ 
+ [Test Case]
+ 
+ 1. Create a file in ~/Desktop
+ 2. Open a nautilus (Files) window of a different directory.
+ 3. Drag the new file from the desktop into the nautilus (Files) window.
+ 
+ The shell should not become unresponsive. Also, the drag is expected to
+ fail and snap back. That's a different issue (bug 1813441) not being
+ fixed here.
+ 
+ [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.
+ 
+ [Other Info]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
-  # set this to 0 to disable apport, or to 1 to enable it
-  # you can temporarily override this with
-  # sudo service apport start force_start=1
-  enabled=0
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

** Description changed:

  [Impact]
  
  Drag and drop files from Desktop to Nautilus freezes gnome-shell in
  Ubuntu 20.10. There is no way to recover without killing gnome-shell
  externally or rebooting.
  
  [Test Case]
  
  1. Create a file in ~/Desktop
  2. Open a nautilus (Files) window of a different directory.
  3. Drag the new file from the desktop into the nautilus (Files) window.
  
  The shell should not become unresponsive. Also, the drag is expected to
  fail and snap back. That's a different issue (bug 1813441) not being
  fixed here.
  
  [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.
  
  [Other Info]
  
+ Patch is in bug 1898005.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

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

Bug description:
  [Im

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