[Desktop-packages] [Bug 2083084] Re: Selection Rectangle does not have an accent color

[vadim]

https://gitlab.gnome.org/GNOME/nautilus/-/issues/3611

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3611
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/3611

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

Title:
  Selection Rectangle does not have an accent color

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  It's just white

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: nautilus 1:47.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 23:11:01 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1223, 840)'
  LiveMediaBuild: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.3-1
   nautilus-extension-gnome-terminal 3.54.0-1ubuntu1

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


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

[Desktop-packages] [Bug 2083084] Re: Selection Rectangle does not have an accent color

[vadim]

** Attachment added: "Screenshot From 2024-09-27 23-08-54.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2083084/+attachment/5822650/+files/Screenshot%20From%202024-09-27%2023-08-54.png

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

Title:
  Selection Rectangle does not have an accent color

Status in nautilus package in Ubuntu:
  New

Bug description:
  It's just white

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: nautilus 1:47.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 23:11:01 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1223, 840)'
  LiveMediaBuild: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.3-1
   nautilus-extension-gnome-terminal 3.54.0-1ubuntu1

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


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

[Desktop-packages] [Bug 2083084] [NEW] Selection Rectangle does not have an accent color

[vadim]

Public bug reported:

It's just white

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: nautilus 1:47.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
Uname: Linux 6.11.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.502
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 23:11:01 2024
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1223, 840)'
LiveMediaBuild: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   44.3-1
 nautilus-extension-gnome-terminal 3.54.0-1ubuntu1

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


** Tags: amd64 apport-bug oracular wayland-session

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

Title:
  Selection Rectangle does not have an accent color

Status in nautilus package in Ubuntu:
  New

Bug description:
  It's just white

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: nautilus 1:47.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 23:11:01 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1223, 840)'
  LiveMediaBuild: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.3-1
   nautilus-extension-gnome-terminal 3.54.0-1ubuntu1

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


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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in Nautilus sidebar

[vadim]

This has already become irrelevant with the release of version 47.  They
moved the desktop to bookmark.

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

Title:
  wayland: desktop folder missing in Nautilus sidebar

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 2057916] Re: Desktop icon disappear in wayland in the sidebar in nautilus, but it appears again in xorg

[vadim]

This has already become irrelevant with the release of version 47.

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

Title:
  Desktop icon disappear in wayland in the sidebar in nautilus, but it
  appears again in xorg

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Can you make another way to add a Desktop icon in wayland, so that it goes by 
default next to the document and not custom added by the user?
  It's just that we don't use Ubuntu with the vanilla gnome, so having a 
desktop icon in the sidebar is very important

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 14 14:09:42 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2024-03-06 (8 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


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

[Desktop-packages] [Bug 2080234] Re: I can't turn off large text

[vadim]

It doesn't turn off. If you set scaling factor 1.00 in the gnome tweaks,
it will reset to 1.25.

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

Title:
  I can't turn off large text

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

Bug description:
  When I installed ubuntu 24.10 I chose large text and since then I
  can't turn it off.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: gnome-control-center 1:47~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 10 14:36:40 2024
  InstallationDate: Installed on 2024-09-09 (1 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2080234/+subscriptions


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

[Desktop-packages] [Bug 2080234] Re: I can't turn off large text

[vadim]

To be more precise i chose large text during installation and since then
I can’t turn it off.

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

Title:
  I can't turn off large text

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

Bug description:
  When I installed ubuntu 24.10 I chose large text and since then I
  can't turn it off.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: gnome-control-center 1:47~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 10 14:36:40 2024
  InstallationDate: Installed on 2024-09-09 (1 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2080234/+subscriptions


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

[Desktop-packages] [Bug 2080234] [NEW] I can't turn off large text

[vadim]

Public bug reported:

When I installed ubuntu 24.10 I chose large text and since then I can't
turn it off.

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: gnome-control-center 1:47~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.30.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 10 14:36:40 2024
InstallationDate: Installed on 2024-09-09 (1 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug oracular wayland-session

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

Title:
  I can't turn off large text

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

Bug description:
  When I installed ubuntu 24.10 I chose large text and since then I
  can't turn it off.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: gnome-control-center 1:47~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 10 14:36:40 2024
  InstallationDate: Installed on 2024-09-09 (1 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2080234/+subscriptions


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

[Desktop-packages] [Bug 2079982] Re: When using yellow as an accent color, the background of the settings becomes darker than when using other accent colors.

[vadim]

** Attachment added: "Screencast From 2024-09-09 14-13-02.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2079982/+attachment/5814785/+files/Screencast%20From%202024-09-09%2014-13-02.webm

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

Title:
  When using yellow as an accent color, the background of the settings
  becomes darker than when using other accent colors.

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

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: gnome-control-center 1:47~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 13:37:44 2024
  InstallationDate: Installed on 2024-09-09 (0 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2079982/+subscriptions


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

[Desktop-packages] [Bug 2079982] [NEW] When using yellow as an accent color, the background of the settings becomes darker than when using other accent colors.

[vadim]

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: gnome-control-center 1:47~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.30.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  9 13:37:44 2024
InstallationDate: Installed on 2024-09-09 (0 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug oracular wayland-session

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

Title:
  When using yellow as an accent color, the background of the settings
  becomes darker than when using other accent colors.

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

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: gnome-control-center 1:47~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 13:37:44 2024
  InstallationDate: Installed on 2024-09-09 (0 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2079982/+subscriptions


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

[Desktop-packages] [Bug 2023044] Re: New thumbnails are missing from file chooser

[vadim]

YS😋😠😍🙃😍😍🙃😍🤤☺️😝🤤😜🙂😛🙂😐😬😶😬😶🤫🤭🤭🤫

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

Title:
  New thumbnails are missing from file chooser

Status in GTK+:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  --
  Thumbnails do not show in the file chooser (provided by gtk4 which is also 
used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the 
thumbnail is generated by for instance, viewing the folder in Nautilus.

  This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable
  GTK release to support the "grid view" in the filechooser.

  Test Case
  -
  1. Use Firefox to download an image file. (This test case assumes you're 
using the default Firefox distributed as a Snap).
  2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser.
  3. Navigate to where the file was downloaded (your Downloads/ folder?)
  4. The file should show a thumbnail image

  Number 4 doesn't happen correctly until you open the folder in
  Nautilus at least once.

  Other Info
  --
  I am linking to what upstream considers the master bug for this issue. But a 
duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 
which has a clearer summary.

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


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

[Desktop-packages] [Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland

[vadim]

I also want to say that the deb version of Google Chrome has the same
behavior 'large text accessibility setting not reflect in Chromium'

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

Title:
  Gnome's large text accessibility setting not reflect in Chromium in
  Wayland

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Chromium - 127.0.6533.119

  wayland

  Chromium app ignores large text setting if started with --ozone-
  platform-hint=wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 20:25:21 2024
  InstallationDate: Installed on 2024-08-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Snap: chromium 127.0.6533.119 (latest/candidate)
  SnapSource: ubuntu/+source/chromium-browser
  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/2077272/+subscriptions


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

[Desktop-packages] [Bug 2070889] Re: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening.

[vadim]

>spinning cursor went away
Yes, Wayland via Ozone fixes the issue for wayland session.

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

Title:
  Chromium opens, but cursor remains in "loading" state within 15
  seconds after opening.

Status in chromium-browser package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  How to replay:
  1.Open chromium - Chromium opens
  2.hover over the chromium icon on the dock
  3.there will be a loading bar on the cursor

  That's what I checked, I took flash drives with a clean installation and 
found out that Ubuntu has this problem, but Fedora does not have this problem. 
  This problem occurs on all chromium browsers, it doesn’t matter whether they 
are deb, snap, flatpack, the problem does not go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 22:55:57 2024
  InstallationDate: Installed on 2024-04-17 (70 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  Snap: chromium 126.0.6478.114 (stable)
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   94   Done2024-06-26T22:54:33+03:00  2024-06-26T22:54:44+03:00  Install 
"chromium" snap
  SnapSource: ubuntu/+source/chromium-browser
  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/2070889/+subscriptions


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

[Desktop-packages] [Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland

[vadim]

https://issues.chromium.org/issues/360909063

I created a bug report

** Bug watch added: issues.chromium.org/issues #360909063
   https://issues.chromium.org/issues/360909063

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

Title:
  Gnome's large text accessibility setting not reflect in Chromium in
  Wayland

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium - 127.0.6533.119

  wayland

  Chromium app ignores large text setting

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 20:25:21 2024
  InstallationDate: Installed on 2024-08-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Snap: chromium 127.0.6533.119 (latest/candidate)
  SnapSource: ubuntu/+source/chromium-browser
  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/2077272/+subscriptions


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

[Desktop-packages] [Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland

[vadim]

It seems that everything fell into place, the scale is preserved, the title bar 
is present again. Indeed, the "use system title bar and borders" option works. 
But it is confusing.
Because in the flatpak version, the deb version of Google Chrome, as well as 
Chromium downloaded from AUR (I did this on another distribution) this option 
is hidden by default. I think it's best to hide this by default to avoid 
confusing users like me.

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

Title:
  Gnome's large text accessibility setting not reflect in Chromium in
  Wayland

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium - 127.0.6533.119

  wayland

  Chromium app ignores large text setting

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 20:25:21 2024
  InstallationDate: Installed on 2024-08-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Snap: chromium 127.0.6533.119 (latest/candidate)
  SnapSource: ubuntu/+source/chromium-browser
  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/2077272/+subscriptions


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

[Desktop-packages] [Bug 2077272] Re: Difference in behavior in wayland and xorg sessions

[vadim]

this is what a wayland session looks like

** Attachment added: "wayland.webm"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+attachment/5806974/+files/wayland.webm

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

Title:
  Difference in behavior in wayland and xorg sessions

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium - 127.0.6533.119

  wayland

  Chromium app ignores large text setting 
  There is no top bar named New Tab - chromuim

  
  -
  xorg
  There is top bar named New Tab - chromuim
  There is a bug "Chromium opens, but still loads within 15 seconds after 
opening"

  -

  What needs to be done:
  1)Remove top bar in xorg session.
  The flatpak or aur version does not have this top bar. It should not be in 
any session. Moreover, Google Chrome deb version comes without a top bar.

  2)Chromium app should not ignore large text setting in ubuntu in
  wayland session

  3)Chromium opens, but still loads within 15 seconds after opening
  https://issues.chromium.org/issues/349835592
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889

  It seems someone has created a custom patch for the Wayland session within 
the Snap format. Chromium now launches directly into the Wayland session 
without any delay.
  As seen in the upstream bug, no one seems to know why this is happening or is 
willing to address it. In other words, Google doesn't seem to prioritize Linux 
development.
  We need to figure out what this patch does, how to integrate it into the xorg 
session, and who can merge it into the upstream repository. This is a serious 
issue affecting all GNOME-based and chromium-based browser distributions and 
their forks, and it's being ignored.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 20:25:21 2024
  InstallationDate: Installed on 2024-08-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Snap: chromium 127.0.6533.119 (latest/candidate)
  SnapSource: ubuntu/+source/chromium-browser
  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/2077272/+subscriptions


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

[Desktop-packages] [Bug 2070889] Re: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening.

[vadim]

You added some patch to version 127.0.6533.119 that makes it open
normally on wayland session. What did you do? Because this behavior is
preserved in the flatpak of the same version.

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

Title:
  Chromium opens, but cursor remains in "loading" state within 15
  seconds after opening.

Status in chromium-browser package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  How to replay:
  1.Open chromium - Chromium opens
  2.hover over the chromium icon on the dock
  3.there will be a loading bar on the cursor

  That's what I checked, I took flash drives with a clean installation and 
found out that Ubuntu has this problem, but Fedora does not have this problem. 
  This problem occurs on all chromium browsers, it doesn’t matter whether they 
are deb, snap, flatpack, the problem does not go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 22:55:57 2024
  InstallationDate: Installed on 2024-04-17 (70 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  Snap: chromium 126.0.6478.114 (stable)
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   94   Done2024-06-26T22:54:33+03:00  2024-06-26T22:54:44+03:00  Install 
"chromium" snap
  SnapSource: ubuntu/+source/chromium-browser
  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/2070889/+subscriptions


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

[Desktop-packages] [Bug 2077272] Re: Difference in behavior in wayland and xorg sessions

[vadim]

Okay, let's just talk only about the large text text then.

Wayland
-
Ubuntu -> Settings -> accessibility -> seeing -> large text. Chromium's 
v127.0.6533.119. The interface does not change at all. But it must change.


** Attachment added: "Screenshot from 2024-08-19 12-25-16.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+attachment/5806970/+files/Screenshot%20from%202024-08-19%2012-25-16.png

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

Title:
  Difference in behavior in wayland and xorg sessions

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium - 127.0.6533.119

  wayland

  Chromium app ignores large text setting 
  There is no top bar named New Tab - chromuim

  
  -
  xorg
  There is top bar named New Tab - chromuim
  There is a bug "Chromium opens, but still loads within 15 seconds after 
opening"

  -

  What needs to be done:
  1)Remove top bar in xorg session.
  The flatpak or aur version does not have this top bar. It should not be in 
any session. Moreover, Google Chrome deb version comes without a top bar.

  2)Chromium app should not ignore large text setting in ubuntu in
  wayland session

  3)Chromium opens, but still loads within 15 seconds after opening
  https://issues.chromium.org/issues/349835592
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889

  It seems someone has created a custom patch for the Wayland session within 
the Snap format. Chromium now launches directly into the Wayland session 
without any delay.
  As seen in the upstream bug, no one seems to know why this is happening or is 
willing to address it. In other words, Google doesn't seem to prioritize Linux 
development.
  We need to figure out what this patch does, how to integrate it into the xorg 
session, and who can merge it into the upstream repository. This is a serious 
issue affecting all GNOME-based and chromium-based browser distributions and 
their forks, and it's being ignored.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 20:25:21 2024
  InstallationDate: Installed on 2024-08-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Snap: chromium 127.0.6533.119 (latest/candidate)
  SnapSource: ubuntu/+source/chromium-browser
  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/2077272/+subscriptions


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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in Nautilus sidebar

[vadim]

Still broken in 24.04

They don't seem to understand that 
1)Ubuntu has desktop icons 
2)Attach icon will be at the very bottom, which is inconvenient 
3)Wayland is already the present, not the future

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

Title:
  wayland: desktop folder missing in Nautilus sidebar

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

Ubuntu 24.04 still has a bug.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

[vadim]

I don't know how to write the path to the cursor file
breeze cursors is a separate folder
And the cursor in the yaru is in /Yaru/cursors
I tried to write the full path there and it didn’t work, I don’t know how to 
write the path to the cursor

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

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

[vadim]

Well I found a solution when I downloaded the breeze theme I got breeze-
cursor instead of a white square when I use dmz-white in wayland when I
move the cursor to dash to panel. It is also the default cursor in xorg.

How it works? Like this:
There is a default folder in /usr/share/icons 
There is index.theme inside 

There is a line that indicates
Inherits=breeze_cursors

Basically you need to create a new cross cursor that would indicate that
there is no cursor or supply the sudo apt-get install breeze package by
default for Ubuntu

** Attachment added: "index.theme"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+attachment/5768366/+files/index.theme

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

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2062377] [NEW] Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

[vadim]

Public bug reported:

1)Go to xorg
2)Download Gnome Tweak Tool
3)Select DMZ-white
4)crash from the system

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
 GCC version:
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 17:38:02 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
 Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
MachineType: Acer Aspire A715-42G
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2021
dmi.bios.release: 1.2
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Azalea_CAS
dmi.board.vendor: LN
dmi.board.version: V1.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.02
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
dmi.product.family: Aspire 7
dmi.product.name: Aspire A715-42G
dmi.product.sku: 
dmi.product.version: V1.02
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in xorg package in Ubuntu:
  New

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [10

[Desktop-packages] [Bug 2023044] Re: New thumbnails are missing from file chooser

[vadim]

Watching by the forum, as someone proposes a solution, they say it sucks
and do nothing. That's the whole point of open source.

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

Title:
  New thumbnails are missing from file chooser

Status in GTK+:
  New
Status in gtk4 package in Ubuntu:
  Triaged

Bug description:
  Impact
  --
  Thumbnails do not show in the file chooser (provided by gtk4 which is also 
used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the 
thumbnail is generated by for instance, viewing the folder in Nautilus.

  This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable
  GTK release to support the "grid view" in the filechooser.

  Test Case
  -
  1. Use Firefox to download an image file. (This test case assumes you're 
using the default Firefox distributed as a Snap).
  2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser.
  3. Navigate to where the file was downloaded (your Downloads/ folder?)
  4. The file should show a thumbnail image

  Number 4 doesn't happen correctly until you open the folder in
  Nautilus at least once.

  Other Info
  --
  I am linking to what upstream considers the master bug for this issue. But a 
duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 
which has a clearer summary.

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

now I'm a wayland fan because the xorg bug is still present

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2057916] [NEW] Desktop icon disappear in wayland in the sidebar in nautilus, but it appears again in xorg

[vadim]

Public bug reported:

Can you make another way to add a Desktop icon in wayland, so that it goes by 
default next to the document and not custom added by the user?
It's just that we don't use Ubuntu with the vanilla gnome, so having a desktop 
icon in the sidebar is very important

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: nautilus 1:45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 14 14:09:42 2024
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2024-03-06 (8 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


** Tags: amd64 apport-bug mantic

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

Title:
  Desktop icon disappear in wayland in the sidebar in nautilus, but it
  appears again in xorg

Status in nautilus package in Ubuntu:
  New

Bug description:
  Can you make another way to add a Desktop icon in wayland, so that it goes by 
default next to the document and not custom added by the user?
  It's just that we don't use Ubuntu with the vanilla gnome, so having a 
desktop icon in the sidebar is very important

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 14 14:09:42 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2024-03-06 (8 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


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

[Desktop-packages] [Bug 2033590] [NEW] random crashes of gnome-characters

[Vadim Sukhomlinov]

Public bug reported:

Usually just a one-line record in syslog:

Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY-
ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed:
sinfo->n_allocated > 0

Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY-
ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed:
sinfo->n_allocated > 0

Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool-org.gnome.[11513]:
segfault at 1c8 ip 7fd1854d1ae3 sp 7fd1794ca9d8 error 6 in
libglib-2.0.so.0.7200.4[7fd18547a000+8f000]

Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome-character[18769]:
segfault at 18 ip 7fb24db9eae3 sp 7ffc99c29ca8 error 6 in
libglib-2.0.so.0.7200.4[7fb24db47000+8f000]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-characters 41.0-4
ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111
Uname: Linux 5.15.0-82-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Aug 30 22:52:57 2023
InstallationDate: Installed on 2020-05-03 (1215 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-characters
UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  random crashes of gnome-characters

Status in gnome-characters package in Ubuntu:
  New

Bug description:
  Usually just a one-line record in syslog:

  Aug 30 19:10:45 COLOSSUS org.gnome.Characters[11012]: ***MEMORY-
  ERROR***: org.gnome.Characters[11012]: GSlice: assertion failed:
  sinfo->n_allocated > 0

  Aug 30 19:12:38 COLOSSUS org.gnome.Characters[11134]: ***MEMORY-
  ERROR***: org.gnome.Characters[11134]: GSlice: assertion failed:
  sinfo->n_allocated > 0

  Aug 30 19:17:29 COLOSSUS kernel: [ 2840.611031] pool-
  org.gnome.[11513]: segfault at 1c8 ip 7fd1854d1ae3 sp
  7fd1794ca9d8 error 6 in
  libglib-2.0.so.0.7200.4[7fd18547a000+8f000]

  Aug 30 22:44:26 COLOSSUS kernel: [15257.581416] gnome-
  character[18769]: segfault at 18 ip 7fb24db9eae3 sp
  7ffc99c29ca8 error 6 in
  libglib-2.0.so.0.7200.4[7fb24db47000+8f000]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-characters 41.0-4
  ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111
  Uname: Linux 5.15.0-82-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Aug 30 22:52:57 2023
  InstallationDate: Installed on 2020-05-03 (1215 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-characters
  UpgradeStatus: Upgraded to jammy on 2022-07-15 (412 days ago)

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


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

[Desktop-packages] [Bug 2021915] Re: dock overlays the rename box

[vadim]

yes, I can't click with the mouse in that area, I use the arrows on the 
keyboard. 
My dock is not set to auto-hide

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

Title:
  dock overlays the rename box

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

Bug description:
  ubuntu 23.04
  wayland and xorg have the same bug
  https://imgur.com/chWxw27

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 31 04:29:44 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2023-05-30 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=5c2a9ea0-07a7-4edf-82d7-b8daefb3a66b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2022
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.

[vadim]

I really don't like this bug, why doesn't anyone fix it?

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

Title:
  Switching to dark mode in settings does not change shell theme.

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

Bug description:
  Changing the "Style" in the "Appearance" section of "Settings" (gnome-
  control-center), does not update the shell theme. When I select dark
  mode from settings, Libadwaita apps respond to the changes, but the
  shell theme and GTK3 applications do not. This has been observed on
  both Wayland and X11.

  Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

  Package Version: 1:43~rc-1ubuntu2

  What I Expected: Changing the style in settings will affect all the
  apps that support changing light/dark mode. The shell theme will also
  respond to the change.

  What happened instead: Only libadwaita apps are affected by changing
  the style in Settings. GTK3 apps and the shell theme do not change.
  When changing to dark mode via the quick settings menu, all the apps
  change their color scheme appropriately. However, there is not a
  smooth transition when switching the style from quick settings.

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

I found more reports:

https://youtrack.jetbrains.com/issue/IDEA-145727/Context-menu-item-
cannot-be-clicked-when-overlaps-the-top-Gnome-bar

https://youtrack.jetbrains.com/issue/IDEA-286370/Cant-click-menu-items-
over-Ubuntu-task-bar.

This error has been around for 5 years.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

Yes, I noticed that it also affects the menu bar. If this is indeed a
problem with the widget in xorg, what should I do? I don't want to use
wayland because it contains many bugs that degrade the Linux experience.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session

[vadim]

ubuntu 22.10 the problem exists

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

Title:
  Using certain xkb-options, e.g. Alt+Shift, for switching input sources
  not reflected by the input source indicator in a wayland session

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

Bug description:
  Currently, there is no way to define Left Alt + Left Shift key combination to 
change keyboard layouts in Ubuntu 22.04. In previous versions there was a 
convenient "Keyboard Layout Options" window in which there was able to set 
required key combination. Since 22.04 release I can't find a way to do that 
because useless "Keyboard Shortcuts" window opens instead in which unable to 
set Left Alt + Left Shift as "Switch to the next source" shortcut.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-01-07 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  jammy wayland-session ubiquity-22.04.3
  Uname: Linux 5.13.0-19-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-control-center/+bug/1956916/+subscriptions


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

But in wayland everything works fine, wayland have some other overlay
algorithm.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

i don't use auto-hide

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

[vadim]

in wayland everything works fine, this is an xorg problem

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

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

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1872475] Re: Wine programs in the dock don't get the orange circle when executed, but get duplicated at the bottom of the dock instead.

[vadim]

This is a classic bug, the point is that the developer did not add the
parameter StartupWMClass in  .desktop file. Basically there are 3 ways
to solve the problem. 1) Download snap app version 2) Create your custom
shortcut (where do you add StartupWMClass) 3)Tell the developer to add
StartupWMClass.

Also watch this video:
https://www.youtube.com/watch?v=xZ_M3Q-U-J0

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

Title:
  Wine programs in the dock don't get the orange circle when executed,
  but get duplicated at the bottom of the dock instead.

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

Bug description:
  I really don't know whether to file this bug report with wine or with
  gnome-shell, but it used to work, so I suspect it is a gnome-shell
  thing.

  How to duplicate it:
  -Install a wine program, and put its icon in the gnome dock.
  -Click on the wine program icon in the dock.
  -An identical icon appears at the bottom of your list of running programs, 
with an orange dot, but the original one has no orange dot to indicate it is 
running.

  What should happen:
  -No duplicate icon should be displayed at the bottom of your dock, and the 
orange dot should appear beside the original icon.

  See my screenshot included.  The icon to look at is the LTSpice one,
  11 from the top, and then find it also near the bottom of the dock
  with an orange dot.

  Thanks for your good work!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 07:30:50 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-19 (360 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1970031] Re: Grey (gray) appears as pink in Ubuntu 22.04

[vadim]

i created new issue on gitlab
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/685

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #685
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/685

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

Title:
  Grey (gray) appears as pink in Ubuntu 22.04

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Grey (gray) appears as pink in Ubuntu 22.04

  WORKAROUND:

  Settings > Colour > YOUR MONITOR = OFF

  ORIGINAL DESCRIPTION:

  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
     Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1970031/+subscriptions


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

[Desktop-packages] [Bug 1970031] Re: [Xiaomi Timi TM1701] Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

[vadim]

1)Ubuntu 22.04 removed Wayland 2)if i set it to sRGB then everything is
fine, if it detects the color automatically for my laptop then gray-pink
colors appear instead of gray

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

Title:
  [Xiaomi Timi TM1701] Instead of gray, my monitor displays pink-gray.
  Ubuntu 22.04

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1970031] Re: Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

[vadim]

i don't really know for sure if this is an xorg problem, but it was fine
in the previous version of 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/1970031

Title:
  Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1970031] [NEW] Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

[vadim]

Public bug reported:

i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
monitor started showing a gray-pink color. I can't take a screenshot
because it will just be gray on your monitor (i checked the screenshot
in windows 11). Did the developers break something in the video card
driver or why did it happen?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 11:24:05 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Sat Apr 23 19:54:00 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
   Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
InstallationDate: Installed on 2022-04-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Timi TM1701
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 106.121
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: XMAKB5R0P0603
dmi.board.asset.tag: Any
dmi.board.name: TM1701
dmi.board.vendor: Timi
dmi.board.version: MP
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 0.3
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
dmi.product.family: Timibook
dmi.product.name: TM1701
dmi.sys.vendor: Timi
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy 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/1970031

Title:
  Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: 

[Desktop-packages] [Bug 1960596] [NEW] no sound after upgrade to 21.10

[Vadim Peretokin]

Public bug reported:

I had sound working in 21.04, did the mandatory upgrade to 21.10 and all
sound is gone - in videos, browsers, games. What could be the problem?

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pipewire 0.3.32-1
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 11 08:59:34 2022
InstallationDate: Installed on 2020-12-21 (416 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pipewire
UpgradeStatus: Upgraded to impish on 2022-02-10 (0 days ago)

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


** Tags: amd64 apport-bug impish

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

Title:
  no sound after upgrade to 21.10

Status in pipewire package in Ubuntu:
  New

Bug description:
  I had sound working in 21.04, did the mandatory upgrade to 21.10 and
  all sound is gone - in videos, browsers, games. What could be the
  problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pipewire 0.3.32-1
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 11 08:59:34 2022
  InstallationDate: Installed on 2020-12-21 (416 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to impish on 2022-02-10 (0 days ago)

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


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

[Desktop-packages] [Bug 1924895] Re: Settings crashes as soon as it is opened

[Vadim Peretokin]

Indeed I had the first two issues. Settings don't seem to crash after a
reboot - will update this when it happens again.

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

Title:
  Settings crashes as soon as it is opened

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

Bug description:
  Just opening the settings causes it to almost immediately crash.

  
  ❯ gnome-control-center

  
  (gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)
  Segmentation fault (core dumped)
  ~ 
  ❯ 
  ~ 
  ❯ gnome-control-center user-accounts

  (gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed
  to commit changes to dconf: Could not connect: Connection refused

  (gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to 
commit changes to dconf: Could not connect: Connection refused
  Segmentation fault (core dumped)
  ~ took 16s 
  ❯ gdb gnome-control-center
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gnome-control-center...
  (No debugging symbols found in gnome-control-center)
  (gdb) r
  Starting program: /usr/bin/gnome-control-center 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffea9e0700 (LWP 13237)]
  [New Thread 0x7fffdf05b700 (LWP 13238)]
  [New Thread 0x7fffde85a700 (LWP 13239)]
  [New Thread 0x7fffde059700 (LWP 13240)]
  [New Thread 0x7fffdd858700 (LWP 13241)]
  [New Thread 0x7fffdcc17700 (LWP 13242)]
  [New Thread 0x7fffc7fff700 (LWP 13243)]
  [New Thread 0x7fffc77fe700 (LWP 13244)]
  [New Thread 0x7fffc6ffd700 (LWP 13245)]

  (gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)

  Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffc7fff700 (LWP 13243)]
  0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
  #3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
  #4  start_thread (arg=) at pthread_create.c:488
  #5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  (gdb) q
  A debugging session is active.

  Inferior 1 [process 13233] will be killed.

  Quit anyway? (y or n) y
  ~ took 20s 
  ❯ gnome-control-center --version
  gnome-control-center 3.36.5
  ~ 
  ❯ ubuntu-bug gnome-control-center

  (gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
  g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
  failed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 09:16:22 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1522 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1924895/+subscriptions

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

[Desktop-packages] [Bug 1924895] [NEW] Settings crashes as soon as it is opened

[Vadim Peretokin]

Public bug reported:

Just opening the settings causes it to almost immediately crash.


❯ gnome-control-center


(gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)
Segmentation fault (core dumped)
~ 
❯ 
~ 
❯ gnome-control-center user-accounts

(gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed to
commit changes to dconf: Could not connect: Connection refused

(gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to commit 
changes to dconf: Could not connect: Connection refused
Segmentation fault (core dumped)
~ took 16s 
❯ gdb gnome-control-center
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9e0700 (LWP 13237)]
[New Thread 0x7fffdf05b700 (LWP 13238)]
[New Thread 0x7fffde85a700 (LWP 13239)]
[New Thread 0x7fffde059700 (LWP 13240)]
[New Thread 0x7fffdd858700 (LWP 13241)]
[New Thread 0x7fffdcc17700 (LWP 13242)]
[New Thread 0x7fffc7fff700 (LWP 13243)]
[New Thread 0x7fffc77fe700 (LWP 13244)]
[New Thread 0x7fffc6ffd700 (LWP 13245)]

(gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)

Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc7fff700 (LWP 13243)]
0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
#3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
#4  start_thread (arg=) at pthread_create.c:488
#5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) q
A debugging session is active.

Inferior 1 [process 13233] will be killed.

Quit anyway? (y or n) y
~ took 20s 
❯ gnome-control-center --version
gnome-control-center 3.36.5
~ 
❯ ubuntu-bug gnome-control-center

(gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
failed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:16:22 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1522 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Settings crashes as soon as it is opened

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

Bug description:
  Just opening the settings causes it to almost immediately crash.

  
  ❯ gnome-control-center

  
  (gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)
  Segmentation fault (core dumped)
  ~ 
  ❯ 
  ~ 
  ❯ gnome-control-center user-accounts

  (gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed
  to commit changes to dconf: Could not connect: Connection refused

  (gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to 
commit changes to dconf: Could not connect: Connection refused
  Segmentation fault (core dumped)
  ~ took 16s 
  ❯ gdb gnome-control-center
  GNU

[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

[Vadim Peretokin]

Is the fix available in 20.04 LTS, or just 20.10 only?

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

Title:
  Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null
  has no properties
  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  Shell becomes slow and unresponsive flooding journal with JS errors

  [ Test case ]

  1. Resize the terminal to use half the screen (using CMD+LEFT)
  2. switch it to fullscreen (F11) and back (F11)
  3. Repeat this some number of times ensure we don't end up in a loop with
 100% CPU usage.
  4. Ensure that it's still possible to get window focus and the UI is 
responsive.

  [ Regression potential ]

  Events are ignored for windows which are still visible.

  ---

  O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I 
did face these problems. The sometimes I have to wait 10 seconds to see if a 
window reacts or not. It is hard to use.
    Installiert:   3.36.1-5ubuntu2
    Installationskandidat: 3.36.2-1ubuntu1~20.04.1
    Versionstabelle:
   3.36.2-1ubuntu1~20.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 3.36.1-5ubuntu2 100
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: BugDistroRelease: 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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun May 24 15:43:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago)

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

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

[Desktop-packages] [Bug 1909543] [NEW] "Failed to start Sound Service" in security logs

[Vadim Peretokin]

Public bug reported:

Security logs are complaining about failing to start the sound service,
on a new installation of Ubuntu 20.04 LTS. This is concerning.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.8
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vadi   3182 F pulseaudio
 /dev/snd/pcmC0D0c:   vadi   3182 F...m pulseaudio
 /dev/snd/pcmC0D0p:   vadi   3182 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 29 09:35:00 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1412 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.25.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Attachment added: "Selection_560.png"
   
https://bugs.launchpad.net/bugs/1909543/+attachment/5447585/+files/Selection_560.png

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

Title:
  "Failed to start Sound Service" in security logs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Security logs are complaining about failing to start the sound
  service, on a new installation of Ubuntu 20.04 LTS. This is
  concerning.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.8
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vadi   3182 F pulseaudio
   /dev/snd/pcmC0D0c:   vadi   3182 F...m pulseaudio
   /dev/snd/pcmC0D0p:   vadi   3182 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 29 09:35:00 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1412 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1908889] [NEW] "Failed to install file: not supported" error

[Vadim Peretokin]

Public bug reported:

On a brand new installation of Ubuntu 20.04 LTS, trying to install a
.deb (say, from discord.com) gives a "Failed to install file: not
supported" error.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 21 10:59:49 2020
InstallationDate: Installed on 2020-12-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  "Failed to install file: not supported" error

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a brand new installation of Ubuntu 20.04 LTS, trying to install a
  .deb (say, from discord.com) gives a "Failed to install file: not
  supported" error.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 10:59:49 2020
  InstallationDate: Installed on 2020-12-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902446] Re: Not possible to see list of wifi networks

[Vadim Peretokin]

The usual gnome environment.

Not much in journalctl:

nov 03 22:59:57 volga audit[9670]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9670 comm="hirimain" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 22:59:57 volga kernel: audit: type=1400 audit(1604440797.544:5054): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9670 comm="hirimain" requested_mask="r" denied_m>
nov 03 23:00:10 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=55594 PROTO=2 
nov 03 23:00:42 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a2:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=36 
TOS=0x00 PREC=0x00 TTL=1 ID=1 PROTO=2 
nov 03 23:00:43 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:fb:92:d1:cf:19:a3:4c:08:00 SRC=192.168.1.226 DST=224.0.0.251 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.353:5055): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.577:5056): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.701:5057): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:51 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="Worker" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:51 volga kernel: audit: type=1400 audit(1604440851.661:5058): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="Worker" requested_mask="r" denied_mas>
nov 03 23:01:11 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=61275 PROTO=2 
nov 03 23:01:18 volga gnome-shell[3615]: 
../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() vir>
nov 03 23:01:21 volga systemd[2315]: Started Application launched by 
gsd-media-keys.
nov 03 23:01:21 volga systemd[2315]: Started VTE child process 69735 launched 
by x-terminal-emulator process 39586.
nov 03 23:01:21 volga systemd[2315]: 
gnome-launched-x-terminal-emulator-69726.scope: Succeeded.

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

Title:
  Not possible to see list of wifi networks

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using the default 'light' theme, the network listing is impossible to
  read

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 19:41:38 2020
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-15 (1355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1902446] [NEW] Not possible to see list of wifi networks

[Vadim Peretokin]

Public bug reported:

Using the default 'light' theme, the network listing is impossible to
read

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 19:41:38 2020
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-15 (1355 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug focal

** Attachment added: "Workspace 1_350.png"
   
https://bugs.launchpad.net/bugs/1902446/+attachment/5430088/+files/Workspace%201_350.png

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

Title:
  Not possible to see list of wifi networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using the default 'light' theme, the network listing is impossible to
  read

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 19:41:38 2020
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-15 (1355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1723758] Re: Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)

[Vadim Shakurov]

I have had bug with locks up too.

июл 10 12:20:41 Home-WS kernel: nouveau :01:00.0: gr: DATA_ERROR 0012 
[RT_LINEAR_WITH_ZETA]
июл 10 12:20:41 Home-WS kernel: nouveau :01:00.0: gr: 0010 [] ch 3 
[001fa14000 systemd-logind[858]] subc 3 class 8597 mthd 0d78 data 0004

I don't know it's new bag or same.

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

Title:
  Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up
  (hangs)

Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  This is an intermittent issue. Rumored to be fixed in Ubuntu 17.04
  according to comments in bug 1645375

  Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at
  /build/linux-
  
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 15 12:27:28 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   iscsitarget, 1.4.20.3+svn502, 4.4.0-96-generic, x86_64: installed
   iscsitarget, 1.4.20.3+svn502, 4.4.0-97-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 210] 
[1462:2011]
  InstallationDate: Installed on 2016-01-13 (641 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/vg0-lv0 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct 12 15:08:58 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 8
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9
   inputMicrosoft Comfort Optical Mouse 1000 MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1860830] Re: Geolocation not working − the Google maps API always returns error codes

[Vadim Evard]

Upd: you can indeed override the API key in about:config.
To find a value that works, download Firefox from mozilla.org, extract the 
archive, and run

grep --binary-files=text MOZ_GOOGLE_LOCATION_SERVICE_API_KEY omni.ja

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

Title:
  Geolocation not working − the Google maps API always returns error
  codes

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Happened as soon as Firefox was updated to 72.0.1. I noticed sites
  could not determine my location.

  Troubleshooting page shows "missing" under Location service key.

  I have another computer running Lubuntu 18.04LTS, which I rarely use.
  Just for fun, I booted it up and as soon as the software updater
  updated Firefox to 72.0.1, location stopped working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 72.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frank  2125 F pulseaudio
   /dev/snd/controlC1:  frank  2125 F pulseaudio
  BuildID: 20200107212822
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 19:58:30 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:727
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago)
  dmi.bios.date: 03/24/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.27
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1442
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 048D10242B202
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1883421] Re: Ubuntu Software can't install .deb files

[Vadim Peretokin]

I imagine it is gnome-software.

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

Title:
  Ubuntu Software can't install .deb files

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Download the .deb from https://zoom.us/support/download and try to
  "Open" it - you'll get an error message saying the tool for installing
  software doesn't know what to do with a software installer file.

  Attached is a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44
  Uname: Linux 5.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun 14 12:38:14 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (3004 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883421] [NEW] Ubuntu Software can't install .deb files

[Vadim Peretokin]

Public bug reported:

Download the .deb from https://zoom.us/support/download and try to
"Open" it - you'll get an error message saying the tool for installing
software doesn't know what to do with a software installer file.

Attached is a screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-software (not installed)
ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44
Uname: Linux 5.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jun 14 12:38:14 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (3004 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Selection_670.png"
   
https://bugs.launchpad.net/bugs/1883421/+attachment/5383749/+files/Selection_670.png

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

Title:
  Ubuntu Software can't install .deb files

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Download the .deb from https://zoom.us/support/download and try to
  "Open" it - you'll get an error message saying the tool for installing
  software doesn't know what to do with a software installer file.

  Attached is a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44
  Uname: Linux 5.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun 14 12:38:14 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (3004 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880095] Re: Keyboard entry stopped working

[Vadim Peretokin]

Yes the mouse did work, and I was able to use the Super key to bring up
Unity's application menu (on this computer I use Unity). Typing text
didn't work, though.

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

Title:
  Keyboard entry stopped working

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

Bug description:
  I was toggling between text entry languages when the keyboard entry
  suddenly stopped working. Even the onscreen keyboard was not able to
  entry any keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri May 22 09:18:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2012-03-23 (2981 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri May 22 09:13:46 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1880095] [NEW] Keyboard entry stopped working

[Vadim Peretokin]

Public bug reported:

I was toggling between text entry languages when the keyboard entry
suddenly stopped working. Even the onscreen keyboard was not able to
entry any keys.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-all (not installed)
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri May 22 09:18:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] 
[1462:3362]
InstallationDate: Installed on 2012-03-23 (2981 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri May 22 09:13:46 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 focal possible-manual-nvidia-install 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/1880095

Title:
  Keyboard entry stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  I was toggling between text entry languages when the keyboard entry
  suddenly stopped working. Even the onscreen keyboard was not able to
  entry any keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu

[Desktop-packages] [Bug 1878395] [NEW] Gnome-software spammed log files with 3, 000 lines

[Vadim Peretokin]

Public bug reported:

Gnome-software spammed log files with 3,000 lines of text and that's not
OK.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18
Uname: Linux 5.3.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed May 13 12:56:19 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2972 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.1
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (187 days ago)

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


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "gnome-software spam"
   
https://bugs.launchpad.net/bugs/1878395/+attachment/5370889/+files/gnome-software%20spam

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

Title:
  Gnome-software spammed log files with 3,000 lines

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gnome-software spammed log files with 3,000 lines of text and that's
  not OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18
  Uname: Linux 5.3.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed May 13 12:56:19 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2972 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.1
   gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to eoan on 2019-11-07 (187 days ago)

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

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

[Desktop-packages] [Bug 1877712] Re: Severe performance degradation in Gnome Shell after upgrade to 20.04

[Vadim Peretokin]

Sorry, that's not really practical to do on a production system.

That said, the issue could have been because there wasn't enough disk
space. Clearing it up and rebooting seems to have solved things. This is
a change in behaviour from previous Ubuntu releases.

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

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Severe performance degradation in Gnome Shell after upgrade to 20.04 -
  everything is slow, even moving the mouse through a right-click menu
  has a severely delayed selection animation.

  Video displaying the problem: https://drive.google.com/open?id=1rAKN-
  ZKks6o9d37hQMbnMgNeAOy8VZyp

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:57:02 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1178 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago)

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

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

[Desktop-packages] [Bug 1877712] Re: Severe performance degradation in Gnome Shell after upgrade to 20.04

[Vadim Peretokin]

The log file is absolutely flooded with errors like:

May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.
May  9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
May  9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on 
MetaDisplay 0x555ad20ba000.

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

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Severe performance degradation in Gnome Shell after upgrade to 20.04 -
  everything is slow, even moving the mouse through a right-click menu
  has a severely delayed selection animation.

  Video displaying the problem: https://drive.google.com/open?id=1rAKN-
  ZKks6o9d37hQMbnMgNeAOy8VZyp

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:57:02 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1178 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago)

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

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

[Desktop-packages] [Bug 1877712] [NEW] Severe performance degradation in Gnome Shell after upgrade to 20.04

[Vadim Peretokin]

Public bug reported:

Severe performance degradation in Gnome Shell after upgrade to 20.04 -
everything is slow, even moving the mouse through a right-click menu has
a severely delayed selection animation.

Video displaying the problem: https://drive.google.com/open?id=1rAKN-
ZKks6o9d37hQMbnMgNeAOy8VZyp

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May  9 08:57:02 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1178 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Severe performance degradation in Gnome Shell after upgrade to 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Severe performance degradation in Gnome Shell after upgrade to 20.04 -
  everything is slow, even moving the mouse through a right-click menu
  has a severely delayed selection animation.

  Video displaying the problem: https://drive.google.com/open?id=1rAKN-
  ZKks6o9d37hQMbnMgNeAOy8VZyp

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:57:02 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1178 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago)

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

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

[Desktop-packages] [Bug 1865975] Re: Blank 'Updates' screen

[Vadim Peretokin]

Hi! Attached is the log of when it happened again.

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+attachment/5340338/+files/log.txt

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

Title:
  Blank 'Updates' screen

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  The software updater keeps interrupting me with "updates available"
  and then shows me a blank screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10.19.10.0
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Mar  4 06:40:21 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2902 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
   gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago)

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

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

[Desktop-packages] [Bug 1865975] Re: Blank 'Updates' screen

[Vadim Peretokin]

It showed an error message this time around - attached screenshot.

** Attachment added: "Selection_211.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1865975/+attachment/5340339/+files/Selection_211.png

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

Title:
  Blank 'Updates' screen

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  The software updater keeps interrupting me with "updates available"
  and then shows me a blank screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10.19.10.0
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Mar  4 06:40:21 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2902 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
   gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago)

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

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

[Desktop-packages] [Bug 1867758] Re: Gnome shell froze completely

[Vadim Peretokin]

1. _usr_bin_gnome-screensaver crashed on the 16th, which is a day before
this report. That crash was uploaded. _usr_bin_gnome-shell.1000 also
crashes on the 11th, that was uploaded as well.

2. I've uninstalled everything I could, will see if it happens again. I
just had the freeze happen now while extensions were still installed.

** Attachment added: "Screenshot_2020-03-19 Installed Extensions - GNOME Shell 
Extensions.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+attachment/5338729/+files/Screenshot_2020-03-19%20Installed%20Extensions%20-%20GNOME%20Shell%20Extensions.png

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

Title:
  Gnome shell froze completely

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell froze completely and would not respond to any mouse clicks
  or keyboard action. The mouse did move, but that's about it. It stayed
  this way for ~15mins before I reset it and lost all my work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 11:51:50 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

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

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

[Desktop-packages] [Bug 1867758] Re: Gnome shell froze completely

[Vadim Peretokin]

Attached is a video of what happened:
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1867758/+attachment/5337919/+files/Gnome%20Shell%20freeze.mp4

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

Title:
  Gnome shell froze completely

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome shell froze completely and would not respond to any mouse clicks
  or keyboard action. The mouse did move, but that's about it. It stayed
  this way for ~15mins before I reset it and lost all my work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 11:51:50 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

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

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

[Desktop-packages] [Bug 1867758] [NEW] Gnome shell froze completely

[Vadim Peretokin]

Public bug reported:

Gnome shell froze completely and would not respond to any mouse clicks
or keyboard action. The mouse did move, but that's about it. It stayed
this way for ~15mins before I reset it and lost all my work.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 17 11:51:50 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1126 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Gnome Shell freeze.mp4"
   
https://bugs.launchpad.net/bugs/1867758/+attachment/5337919/+files/Gnome%20Shell%20freeze.mp4

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

Title:
  Gnome shell froze completely

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome shell froze completely and would not respond to any mouse clicks
  or keyboard action. The mouse did move, but that's about it. It stayed
  this way for ~15mins before I reset it and lost all my work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 11:51:50 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

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

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

[Desktop-packages] [Bug 1866004] Re: Correct password does not unlock computer

[Vadim Peretokin]

Right-clicking on the password field doesn't show me a menu :(

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

Title:
  Correct password does not unlock computer

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Every once in a while the lock screen will stop accepting the correct
  password, and I lose all my open work.

  I do have two input methods installed, but toggling between them on
  the lock screen does not work.

  I am able to go back to the main login screen and enter the password
  there, but then it simply takes me back to the lock screen.

  Happy to add any additional information!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 09:46:22 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (17 days ago)

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

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

[Desktop-packages] [Bug 1866004] [NEW] Correct password does not unlock computer

[Vadim Peretokin]

Public bug reported:

Every once in a while the lock screen will stop accepting the correct
password, and I lose all my open work.

I do have two input methods installed, but toggling between them on the
lock screen does not work.

I am able to go back to the main login screen and enter the password
there, but then it simply takes me back to the lock screen.

Happy to add any additional information!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  4 09:46:22 2020
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1112 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-02-15 (17 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Correct password does not unlock computer

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Every once in a while the lock screen will stop accepting the correct
  password, and I lose all my open work.

  I do have two input methods installed, but toggling between them on
  the lock screen does not work.

  I am able to go back to the main login screen and enter the password
  there, but then it simply takes me back to the lock screen.

  Happy to add any additional information!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 09:46:22 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (17 days ago)

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

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

[Desktop-packages] [Bug 1865975] [NEW] Blank 'Updates' screen

[Vadim Peretokin]

Public bug reported:

The software updater keeps interrupting me with "updates available" and
then shows me a blank screen.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.0
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Mar  4 06:40:21 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2902 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago)

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


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "Selection_450.png"
   
https://bugs.launchpad.net/bugs/1865975/+attachment/5333259/+files/Selection_450.png

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

Title:
  Blank 'Updates' screen

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The software updater keeps interrupting me with "updates available"
  and then shows me a blank screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10.19.10.0
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Mar  4 06:40:21 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2902 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
   gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to eoan on 2019-11-07 (117 days ago)

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

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

[Desktop-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland

[Vadim Andreyev]

Still not fixed in 2020. Gnome-shell and Wayland = Wacom cursor
dissapears.

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

Title:
  wacom invisible mouse pointer in wayland

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
  which has touch and pen functionality.

  Controlling the mouse pointer through the touch functionality seems to
  work fine, but using the stylus produced very strange behaviour,
  depending the program.

  - With Firefox there there are two pointers - one that is moving in
  accordance with the stylus movements, and one stays put at the
  position, when the stylus movement was detected.

  - With Darktable the mouse pointer becomes invisible, once it's moved
  inside of the application window (it registers clicks though). Once
  the pointer is moved outside of the application window, it appears
  again.

  I'm running Ubuntu inside of a wayland session.

  libwacom2: 0.24-1

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

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

[Desktop-packages] [Bug 1856648] [NEW] Software centre display is blank

[Vadim Peretokin]

Public bug reported:

Software centre disrupts my workflow with an urgent notification for
"important" updates, yet when I click 'View', it shows nothing.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10.19.10.0
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Dec 17 06:27:49 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2824 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
 gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
SourcePackage: gnome-software
UpgradeStatus: Upgraded to eoan on 2019-11-07 (39 days ago)

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


** Tags: amd64 apport-bug eoan third-party-packages

** Attachment added: "2019-12-17_06-28.png"
   
https://bugs.launchpad.net/bugs/1856648/+attachment/5313155/+files/2019-12-17_06-28.png

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

Title:
  Software centre display is blank

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Software centre disrupts my workflow with an urgent notification for
  "important" updates, yet when I click 'View', it shows nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10.19.10.0
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Dec 17 06:27:49 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2824 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu10.19.10.0
   gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to eoan on 2019-11-07 (39 days ago)

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

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

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

[Vadim Nevorotin]

18.10, bug is still here! It's a very basic experience - Ubuntu with
Gnome3 can't make even such simple basic things work! What can we say
about other things, if user can't change keyboard layout in  a proper
way?

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in GNOME Settings Daemon:
  Unknown
Status in Ubuntu Flashback:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in Ubuntu GNOME Flashback:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Unknown
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a combination of two modifier keys such as Ctrl+Shift
  -> the UI should reflect the new keys

  - add at least two input sources through gnome-control-center's text entry
    settings
  - press and release Ctrl+Shift
  -> the current input source should change

  [Regression Potential]

  That UI was not working before, it should only be an improvement (some
  key combos are not working as expected, that's another issue and
  shouldn't be mixed with this one)

  The input switching shortcut might capture other non-modifier
  shortcuts, but users will need to consider this when choosing their
  switching shortcut anyways. For users this bug affects, this
  represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  You can use the tag keyboard-layout-switching-hotkeys to find related bugs.
  
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys

  For using layout switching hotkeys in Unity Greeter, see bug 1245137.
  For using layout switching hotkeys in GNOME lockscreen, see bug 1244548.
  For using layout switching hotkeys in GNOME FlashBack sessions, see bug 
1687466 (at least ).

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions

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

[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

[Vadim Peretokin]

Sorry but this bug report is not for discussion on the best flavour of
Ubuntu - please ask on the forums and don't spam everyone involved in
the discussion.

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

[Vadim Peretokin]

Second time does not work for me - neither the third, nor the tenth.
Once I lock the screen, there is a chance the GNOME environment will
reject all password attempts to lock it and I have to lose all my work
by forcing a restart. This is a very serious problem.

Is there a workaround available?

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1771068] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Vadim Peretokin]

Public bug reported:

Trying to install winehq-staging from the Wine APT repository on Ubuntu
17.10 yields this error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-42.47-generic 4.13.16
Uname: Linux 4.13.0-42-generic x86_64
NonfreeKernelModules: sep4_1 socperf2_0 pax
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Mon May 14 09:25:17 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-va4Lad/20-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-02-15 (452 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Trying to install winehq-staging from the Wine APT repository on
  Ubuntu 17.10 yields this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-42.47-generic 4.13.16
  Uname: Linux 4.13.0-42-generic x86_64
  NonfreeKernelModules: sep4_1 socperf2_0 pax
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Mon May 14 09:25:17 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-va4Lad/20-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-02-15 (452 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1769298] [NEW] Unlock screen does not accept correct password

[Vadim Peretokin]

Public bug reported:

The unlock screen that you get after locking the computer will sometimes
not accept the correct password. If I switch to tty1 I can login with
the same, correct password fine and if I reboot the computer (lose all
my open apps and unsaved data), the password works fine as well.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: sep4_1 socperf2_0 pax nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 07:11:57 2018
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2233 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Unlock screen does not accept correct password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The unlock screen that you get after locking the computer will
  sometimes not accept the correct password. If I switch to tty1 I can
  login with the same, correct password fine and if I reboot the
  computer (lose all my open apps and unsaved data), the password works
  fine as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: sep4_1 socperf2_0 pax nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 07:11:57 2018
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2233 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1735666] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Vadim Peretokin]

Public bug reported:

This popped up out of the blue.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 23 10:10:49 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2012-03-23 (2078 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This popped up out of the blue.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Thu Nov 23 10:10:49 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2012-03-23 (2078 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

You can also do all of the commands from the rescue mode.

What is concerning is that this major issue is still left untouched. Is
there anything we can do to help?

On Sun, 5 Nov 2017, 10:05 pm William Haverstock, 
wrote:

> I had the blank screen, no login screen problem.
>
> The computer was otherwise running though.
>
> I ssh-ed from another computer to the problem computer
> to execute the suggested commands.
>
> If on a home network you can login to your router with a
> web browser to get the IP address for your problem computer.
>
> Mine was 192.168.1.3
>
> The following fixed the problem for me.
>
> First I did (without the comment).
>
>   sudo apt-get install lightdm # This showed lightdm was installed
>
> Second I did uname -r and found the completion for
> the linux-headers-$(uname -r) command.
>
> I don't know why I didn't use the suggested:
> sudo apt install linux-headers-$(uname -r)
>
> Then I did the suggested commands, one after the other:
>   sudo apt purge gdm3
>   sudo apt purge nvidia*
>   sudo apt install linux-headers-4.13.0-16-generic # ADJUST THIS
>   sudo apt install nvidia-384
>   sudo dpkg-reconfigure lightdm # Suggested when 1st command ran
>   sudo shutdown -r now  # Restart
>
> Went to the problem computer, the login screen came up.
>
> The Desktop Environment that was selected was:
>   Ubuntu on Xorg(Default)
>
> I was able to login.
>
> My problem computer is at least 10 years old.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

-- 
Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

Hmm. What I did was load into recovery mode which allowed me to install and
uninstall packages - there I uninstalled lightgdm and ran the suggested
dpkg-config command to setup gdm.

On Sat, Nov 4, 2017 at 4:11 PM Bernadette Addison 
wrote:

> none of the workarounds or suggestions here work for me.  It is an
> impossible task getting nvidia drivers to work even when only using
> XORG/ X11 services and NOT wayland.  I will keep looking for answers...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1728424] [NEW] Calendar is not respecting 12hour setting

[Vadim Peretokin]

Public bug reported:

I have Ubuntu set to show time as 12hours yet the calendar is using 24
hours, which is uncomfortable.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 29 14:53:21 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2045 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Workspace 1_228.png"
   
https://bugs.launchpad.net/bugs/1728424/+attachment/4999556/+files/Workspace%201_228.png

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

Title:
  Calendar is not respecting 12hour setting

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I have Ubuntu set to show time as 12hours yet the calendar is using 24
  hours, which is uncomfortable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Oct 29 14:53:21 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2045 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

The VM would be using VirtualBox drivers, not NVIDIA - so I don't think
your problem is related!

On Sun, 29 Oct 2017, 4:45 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Thanks! Ran that on a VM as a test. I wound up with a text-based login
> shell, no greeter. "sudo apt install lightdm" fixed that, but my VM may
> not have been in a totally clean state.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

sudo apt purge gdm3
sudo apt purge nvidia*
sudo apt install linux-headers-$(uname -r)
sudo apt install nvidia-384

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

-- 
Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

See the steps we've already posted to alleviate the issue. Remove gdm

On Sat, 28 Oct 2017, 11:00 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Sorry to spam the comments, there's no edit feature. Once again I have a
> black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
> get to a shell. How do I troubleshoot this?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

-- 
Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

That did not work for me. I had to uninstall gdm3 completely in order to be
able to even get a login screen up.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1726272] [NEW] Doesn't display any software

[Vadim Peretokin]

Public bug reported:

No software is loaded at all. I can't search for new software or view
existing software - the tool is a brick. See video for proof.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-software 3.22.7-0ubuntu3.17.04.5
Uname: Linux 4.9.45-040945-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Oct 23 08:57:51 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (249 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: Upgraded to zesty on 2017-05-24 (151 days ago)

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


** Tags: amd64 apport-bug third-party-packages zesty

** Attachment added: "Kazam_screencast_00022.mp4"
   
https://bugs.launchpad.net/bugs/1726272/+attachment/4987265/+files/Kazam_screencast_00022.mp4

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

Title:
  Doesn't display any software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  No software is loaded at all. I can't search for new software or view
  existing software - the tool is a brick. See video for proof.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-software 3.22.7-0ubuntu3.17.04.5
  Uname: Linux 4.9.45-040945-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Oct 23 08:57:51 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-05-24 (151 days ago)

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

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

[Desktop-packages] [Bug 1725734] [NEW] Indicator size is too small

[Vadim Peretokin]

Public bug reported:

The indicator size in 17.10 is too small to be comfortable:

https://i.stack.imgur.com/r5Eza.png

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 17:28:50 2017
DisplayManager: lightdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Indicator size is too small

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The indicator size in 17.10 is too small to be comfortable:

  https://i.stack.imgur.com/r5Eza.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 17:28:50 2017
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (2037 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725641] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit st

[Vadim Peretokin]

Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
AptOrdering:
 libdb5.3:amd64: Configure
 multiarch-support:amd64: Configure
 libobs0:amd64: Install
 obs-plugins:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 21 10:13:28 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
  finally managed to login.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  AptOrdering:
   libdb5.3:amd64: Configure
   multiarch-support:amd64: Configure
   libobs0:amd64: Install
   obs-plugins:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 10:13:28 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-03-23 (2037 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1712862] [NEW] VPN auto-connection does not work at login

[Vadim Peretokin]

Public bug reported:

I've setup the VPN to autoconnect on login. When I log in, the
connection keeps failing to establish. If I disconnect from the network
it's trying to connect to and click connect manually, it is able to
connect to the network and the VPN straight away.

Essentially, every time I log in I have to manually disconnect and
reconnect to a network - and the autoconnecting bit fails to do its job.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Aug 24 18:01:01 2017
EcryptfsInUse: Yes
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-23 (1979 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-06-24 (61 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug zesty

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

Title:
  VPN auto-connection does not work at login

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've setup the VPN to autoconnect on login. When I log in, the
  connection keeps failing to establish. If I disconnect from the
  network it's trying to connect to and click connect manually, it is
  able to connect to the network and the VPN straight away.

  Essentially, every time I log in I have to manually disconnect and
  reconnect to a network - and the autoconnecting bit fails to do its
  job.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug 24 18:01:01 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-03-23 (1979 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-06-24 (61 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 259698] Re: pptp vpn service stops unexpectedly

[vadim]

I'm using 16.04 Xubuntu. I.ve installed it on my new computer and I can't 
connect to VPN. Later I used to connect to that VPN from my old pc with 14.04 
Xubuntu and everything was ok.
Attached syslog from my 16.04 machine.

** Attachment added: "syslog dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/259698/+attachment/4787785/+files/syslog%20dump.txt

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

Title:
  pptp vpn service stops unexpectedly

Status in pptp-linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pptp-linux

  Using ubuntu 8.10 x86.

  pptp-linux version 1.7.2-1

  When I select the vpn option, I can create the VPN configuration, but
  after trying to connect for around ~1 second, I get the popup error:

  "The VPN connection 'Warwick' failed because the VPN service stopped
  unexpectedly."

  Im not entirely sure how to execute the connection via command line,
  so I cant work out how to get any more info on what is going on.

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

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

[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown

[Vadim Andryuschenko]

Mark, thanks for such detailed explanation and extremely fast response!
It's grave news for me to hear that X11 is the major problem here. Would
it be better if your publish it in Ubuntu FAQ (or elsewhere) and close
all these bugs with "won't fix" to make community realize the point?

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

Title:
  Desktop contents displayed on resume, before lock screen is shown

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  I am running 14.04. When I resume from sleep, the contents of my
  desktop (including any open windows, emails, etc) are displayed
  onscreen briefly before the unlock screen is shown. This potentially
  allows an attacker to view the contents of a locked screen.

  To reproduce:
  1) Suspend a machine, e.g. by closing the lid
  2) Resume the machine

  Expected results:
  Upon resume, the first thing shown onscreen is the screensaver unlock screen.

  Actual results:
  Upon resume, the first thing shown onscreen is the set of open windows that 
were displayed before the machine was put to sleep. After a second or two, the 
unlock screen is drawn and you have to enter a password to unlock the machine.

  This is reproducible on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 14 09:05:50 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2013-12-02 (73 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago)

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

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

[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown

[Vadim Andryuschenko]

seth-arnold, imho, this problem systematically reported in different
versions of Ubuntu with different desktop environments and seems like
ignored by developers. The security threat is severe and the root of the
problem lies much deeper than patching a concrete combination of
components. Confess I don't know and not going to investigate the
problem (despite that as sw developer I do want to hear about it
causes), but could you as a member of security team explain us why don't
you refactor or redesign this? And we as system users would be pleased
if some techguy investigate the problem and open a new "correct" bug
instead of switching bug to invalid state practically sinking it to the
"garbage pit".

There is no offence in my comment, but for many reasons lots of people
can't use OSes with such security holes and this is very disappointing.

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

Title:
  Desktop contents displayed on resume, before lock screen is shown

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  I am running 14.04. When I resume from sleep, the contents of my
  desktop (including any open windows, emails, etc) are displayed
  onscreen briefly before the unlock screen is shown. This potentially
  allows an attacker to view the contents of a locked screen.

  To reproduce:
  1) Suspend a machine, e.g. by closing the lid
  2) Resume the machine

  Expected results:
  Upon resume, the first thing shown onscreen is the screensaver unlock screen.

  Actual results:
  Upon resume, the first thing shown onscreen is the set of open windows that 
were displayed before the machine was put to sleep. After a second or two, the 
unlock screen is drawn and you have to enter a password to unlock the machine.

  This is reproducible on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 14 09:05:50 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2013-12-02 (73 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago)

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

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

[Desktop-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Vadim Peretokin]

Yep, already have ran into that problem - rebooted and had no internet
due to NM repeatedly crashing. This is a severe issue.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged

Bug description:
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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

[Desktop-packages] [Bug 1540014] [NEW] NetworkManager crashes over and over again, and does not launch

[Vadim Peretokin]

Public bug reported:

I did the kernel updates this morning, restarted my computer, and had no
internet. Tried using an older kernel version, manually starting
NetworkManager, all the things - nothing works, there is no internet.

All NetworkManager is doing is crashing repeatedly and that's about it:

Jan 31 09:38:07 gooseberry ModemManager[3692]:   ModemManager (version 
1.0.0) starting...
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3699]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.385758] do_general_protection: 1 
callbacks suppressed
Jan 31 09:38:07 gooseberry kernel: [  161.385761] traps: NetworkManager[3699] 
general protection ip:469fee sp:7ffc1d7ddfc0 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.460737] init: network-manager main 
process (3699) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.460749] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3707]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.469470] traps: NetworkManager[3707] 
general protection ip:469fee sp:7ffdedbe8250 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.543303] init: network-manager main 
process (3707) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.543324] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3712]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.549176] traps: NetworkManager[3712] 
general protection ip:469fee sp:7fff0dc74c20 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.626148] init: network-manager main 
process (3712) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.626169] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3717]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.635031] traps: NetworkManager[3717] 
general protection ip:469fee sp:7fff5abe7ba0 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.711343] init: network-manager main 
process (3717) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.711364] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3722]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.717615] traps: NetworkManager[3722] 
general protection ip:469fee sp:7ffcad607d80 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.796157] init: network-manager main 
process (3722) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.796179] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3727]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.805741] traps: NetworkManager[3727] 
general protection ip:469fee sp:7ffd48e64d40 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.882233] init: network-manager main 
process (3727) killed by SEGV signal
Jan 31 09:38:07 gooseberry kernel: [  161.882247] init: network-manager main 
process ended, respawning
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  NetworkManager (version 
0.9.8.8) is starting...
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  Read config file 
/etc/NetworkManager/NetworkManager.conf
Jan 31 09:38:07 gooseberry NetworkManager[3732]:  WEXT support is enabled
Jan 31 09:38:07 gooseberry kernel: [  161.887065] traps: NetworkManager[3732] 
general protection ip:469fee sp:7ffe912d5d70 error:0 in 
NetworkManager[40+10d000]
Jan 31 09:38:07 gooseberry kernel: [  161.960756] init: network-

[Desktop-packages] [Bug 1527884] Re: Firefox 43.0: Downloads fail

[Vadim Shlyakhov]

That's possibly related to
https://bugzilla.mozilla.org/show_bug.cgi?id=1233434 (Linux: temporary
download directory is not created specifically for each user).

** Bug watch added: Mozilla Bugzilla #1233434
   https://bugzilla.mozilla.org/show_bug.cgi?id=1233434

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

Title:
  Firefox 43.0: Downloads fail

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  My firefox just got updated to 43.0. Starting with the update, all
  downloads fail. There is no file selection dialogue any more, just the
  blue arrow appears - and the downloads list says "Failed". I have
  tried the same on a clean profile with no add-ons, and downloads still
  fail.

  In the browser console, I get the following error message on each download 
attempt:
  [Exception... "Component returned failure code: 0x80070057 
(NS_ERROR_ILLEGAL_VALUE) [nsIAnnotationService.setPageAnnotation]"  nsresult: 
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: 
resource://app/modules/DownloadsCommon.jsm :: onDownloadChanged :: line 735"  
data: no]

  Steps to reproduce:
  Klick on any downloadable file on a website (e.g. ZIP oder PDF).

  Result:
  Blue arrow appears, downloads list says "failed" below the download filename. 
The file will not download.

  Expected result:
  File dialogue (with appropriate settings). File being downloaded from the 
internet.

  Versions:
  Kubuntu 14.04.3 LTS
  Firefox 43.0+build1-0ubuntu0.14.04.1

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

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

[Desktop-packages] [Bug 1527884] Re: Firefox 43.0: Downloads fail

[Vadim Shlyakhov]

As a workaround you could try chmod 0777 /tmp/mozilla_mozillaUser0

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

Title:
  Firefox 43.0: Downloads fail

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  My firefox just got updated to 43.0. Starting with the update, all
  downloads fail. There is no file selection dialogue any more, just the
  blue arrow appears - and the downloads list says "Failed". I have
  tried the same on a clean profile with no add-ons, and downloads still
  fail.

  In the browser console, I get the following error message on each download 
attempt:
  [Exception... "Component returned failure code: 0x80070057 
(NS_ERROR_ILLEGAL_VALUE) [nsIAnnotationService.setPageAnnotation]"  nsresult: 
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: 
resource://app/modules/DownloadsCommon.jsm :: onDownloadChanged :: line 735"  
data: no]

  Steps to reproduce:
  Klick on any downloadable file on a website (e.g. ZIP oder PDF).

  Result:
  Blue arrow appears, downloads list says "failed" below the download filename. 
The file will not download.

  Expected result:
  File dialogue (with appropriate settings). File being downloaded from the 
internet.

  Versions:
  Kubuntu 14.04.3 LTS
  Firefox 43.0+build1-0ubuntu0.14.04.1

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

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

[Desktop-packages] [Bug 1517222] [NEW] Additional monitor does not always come online anymore after suspend

[Vadim Peretokin]

Public bug reported:

I've got an external monitor plugged in via DisplayPort that always used
to come online in Ubuntu 15.04 after I resumed the laptop from suspend.
In 15.10 however, the monitor will often just stay black and it takes me
re-plugging the cable to bring the picture back on it.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Nov 18 07:26:39 2015
DistUpgraded: 2015-10-27 08:48:20,176 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.8, 4.2.0-17-generic, x86_64: installed
 vboxhost, 5.0.8, 4.2.0-18-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev 
ff) (prog-if ff)
InstallationDate: Installed on 2014-06-26 (508 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 14
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-10-26 (21 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU424B3ZZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 14
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Nov 16 07:38:53 2015
xserver.configfile: default
xserver.errors:
 RADEON(G0): [XvMC] Failed to initialize extension.
 intel(0): failed to set mode: Invalid argument [22]
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4925 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

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

Title:
  Additional monitor does not always come online anymore after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I've got an external monitor plugged in via DisplayPort that always
  used to come online in Ubuntu 15.04 after I resumed the laptop from
  suspend. In 15.10 however, the monitor will often just stay black and
  it takes me re-plugging the cable to bring the picture back on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Nov 18 07:26:39 2015
  DistUpgraded: 2015-10-27 08:48:20,176 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.8, 4.2.0-17-generic, x86_64: installed
   vboxhost, 5.0.8, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics C

[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Vadim Nevorotin]

Should be hight priority bug. A lot of input fields have some behaviour
for loosing focus. E.g. search field in gedit disappear when changing
keyboard layout, guake with autohide is unusable because of this bug, a
lot of web applications have problems etc. In fact, now there are a lot
of annoying problems with using two or more layouts in Ubuntu, so
comfortable work in system is impossible. If such bugs in desktop
components haven't hight priority, which should have it?

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in gnome-settings-daemon:
  Confirmed
Status in Project Hamster:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Fedora:
  Unknown
Status in gnome-settings-daemon package in openSUSE:
  Won't Fix

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions

-- 
Mailing list: https://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 1431753] Please test proposed package

[Vadim Peretokin]

Hi John,

I think that after you add the repository, just doing an update will
install the updated new packages.

On Fri, Jul 24, 2015 at 10:46 AM, John Feole <1431...@bugs.launchpad.net>
wrote:

> Hi Adam,
>
> I've never used this -proposed repo and had a coupla questions..(my son son
> Sean Feole works for Canonical as well)
>
> I've been using Ubuntu for work/home use since 2006 or so when i was at Sun
> and heard about it via Solaris Engineering...
>
> Anyway, I enabled the -proposed  repo, and I see a lot of stuff.  My
> question is, can I deselect all the other stuff and only load the NVIDIA
> 346 stuff?  Guess my real question is, what stuff do I need to install to
> rectify this NVIDIA bug..?
>
> Thank You,
> John Feole
>
> On Thu, Jul 23, 2015 at 4:15 PM, Adam Conrad  wrote:
>
> > Hello Stefan, or anyone else affected,
> >
> > Accepted nvidia-graphics-drivers-340 into trusty-proposed. The package
> > will build now and be available at https://launchpad.net/ubuntu/+source
> > /nvidia-graphics-drivers-340/340.76-0ubuntu0.1 in a few hours, and then
> > in the -proposed repository.
> >
> > Please help us by testing this new package.  See
> > https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> > enable and use -proposed.  Your feedback will aid us getting this update
> > out to other Ubuntu users.
> >
> > If this package fixes the bug for you, please add a comment to this bug,
> > mentioning the version of the package you tested, and change the tag
> > from verification-needed to verification-done. If it does not fix the
> > bug for you, please add a comment stating that, and change the tag to
> > verification-failed.  In either case, details of your testing will help
> > us make a better decision.
> >
> > Further information regarding the verification process can be found at
> > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> > advance!
> >
> > ** Changed in: nvidia-graphics-drivers-340-updates (Ubuntu Trusty)
> >Status: Confirmed => Fix Committed
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1431753
> >
> > Title:
> >   Nvidia binary driver FTBS due to DKMS layer violation
> >
> > Status in nvidia-graphics-drivers-331 package in Ubuntu:
> >   Confirmed
> > Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
> >   Confirmed
> > Status in nvidia-graphics-drivers-340 package in Ubuntu:
> >   Fix Released
> > Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
> >   Fix Released
> > Status in nvidia-graphics-drivers-346 package in Ubuntu:
> >   Fix Released
> > Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
> >   Fix Released
> > Status in nvidia-graphics-drivers-331 source package in Trusty:
> >   Triaged
> > Status in nvidia-graphics-drivers-331-updates source package in Trusty:
> >   Triaged
> > Status in nvidia-graphics-drivers-340 source package in Trusty:
> >   Fix Committed
> > Status in nvidia-graphics-drivers-340-updates source package in Trusty:
> >   Fix Committed
> > Status in nvidia-graphics-drivers-346 source package in Trusty:
> >   Fix Committed
> > Status in nvidia-graphics-drivers-346-updates source package in Trusty:
> >   Fix Committed
> >
> > Bug description:
> >   Filing this against the 340-updates version but possibly the same
> >   applies to older versions, too. The nvidia source package produces two
> >   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
> >   The problem is that the DKMS build of the nvidia-uvm module runs
> >   compile steps inside the nvidia modules build directory. This is
> >   violating the DKMS assumption that each module can be build
> >   independently (there is no way of describing cross-modules
> >   dependencies and even more important, the autoinstall step after a new
> >   kernel is installed will run the modules build in parallel).
> >
> >   Since nvidia and nvidia-uvm are very dependent on each other the right
> >   course of action seems to be to combine both sources in one DKMS
> >   module that produces two kernel modules (this is supported by DKMS).
> >   For the transition this resulting dkms package needs to have a
> >   breaks/replaces for the nvidia-uvm package.
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1412105).
> https://bugs.launchpad.net/bugs/1431753
>
> Title:
>   Nvidia binary driver FTBS due to DKMS layer violation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in 

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

[Vadim Peretokin]

Can you guys not litter the bug report?

On Fri, Jun 19, 2015 at 6:18 AM, Kristian Erik Hermansen <
kristian.herman...@gmail.com> wrote:

> Just use Debian. No one considers Ubuntu secure any more after the privacy
> violations embedded by Canonical.
>
> On Thu, Jun 18, 2015 at 12:41 PM rbscy...@yahoo.ca 
> wrote:
>
> > That may be so.  However, I care.  I use Linux as my everyday computer
> > at home for everything.  I use the "LTS" version because I expect less
> > problems, and don't really know a hell-of-a-lot about the "underneath"
> > workings of Linux.  If this means I have to go to another distribution,
> > so be it.
> >
> >
> > On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote:
> > > No vendor cares about linux
> > > On Thu, Jun 18, 2015 at 11:46 AM Heath  wrote:
> > >
> > >> This seems to me like a trivial bug fix, is this just nVidia not
> wanting
> > >> to devote time to a fix?
> > >>
> > >> --
> > >> You received this bug notification because you are subscribed to a
> > >> duplicate bug report (1405694).
> > >> https://bugs.launchpad.net/bugs/1431753
> > >>
> > >> Title:
> > >>Nvidia binary driver FTBS due to DKMS layer violation
> > >>
> > >> To manage notifications about this bug go to:
> > >>
> > >>
> >
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
> > >>
> >
> > --
> >
> >
> > ** Attachment added: "ronnie6.png"
> >
> >
> https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1405694).
> > https://bugs.launchpad.net/bugs/1431753
> >
> > Title:
> >   Nvidia binary driver FTBS due to DKMS layer violation
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1412105).
> https://bugs.launchpad.net/bugs/1431753
>
> Title:
>   Nvidia binary driver FTBS due to DKMS layer violation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

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

[Desktop-packages] [Bug 1430068] [NEW] Unable to launch gnome-system-monitor

[Vadim Peretokin]

Public bug reported:

When you have too many open files, you can't launch gnome-system-
monitor:

 $ gnome-system-monitor

(gnome-system-monitor:23720): glibmm-CRITICAL **: 
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local directory monitor type


(gnome-system-monitor:23720): Gtk-CRITICAL **: gtk_window_present_with_time: 
assertion 'GTK_IS_WINDOW (window)' failed

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gnome-system-monitor 3.8.2.1-2ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 10 09:32:12 2015
InstallationDate: Installed on 2014-06-26 (255 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: gnome-system-monitor
UpgradeStatus: Upgraded to utopic on 2014-10-27 (133 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Unable to launch gnome-system-monitor

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

Bug description:
  When you have too many open files, you can't launch gnome-system-
  monitor:

   $ gnome-system-monitor

  (gnome-system-monitor:23720): glibmm-CRITICAL **: 
  unhandled exception (type Glib::Error) in signal handler:
  domain: g-io-error-quark
  code  : 0
  what  : Unable to find default local directory monitor type

  
  (gnome-system-monitor:23720): Gtk-CRITICAL **: gtk_window_present_with_time: 
assertion 'GTK_IS_WINDOW (window)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-system-monitor 3.8.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 09:32:12 2015
  InstallationDate: Installed on 2014-06-26 (255 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (133 days ago)

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

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

[Desktop-packages] [Bug 1412105] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build

[Vadim Peretokin]

Public bug reported:

Happened while upgrading.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-45-generic
Date: Sun Jan 18 14:35:26 2015
InstallationDate: Installed on 2012-03-23 (1030 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
UpgradeStatus: Upgraded to trusty on 2014-07-26 (176 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Happened while upgrading.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-45-generic
  Date: Sun Jan 18 14:35:26 2015
  InstallationDate: Installed on 2012-03-23 (1030 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: Upgraded to trusty on 2014-07-26 (176 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1412105/+subscriptions

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

[Desktop-packages] [Bug 1411382] [NEW] Applications view not displaying any applications

[Vadim Peretokin]

Public bug reported:

See screenshot included. Just broke down out of the blue.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Jan 16 05:42:09 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-03-23 (1028 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-07-26 (173 days ago)

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


** Tags: amd64 apport-bug third-party-packages trusty

** Attachment added: "Workspace 1_127.png"
   
https://bugs.launchpad.net/bugs/1411382/+attachment/4299456/+files/Workspace%201_127.png

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

Title:
  Applications view not displaying any applications

Status in unity package in Ubuntu:
  New

Bug description:
  See screenshot included. Just broke down out of the blue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Jan 16 05:42:09 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-03-23 (1028 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-07-26 (173 days ago)

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

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

[Desktop-packages] [Bug 1410091] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

[vadim]

Public bug reported:

nvidia driver update

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-44-generic
Date: Tue Jan 13 09:52:53 2015
InstallationDate: Installed on 2014-09-07 (127 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  nvidia driver update

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Tue Jan 13 09:52:53 2015
  InstallationDate: Installed on 2014-09-07 (127 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410091/+subscriptions

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