date:20221101

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

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

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

Title:
  Expandable folders option disappeared

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10  nautilus: Installed: 1:43.0-1ubuntu1
  Nautilus click on 'Preferences' Expandable folders option was present in 
Ubuntu 22.04 now disappeared in Ubuntu 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  1 18:54:22 2022
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 
879)'
  InstallationDate: Installed on 2022-10-25 (7 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-share0.7.5-0.1

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


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

[Desktop-packages] [Bug 1995412] [NEW] Expandable folders option disappeared

Public bug reported:

Ubuntu 22.10  nautilus: Installed: 1:43.0-1ubuntu1
Nautilus click on 'Preferences' Expandable folders option was present in Ubuntu 
22.04 now disappeared in Ubuntu 22.10.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  1 18:54:22 2022
GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 
879)'
InstallationDate: Installed on 2022-10-25 (7 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-share0.7.5-0.1

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


** Tags: amd64 apport-bug kinetic

** Attachment added: "expandable folders.png"
   
https://bugs.launchpad.net/bugs/1995412/+attachment/5628325/+files/expandable%20folders.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/1995412

Title:
  Expandable folders option disappeared

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 22.10  nautilus: Installed: 1:43.0-1ubuntu1
  Nautilus click on 'Preferences' Expandable folders option was present in 
Ubuntu 22.04 now disappeared in Ubuntu 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  1 18:54:22 2022
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 
879)'
  InstallationDate: Installed on 2022-10-25 (7 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-share0.7.5-0.1

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


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

[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)

2022-11-01 Thread Tony Martin Berbel

Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7
/etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande 
introuvable
/etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande 
introuvable

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in Light Display Manager:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Desktop-packages] [Bug 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version

2022-11-01 Thread akkount rekover

** Branch unlinked: lp:ubuntu/trusty-proposed/software-properties

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

Title:
  Create Unity Control Center so can remain on old GNOME Control Center
  version

Status in Empathy:
  Fix Released
Status in Eye of GNOME:
  Fix Released
Status in GNOME Color Manager:
  Incomplete
Status in GNOME media utilities:
  Expired
Status in gThumb:
  Fix Released
Status in Nautilus:
  Fix Released
Status in Unity:
  Fix Released
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in compiz package in Ubuntu:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-color-manager package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in gthumb package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in landscape-client package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntuone-control-panel package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in webaccounts-browser-extension package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu/Unity uses GNOME Control Center as the application to configure
  the Unity session. We've made a lot of changes appropriate for Ubuntu
  and Unity (61 patches) which makes it hard to maintain and creates a
  conflict for Ubuntu GNOME to use the control center. Unity 7 will be
  replaced by Unity 8 in the future which has a new settings interface.

  So we can continue to remain on the current version of GNOME Control
  Center but allow Ubuntu GNOME to continue to update we will create a
  new project lp:unity-control-center which is a copy of GNOME Control
  Center 3.6 but with appropriate renaming so both can be installed.

  A number of packages that refer to gnome-control-center need to be
  updated to refer to unity-control-center (see bug tasks).

  A PPA for testing is https://launchpad.net/~ubuntu-
  desktop/+archive/unity-control-center

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


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

[Desktop-packages] [Bug 1995396] Re: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInpu

2022-11-01 Thread Ivan Arsenault

I find a way to remove the « Transparency scrool chooser bar » tested on
my webkit2gtk (2.38.1-1) that I rebuilt with that bar off for now.

ref: https://docs.gtk.org/gtk3/method.ColorChooser.set_use_alpha.html

Check the patch.

Temporary remove that bar solve my problem for now.

Thank you

** Patch added: "remove_alpha_from_color_chooser.patch"
   
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1995396/+attachment/5628322/+files/remove_alpha_from_color_chooser.patch

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

Title:
  /usr/lib/x86_64-linux-
  
gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInputType::didChooseColor:IPC::callMemberFunctionImpl

Status in webkit2gtk package in Ubuntu:
  Confirmed

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

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


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

[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory

You were faster than me on #6, Alexander. :)

> And just to confirm, Google builds from https://download-
chromium.appspot.com (now version 109.0.5396.0) open without issue.

Yes, it is a downstream issue related to the crash pad, which serves no
purpose in our context.

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

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


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

[Desktop-packages] [Bug 1987330] Re: Dock click action "previews" focuses instead

2022-11-01 Thread John Barrett

The option is correctly set, you can see the output of gsettings in the
attached video. Regardless, the issue seems to have spontaneously
resolved itself despite no apparent change to the installed version of
dash-to-dock (apt list still has it at 72~ubuntu5.22.04.1), so I've
marked this bug as Invalid. Thanks for your help.

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

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

Title:
  Dock click action "previews" focuses instead

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

Bug description:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  With the Ubuntu dock click-action set to previews, focusing on one
  program then clicking on the icon of a different program with multiple
  windows focuses the most recently used window from that program
  instead of showing the previews.

  Steps to reproduce:-

  1) Open multiple Terminal windows (or any program I guess, but I used 
Terminal and Firefox for testing)
  2) Open Firefox
  3) Click on the Terminal icon in the dock

  Expected behaviour:

  Previews for all the Terminal windows are shown

  Actual behaviour:

  The most recent Terminal window is focused.

  Additional info:

  Appears to be a regression of #1947445, which was supposedly fixed in
  version 70 but I'm on version 72. I've tried setting the click-action
  via gsettings and by editing /usr/share/glib-2.0/schemas/10_ubuntu-
  dock.gschema.override (as per #1770405) but neither has any effect.

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


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

[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory

2022-11-01 Thread Alexander Browne

And just to confirm, Google builds from https://download-
chromium.appspot.com (now version 109.0.5396.0) open without issue.

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

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


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

[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory

I am aware that my tentative fix (submitted to beta) failed to solve the
issue. But we are getting closer.

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

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


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

[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory

2022-11-01 Thread Alexander Browne

With the latest version just released to the beta channel, revision
2180, I no longer see the "spawn" lines, but it still is not starting
up for me (Ubuntu 22.10). This is all I get:

$ chromium
Trace/breakpoint trap (core dumped)

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

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


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

[Desktop-packages] [Bug 1991263] Re: duplicate appindicators

2022-11-01 Thread Sebastien Bacher

reopening, we are still getting reports of the issue with the most
recent version

** Changed in: gnome-shell-extension-appindicator (Ubuntu Kinetic)
   Status: Fix Released => Triaged

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Jammy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Triaged

Bug description:
  [ Impact ]

  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  [ Test case ]

  From shell point of view:
   - Lock / unlock your desktop multiple times

  With applications (both cases must be fixed):
   1) Electron apps
  - Install ferdium (https://github.com/ferdium/)
  - Open it in guest mode, go to settings
  - Toggle the "Always Show Ferdium in System Tray" option multiple times
  - Once disabled indicators should go away and be added again

   2) KDE Status Notification apps
  - Download Telegram desktop (snap install telegram-desktop)
  - Run it with:
XDG_CURRENT_DESKTOP=KDE Telegram
or
XDG_CURRENT_DESKTOP=KDE telegram-desktop
  - Disable notificationn area icon and enable it again
  - The icon should be hidden and shown again accordingly

  [ Regression potential ]

   - Icon could not show at all or with the wrong content
   - Icon updates may lead to more CPU usage
   - Updated to icon could not be properly visible

  
  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.SourcePackage: 
gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

[Desktop-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2022-11-01 Thread You-Sheng Yang

Hi Jérôme,

Apparently I missed your message as well.

These patches have been included in kernel v5.7, and oem-6.0 has EOL-ed.

** No longer affects: bluez (Ubuntu)

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.0 (Ubuntu Bionic)
   Status: New => Invalid

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

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

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

** Changed in: linux-oem-6.0 (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: linux-oem-6.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-6.0 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-6.0 source package in Focal:
  Won't Fix

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

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


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

[Desktop-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)

2022-11-01 Thread Joseph McKittrick

I have an AMD CPU and my Motherboard has no integrated graphics and I am
still experiencing this problem.

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

Title:
  Can not login after new kernel installed (nvidia driver crashed)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Confirmed
Status in xserver-xorg-video-intel source package in Jammy:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

'Fix Released' is the only supported closed state for upstream bug
tasks, even when an upstream bug is closed without a fix.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri:

[Desktop-packages] [Bug 1814936] Re: chromium-browser fails to start, with message [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3

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

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

Title:
  chromium-browser fails to start, with message
  [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction
  Proxy DB: 3

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in chromium-browser package in Debian:
  New

Bug description:
  EDIT: upstream report at
  https://bugs.chromium.org/p/chromium/issues/detail?id=944295

  ps shows chromium-browser processes are running, but no windows
  appear.

  I've been able to correlate the message
  "[...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction
  Proxy DB: 3" with this failure mode.

  Users are frustrated when it happens to them, and advice online is to
  delete your profile and reboot, which is suboptimal, because it
  removes all bookmarks, history, settings, etc.  I have one user that
  gets this error almost daily, even after workstation swap, so I'm
  guessing there's a behavioral component as well.

  I have confirmed that killing all chromium-browser processes and
  rolling back just $HOME/.config/chromium/Default/Preferences to the
  state it was before a prior successful start is enough to fix the
  issue when it happens to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 71.0.3578.98-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGs6EyAQEBAQgcAQOARid46g8lqFRDliIaUFS/74BxT4GAgQCzAIFAlQCpQNHAVl4AoKCgKVAwIDUAuokhAAAS/QAySx5aGAAKICAgICAg/ABWQTMyQVEKICAgICAg/wBKMkxNQVMwMDExOTQKARECAyXxSpAEAwEUEgUfBxMjCQcHgwEAAG0DDAAQADgxAjqAGHE4LUBYLEUAuokhAAAfVl4AoKCgKVAwIDUAuokhAAAeAR0AclHQHiBuKFUAuokhAAAf1QmAoCDgLRAIYCIAuokhCAgY9A==
   modes: 2560x1440 2560x1440 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080 1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 720x576 720x480 720x480 720x480i 720x480i 
640x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Wed Feb  6 08:45:01 2019
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   
'/usr/share/mate:/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstalledPlugins:

  Load-Avg-1min: 3.04
  Load-Processes-Running-Percent:   0.1%
  MachineType: Shuttle Inc. DX30D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=dc6e336f-c022-11e8-b65f-80ee73d362fb ro
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FDX30
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd02/15/2017:svnShuttleInc.:pnDX30D:pvrV1.0:rvnShuttleInc.:rnFDX30:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: D
  dmi.product.name: DX30D
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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


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

[Desktop-packages] [Bug 1809105] Re: Broken setting custom flags in /usr/bin/chromium-browser script

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

Please let me know if I misunderstood and this isn't a duplicate.

** This bug has been marked a duplicate of bug 1514484
   Chromium start-up script doesn't accept argument values with spaces in 
$CHROMIUM_FLAGS, cause is lack of quotes

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

Title:
  Broken setting custom flags in /usr/bin/chromium-browser script

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  To workaround LP#1808853 (https://bugs.launchpad.net/bugs/1808853) I
  tried to make the following script (/etc/chromium-
  browser/customizations/20-chromium-useragent-fix):

  https://gitlab.com/mikhailnov/nastr/blob/master/chromium-useragent-
  fix.sh

  But it does not work due to probably an error in /usr/bin/chromium-
  browser

  If use an unmodified /usr/bin/chromium-browser, then my scripts leads
  to openning multiple tabs, because --useagent=VALUE is passed as
  multiple arguements, not one.

  I've made a patch:
  --- ./chromium-browser  2018-12-17 04:53:00.0 +0300
  +++ /tmp/chromium-browser   2018-12-19 14:16:29.186960503 +0300
  @@ -207,16 +207,16 @@
     echo "$GDB $LIBDIR/$APPNAME -x $tmpfile"
     $GDB "$LIBDIR/$APPNAME" -x $tmpfile
     if [ $want_temp_profile -eq 1 ] ; then
  -rm -rf $TEMP_PROFILE
  +rm -rf ${TEMP_PROFILE:?}/*
     fi
     exit $?
   else
     if [ $want_temp_profile -eq 0 ] ; then
  -exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
  +exec "$LIBDIR/$APPNAME" "$CHROMIUM_FLAGS" "$@"
     else
   # we can't exec here as we need to clean-up the temporary profile
  -$LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
  -rm -rf $TEMP_PROFILE
  +"$LIBDIR/$APPNAME" "$CHROMIUM_FLAGS" "$@"
  +rm -rf ${TEMP_PROFILE:?}/*
     fi
   fi

  After this multiple pages are not openned, but, if we run
  $ bash -x /usr/bin/chromium-browser
  we see:
  + exec /usr/lib/chromium-browser/chromium-browser ' 
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=32.0.0.101 --user-agent=Mozilla/5.0 (X11; Linux x86_64) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36  
--enable-pinch' https://yandex.ru/internet

  the problem is in ' ', new user-agent is not applied

  If to run manually
  $ /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=32.0.0.101 --user-agent=Mozilla/5.0 (X11; Linux x86_64) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36  
--enable-pinch https://yandex.ru/internet

  then setting a custom useragent does work.

  What can be done?

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


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

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-11-01 Thread Henrik Harmsen

Dear Mr Bug Watch Updater: If you are referring to
https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 then I would like to
inform you that it was closed without fixing and the problem still
remains so please explain in what way the fix is released.

Thanks.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string

[Desktop-packages] [Bug 1990886] Re: Security updates missing after 91.11.0

2022-11-01 Thread Ras

It's starting all over again.

Security issues fixed in 102.3.1, released Sep-28: 
https://www.mozilla.org/en-US/security/advisories/mfsa2022-43/
Security issues fixed in 102.4, released Oct-18: 
https://www.mozilla.org/en-US/security/advisories/mfsa2022-46/

Meanwhile, Olivier started working on 102.3.1 about a full month ago. At
some point in the pipeline, the progress just stalls. The overall
process seems to be too convoluted for a single maintainer to cope with.

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

Title:
  Security updates missing after 91.11.0

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Upstream released Thunderbird 91.11.0 on June 28, 2022.
  It's now at 91.13.1 from September 19, 2022. The release notes say:
  "By popular demand, Thunderbird 91.13.1 contains important security updates 
that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as 
possible."
  Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/

  Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird 
91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after 
91.11.0.
  The package should be updated to 91.13.1.

  Given that it has been three months without security updates, there
  seems to be some general friction with following upstream.

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


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

[Desktop-packages] [Bug 1794354] Re: [snap] emoji show as black and white if fonts-symbola is installed

Still an issue? Cannot reproduce in current stable 107.0.5304.87.

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

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

Title:
  [snap] emoji show as black and white if fonts-symbola is installed

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I'm using the Chromium Snap from the Beta channel.

  Test Case
  =
  0. Be sure you don't have the Chromium deb running.
  1. Visit https://launchpad.net/bugs/1779569
  The rainbow emoji  should show in color
  2. sudo apt install fonts-symbola
  3. Close Chromium. Wait a few moments to make sure it closes then open it and 
repeat step 1
  4. The rainbow emoji  shows in black and white

  Other Info
  ==
  Firefox and GTK apps like gedit correctly show  in color as long as 
fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is 
also installed.

  I also was unable to duplicate this bug with the Firefox Snap [edge
  channel 63.0b9-1 (134)].

  System Info
  ===
  Ubuntu 18.10
  fonts-noto-color-emoji 0~20180810-1

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   https://forum.snapcraft.io/
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: beta
  refresh-date: 8 days ago, at 13:41 EDT
  channels:  
stable:69.0.3497.100 (494) 141MB -
candidate: 69.0.3497.100 (494) 141MB -
beta:  70.0.3538.16  (487) 142MB -
edge:  70.0.3538.9   (472) 142MB -
  installed:   70.0.3538.16  (487) 142MB -

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


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

[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

2022-11-01 Thread Brad Woodward

Can confirm that libmutter-10-0/42.5-0ubuntu1 fixed my issue. Thanks for
all your hard work on this!

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  On dual-GPU systems, gnome-shell may crash in
  gbm_surface_release_buffer() during display config changes, like when
  rearranging monitor positions.

  [ Test Plan ]

  1. Find a dual GPU system where both use open source drivers (like Intel + 
AMD).
  2. Ideally also attach one monitor to each GPU.
  3. Open Settings and repeatedly change the monitor layout pressing Apply each 
time.

  Expect: System does not crash.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

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

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


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

[Desktop-packages] [Bug 1764648] Re: Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  2 ways to reproduce:
  1) Go to 
https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html 
and run the all/conformance/reading tests.
  2) Go to photoeditor.polarr.co. Select the Pro workspace. Skip the tutorial. 
Press F to open the filters panel (or click the 3 circle icon on the left). All 
of the filter previews will be garbled or black for any image that you edit.

  I've tried this on 2 computers, one with a 980, and one with a 1070.
  They both fail on Ubuntu 18.04 but work correctly on 16.04 and 17.10.
  Firefox works correctly. I attempted to use the Noveau driver, but I
  got a max resolution of 640p and WebGL didn't work at all so far as I
  could tell.

  I've tried running my Polarr photo editor (an Electron app) on 18.04,
  and it also doesn't work correctly any more.

  This is what I get in the terminal for chromium-browser when I run the WebGL 
conformance tests for reading pixels:
  amiller@amiller-All-Series:~$ chromium-browser 
  [4775:4775:0417/30.985800:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.986559:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987074:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987630:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 00:06:03 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Sat Apr  7 06:58:00 2018)
  Load-Avg-1min: 0.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=a9752952-f843-46f2-9206-e16c858d6d33 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1203
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1203:bd12/10/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.default.chromium-browser: [deleted]

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


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

[Desktop-packages] [Bug 1793738] Re: /usr/lib/chromium-browser/chromium-browser:11:vmw_svga_winsys_query_init:begin_query_vgpu10:svga_begin_query:svga_end_query:st_BeginQuery

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

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

Title:
  /usr/lib/chromium-browser/chromium-
  
browser:11:vmw_svga_winsys_query_init:begin_query_vgpu10:svga_begin_query:svga_end_query:st_BeginQuery

Status in chromium-browser package in Ubuntu:
  Incomplete

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

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


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

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-11-01 Thread Bug Watch Updater

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx:

[Desktop-packages] [Bug 1995396] Re: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInpu

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

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

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

Title:
  /usr/lib/x86_64-linux-
  
gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInputType::didChooseColor:IPC::callMemberFunctionImpl

Status in webkit2gtk package in Ubuntu:
  Confirmed

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

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


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

[Desktop-packages] [Bug 1995396] [NEW] /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorIn

2022-11-01 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: webkit2gtk (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: kinetic

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

Title:
  /usr/lib/x86_64-linux-
  
gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInputType::didChooseColor:IPC::callMemberFunctionImpl

Status in webkit2gtk package in Ubuntu:
  Confirmed

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

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


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

[Desktop-packages] [Bug 1993874] Re: Settings and Quick Menu apply Dark style differently

2022-11-01 Thread Silvano junior

I am also experiencing this bug. I can replicate it by doing the
following

1. Have system set to dark theme
2. Open settings
3. Observe that now Shell theme are in light mode
4. Observe that, in settings, dark theme is still selected
5. Observe that, in the quick panel, dark theme is deactivated
6. Click on dark mode in quick panel
7. Observe that everything is back to dark theme

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

Title:
Settings and Quick Menu apply Dark style differently

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

Bug description:
I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
no longer in Dark mode including gedit/chrome. When setting the style
through the quick menu however, these apps go to Dark mode (presumably
due to gtk theme being applied). Likewise for the quick menu itself,
setting the style to Dark in gnome-control-settings doesn't change it
to dark, it remains light.

see screenshot attached, you will see that when setting the style to
Dark in Settings, gedit and the quick menu remain light. I tried to
logout in case it was an issue with how the settings are applied but
it didn't help. it's also clear that the toggle in the quick menu
works as intended so there seems to be an issue with the way gnome-
control-center applies the Dark style.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 10:21:40 2022
InstallationDate: Installed on 2022-04-06 (198 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

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

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

[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2524

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

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

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

Title:
  WiFi captive portals stopped working after Kinetic upgrade

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer
  recognizes captive portals.

  Attempting to run /usr/libexec/gnome-shell-portal-helper produces this
  output:

  (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS 
module 'fileUtils' found in search path
  @resource:///org/gnome/shell/portalHelper/main.js:13:30
  @:1:14

  
  This may be normal because of the environment, but it is the best I have to 
go on now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 19:26:44 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  InstallationDate: Installed on 2019-08-06 (1179 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago)

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


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

[Desktop-packages] [Bug 1995353] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1995353/+attachment/5628291/+files/monitors.xml.txt

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1995353] Re: Switching between desktops often doesn't work

apport information

** Tags added: apport-collected kinetic third-party-packages wayland-
session

** Description changed:

  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.
  
- Btw I don't see this issue when I select an app in the sidebar thing.
- Then the desktop switch is seamless.
+ Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-08-27 (431 days ago)
+ InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
+ Package: gnome-shell 43.0-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
+ RelatedPackageVersions: mutter-common 43.0-1ubuntu4
+ Tags: third-party-packages kinetic wayland-session
+ Uname: Linux 5.19.0-23-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing. Then 
the desktop switch is seamless.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-08-27 (431 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell 43.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (11 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2022-11-01 Thread Petr

Ubuntu 22.04.1 LTS. I see this bug every day, all the time, and it's
extremely annoying. Impossible to work properly.

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

Title:
  Dock displaying over window after resuming from blank screen

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

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-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/dash-to-dock/+bug/1961508/+subscriptions


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

[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment

2022-11-01 Thread Guilherme Alvarenga

I have the same issue but I can't edit 'detect.py' as other people have
suggested. It is a read-only file and I can't edit it. Any ideas how to
do so? My issue is also that my second and third monitors are mostly
black. Sometimes they work out of nowhere but then it goes out again.

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

Title:
  UnboundLocalError: local variable 'version' referenced before
  assignment

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

Bug description:
  Hello, we received a drive-by complaint about the ubuntu-drivers
  autoinstall tool:

  < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
  < Fhazal> this error appear when i try to auto install recommended driver
  < Fhazal> https://pastebin.com/ydZVFT24

  The contents of the pastebin:

  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  
  Skimming the version on my system it sure feels plausible:

  def nvidia_desktop_pre_installation_hook(to_install):
  '''Applies changes that need to happen before installing the NVIDIA 
drivers'''
  with_nvidia_kms = False

  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
  try:
  version = int(package_name.split('-')[-1])
  except ValueError:
  pass
  finally:
  with_nvidia_kms = version >= 470

  if with_nvidia_kms:
  set_nvidia_kms(1)


  If there was an exception splitting, indexing, or converting to an
  int, that 'version' variable may not have a value.

  Thanks

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


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

[Desktop-packages] [Bug 1995353] Re: Switching between desktops often doesn't work

2022-11-01 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 1995353

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

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

Title:
  Switching between desktops often doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
  When this happens I need to switch desktops again until everything is 
responsive again.

  Btw I don't see this issue when I select an app in the sidebar thing.
  Then the desktop switch is seamless.

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


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

[Desktop-packages] [Bug 1987631] Re: Screencast only records one second

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

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

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


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

[Desktop-packages] [Bug 1993308] Re: Update gnome-calendar to 43.1

This bug was fixed in the package gnome-calendar - 43.1-0ubuntu1

---
gnome-calendar (43.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1993308)
- Fixes multiple issues with recurring events

 -- Jeremy Bicha   Tue, 18 Oct 2022 10:09:27 -0400

** Changed in: gnome-calendar (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-calendar to 43.1

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS

  This includes several fixes for recurring calendar events. These bugs
  were considered a release blocker for Fedora 37.

  https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar

  What Could Go Wrong
  ---
  GNOME Calendar is included by default only in the Ubuntu Desktop flavor.

  If there are bugs in GNOME Calendar, Evolution (not installed by
  default) could be used instead.

  GNOME Calendar can sync with Google or Microsoft online calendars.
  Therefore, bugs in editing calendar events can by synced to those
  services.

  GNOME Calendar is part of GNOME Core and is included in the GNOME
  micro release exception

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

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


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

[Desktop-packages] [Bug 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic

This bug was fixed in the package software-properties - 0.99.27.1

---
software-properties (0.99.27.1) kinetic; urgency=medium

  * softwareproperties/qt/SoftwarePropertiesQt.py: Don't crash if the driver
package does not have a matching modules package (LP: #1993370)

 -- Brian Murray   Wed, 19 Oct 2022 07:38:40 -0700

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio
  Kinetic

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel
  Core i5, UEFI, no secure boot, Broadcom WiFi.

  OS: Ubuntu Studio Kinetic, Final ISO

  Steps to reproduce:

  1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
  2. Reboot and log into the newly installed system.
  3. Open a terminal and run "sudo software-properties-kde".
  4. Click "Additional Drivers" in the window that pops up.
  5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  Expected result: The Apply Changes button should become clickable,
  allowing the user to install the driver.

  Actual result: The button remains grayed out, and the following error
  message is printed in the terminal:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.27
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 18 21:33:51 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1995358] Re: Screencast only records few seconds

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

This should be fixed in 42.5 (bug 1987631) ?

** This bug has been marked a duplicate of bug 1987631
   Screencast only records one second

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

Title:
  Screencast only records few seconds

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  New

Bug description:
  Hi guys,

   Found a regression of pipewire on ThinkCentre Neo 50a, the
  screencast(Ctrl + Alt + Shift + R) could not record video correctly.

   The version 0.3.48-1ubuntu1 of pipewire works fine with 22.04.1 stock
  image. After upgraded pipewire packages to 0.3.48-1ubuntu2, it's very
  easy to reproduce this issue.

  https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057

  ubuntu: 22.04.1

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


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

[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

2022-11-01 Thread iGadget

Yup, same with any PWA (or site). After almost 5(!!!) years, still no
progress here. Google being the obvious winner since that's the *only*
browser remaining where PWA's 'just work'. Would really appreciate a
response to #26.

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

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


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

[Desktop-packages] [Bug 1995353] [NEW] Switching between desktops often doesn't work

You have been subscribed to a public bug:

After upgrading from 22.04 to 22.10 I have been having issues when switching 
between desktops with Ctrl+Alt and the arrow keys. Often the animation will 
stop half-way so I can see half of each desktop. Sometimes the animation 
finishes but the little indicator at the bottom of the screen (which shows you 
which desktop you're on) doesn't go away and the mouse will not move. 
When this happens I need to switch desktops again until everything is 
responsive again.

Btw I don't see this issue when I select an app in the sidebar thing.
Then the desktop switch is seamless.

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

-- 
Switching between desktops often doesn't work
https://bugs.launchpad.net/bugs/1995353
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1995358] [NEW] Screencast only records few seconds

2022-11-01 Thread Bin Li

Public bug reported:

Hi guys,

 Found a regression of pipewire on ThinkCentre Neo 50a, the
screencast(Ctrl + Alt + Shift + R) could not record video correctly.

 The version 0.3.48-1ubuntu1 of pipewire works fine. After upgraded to
0.3.48-1ubuntu2, it's very easy to reproduce this issue.

https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-1994117 sutton

** Attachment added: "screencast.webm"
   
https://bugs.launchpad.net/bugs/1995358/+attachment/5628254/+files/screencast.webm

** Tags added: oem-priority originate-from-1994117 sutton

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

Title:
  Screencast only records few seconds

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  New

Bug description:
  Hi guys,

   Found a regression of pipewire on ThinkCentre Neo 50a, the
  screencast(Ctrl + Alt + Shift + R) could not record video correctly.

   The version 0.3.48-1ubuntu1 of pipewire works fine. After upgraded to
  0.3.48-1ubuntu2, it's very easy to reproduce this issue.

  https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057

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


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

[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory

2022-11-01 Thread Luis Alberto Pabón

I can confirm this happens with Chromium beta (108.0.5359.22) and edge
(108.0.5359.19), but not stable (106.0.5249.119)

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

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


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

[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

This bug was fixed in the package mutter - 42.5-0ubuntu1

---
mutter (42.5-0ubuntu1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release (LP: #1985856)
  * debian/patches: Refresh
  * debian/libmutter-10-0.symbols: Sync with new and removed internal symbols

  [ Daniel van Vugt ]
  * Update Support-Dynamic-triple-double-buffering.patch.
Dual-GPUs crash in gbm_surface_release_buffer (LP: #1969422)
Leftover mouse pointer when moving between monitors (LP: #1988625)

  [ Zoe Spellman ]
  * New upstream release

 -- Zoe Spellman   Thu, 13 Oct 2022 12:08:14
-0700

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

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  On dual-GPU systems, gnome-shell may crash in
  gbm_surface_release_buffer() during display config changes, like when
  rearranging monitor positions.

  [ Test Plan ]

  1. Find a dual GPU system where both use open source drivers (like Intel + 
AMD).
  2. Ideally also attach one monitor to each GPU.
  3. Open Settings and repeatedly change the monitor layout pressing Apply each 
time.

  Expect: System does not crash.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

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

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


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

[Desktop-packages] [Bug 1981724] Re: Update mutter to 42.3

This bug was fixed in the package mutter - 42.5-0ubuntu1

---
mutter (42.5-0ubuntu1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release (LP: #1985856)
  * debian/patches: Refresh
  * debian/libmutter-10-0.symbols: Sync with new and removed internal symbols

  [ Daniel van Vugt ]
  * Update Support-Dynamic-triple-double-buffering.patch.
Dual-GPUs crash in gbm_surface_release_buffer (LP: #1969422)
Leftover mouse pointer when moving between monitors (LP: #1988625)

  [ Zoe Spellman ]
  * New upstream release

 -- Zoe Spellman   Thu, 13 Oct 2022 12:08:14
-0700

** Changed in: mutter (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  Update mutter to 42.3

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.3/NEWS

  It's hoped that this update will be included in Ubuntu 22.04.1 LTS.

  Test Case
  -
  sudo apt install budgie-desktop gnome-session gnome-shell-extensions
  Install the update.
  Log out.
  Select your name on the login screen.
  Click the gear button to choose a session to log in to.
  Finish logging in.

  Verify that things continue to work well for all these sessions:
  Budgie
  GNOME
  GNOME Classic
  Ubuntu
  Ubuntu on Xorg

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

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

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


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

[Desktop-packages] [Bug 1969422] Update Released

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  On dual-GPU systems, gnome-shell may crash in
  gbm_surface_release_buffer() during display config changes, like when
  rearranging monitor positions.

  [ Test Plan ]

  1. Find a dual GPU system where both use open source drivers (like Intel + 
AMD).
  2. Ideally also attach one monitor to each GPU.
  3. Open Settings and repeatedly change the monitor layout pressing Apply each 
time.

  Expect: System does not crash.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

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

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


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

[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5

This bug was fixed in the package mutter - 42.5-0ubuntu1

---
mutter (42.5-0ubuntu1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release (LP: #1985856)
  * debian/patches: Refresh
  * debian/libmutter-10-0.symbols: Sync with new and removed internal symbols

  [ Daniel van Vugt ]
  * Update Support-Dynamic-triple-double-buffering.patch.
Dual-GPUs crash in gbm_surface_release_buffer (LP: #1969422)
Leftover mouse pointer when moving between monitors (LP: #1988625)

  [ Zoe Spellman ]
  * New upstream release

 -- Zoe Spellman   Thu, 13 Oct 2022 12:08:14
-0700

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

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

Title:
  Update Mutter to 42.5

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

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

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


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

[Desktop-packages] [Bug 1985856] Update Released

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update Mutter to 42.5

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

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

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


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

[Desktop-packages] [Bug 1988625] Re: Left-over cursor visible on second screen

This bug was fixed in the package mutter - 42.5-0ubuntu1

---
mutter (42.5-0ubuntu1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release (LP: #1985856)
  * debian/patches: Refresh
  * debian/libmutter-10-0.symbols: Sync with new and removed internal symbols

  [ Daniel van Vugt ]
  * Update Support-Dynamic-triple-double-buffering.patch.
Dual-GPUs crash in gbm_surface_release_buffer (LP: #1969422)
Leftover mouse pointer when moving between monitors (LP: #1988625)

  [ Zoe Spellman ]
  * New upstream release

 -- Zoe Spellman   Thu, 13 Oct 2022 12:08:14
-0700

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

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

Title:
  Left-over cursor visible on second screen

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  When I move my mouse between screens, every once in a while a leftover
  cursor remains on the screen I just left. Moving to that screen again
  fixes.

  [ Test Plan ]

  1. Set up a dual-monitor system using open source graphics drivers only.
  2. Log into a Wayland session (usually just "Ubuntu").
  3. Wiggle the mouse between the two monitors.

  Expect: The mouse pointer never gets left behind and frozen on the
  previous monitor.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

  This sounds like (Fix Released) #1724977, but seems to happen on extra
  screens.

  It may be related to different scales of my two displays (100% vs.
  200%).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  3 11:51:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1988625] Update Released

The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Left-over cursor visible on second screen

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  When I move my mouse between screens, every once in a while a leftover
  cursor remains on the screen I just left. Moving to that screen again
  fixes.

  [ Test Plan ]

  1. Set up a dual-monitor system using open source graphics drivers only.
  2. Log into a Wayland session (usually just "Ubuntu").
  3. Wiggle the mouse between the two monitors.

  Expect: The mouse pointer never gets left behind and frozen on the
  previous monitor.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

  This sounds like (Fix Released) #1724977, but seems to happen on extra
  screens.

  It may be related to different scales of my two displays (100% vs.
  200%).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  3 11:51:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1994141] Re: incompatible versions of network-manager-openvpn and openvpn delivered in ubuntu22.10

2022-11-01 Thread josef dvoracek

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

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

Title:
  incompatible versions of network-manager-openvpn and openvpn delivered
  in ubuntu22.10

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  After installing  network-manager-openvpn(1.10.0-1ubuntu2),
  openvpn(2.6.0~git20220818-1ubuntu1) is installed as a dependency.

  Mentioned NM plugin uses openvpn option `--cipher` instead of `--data-
  ciphers`. With openvpn2.6.0+ this breaks existing setups - connection
  never establishes and fails with message like:

  ```
  DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in 
--data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores 
--cipher for cipher negotiations.
  ```
  and
  ```
  Connection reset, restarting [0]
  ```

  reproducer: configure openVPN client against openVPN server with
  cipher set to 'AES-256-CBC'.

  workaround: manually install openvpn 2.5.x from sources and mask
  distribution-provided openvpn 2.6.x.

  proposed solution:

  deliver compatible combination of network-manager-openvpn and openvpn.

  
  system info:
  Description:Ubuntu 22.10
  Release:22.10

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


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

[Desktop-packages] [Bug 1956248] Re: I get two characters in Activities when I press one key for the first key I press...

2022-11-01 Thread Bug Watch Updater

** Changed in: dash-to-dock
   Status: Unknown => New

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

Title:
  I get two characters in Activities when I press one key for the first
  key I press...

Status in Dash to dock:
  New
Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  If I click the Activities in the upper right hand corner of the
  screen, then do NOT click in the search bar and begin to type, I get
  two of whatever character I hit.  At first I thought it was due to my
  keyboard wearing out, but it happens on multiple computers, and
  whatever key I type, even infrequently used ones.  If I click in the
  search bar before I type, then the characters are not duplicated.  If
  I then backspace over the single character that was correctly
  displayed in the search bar and type another character, that character
  is doubled.  Bounce keys will not eliminate this either.  I started
  noticing doubling characters a couple of weeks (approximately) ago.  I
  didn't start to suspect the real reason until recently.

  Thanks for working on this for all of us!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  3 11:43:59 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-19 (990 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 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago)

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


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

[Desktop-packages] [Bug 1995354] [NEW] /usr/libexec/gnome-calculator-search-provider:5:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard:_gdk_x11_device_mana

2022-11-01 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: kinetic

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

Title:
  /usr/libexec/gnome-calculator-search-
  
provider:5:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard:_gdk_x11_device_manager_new

Status in gnome-calculator package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 1995329] Re: [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

** Summary changed:

- Devices pair and connect, but immediately (4-5 secs) disconnect
+ [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but 
immediately (4-5 secs) disconnect

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

** Summary changed:

- [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but 
immediately (4-5 secs) disconnect
+ [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately 
(4-5 secs) disconnect

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device

[Desktop-packages] [Bug 1936734] Re: All app icons are missing

** Summary changed:

- Gnome launcher icons are missing
+ All app icons are missing

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

Title:
  All app icons are missing

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

Bug description:
  The Favorite applications on Gnome's launcher pane on the left sporadically 
disappear for significant amounts of time.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-07-16 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: gnome-shell-extension-ubuntu-dock 69ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Tags:  hirsute wayland-session
  Uname: Linux 5.11.0-22-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/dash-to-dock/+bug/1936734/+subscriptions


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

[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static

** Summary changed:

- intermittent green static
+ [amdgpu] intermittent green static

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

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

Title:
  [amdgpu] intermittent green static

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)

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


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

[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

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

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1995236] Re: Xsessions has_option code error with fix

Bug 1922414 covers one of the issues with has_option so please reword
this bug to cover one other issue only.

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  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.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  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:

[Desktop-packages] [Bug 1995207] Re: [amdgpu] gnome-shell: page allocation failure

** Summary changed:

- [22.10] gnome-shell: page allocation failure
+ [amdgpu] gnome-shell: page allocation failure

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947

[Desktop-packages] [Bug 1995216] Re: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system

** Package changed: xorg (Ubuntu) => mate-desktop (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/1995216

Title:
  X forgets monitor configuration when HDMI cable was unplugged and then
  re-plugged on a running system

Status in mate-desktop package in Ubuntu:
  New

Bug description:
  Running 22.04.1, I am using a the following (See 01.png) monitor
  setup.

  When I unplug the HDMI cable from my video card and plug it back, the
  monitor has lost it's orientation (See 02.png)

  If I then reconfigure the monitors I get the following (See 03.png).
  However the changes are taken into consideration and the display is
  back to normal.

  Yet if I continue dragging the monitors around in that same interface
  odd interface behavior start happening more frequently (See 04.png).

  So this could perhaps be split into 2 bugs. I will let you decide.

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Oct 30 12:25:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
  InstallationDate: Installed on 2022-06-02 (149 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  LightdmDisplayLog:
   (EE) event6  - Metadot - Das Keyboard Das Keyboard: client bug: event 
processing lagging behind by 32ms, your system is too slow
   (EE) event6  - Metadot - Das Keyboard Das Keyboard: client bug: event 
processing lagging behind by 36ms, your system is too slow
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic 
root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  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/mate-desktop/+bug/1995216/+subscriptions


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

[Desktop-packages] [Bug 1995202] Re: Wacom input devices change button assignment depending on application

** Tags added: wacom

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

Title:
  Wacom input devices change button assignment depending on application

Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.1 LTS

  Expected:
  Wacom pen and mouse should send a middle and right mouseclick in every 
application. The key assignment should be done once in system-settings.

  Instead:
  Depending on the application, wacom input devices (pen, mouse...) change the 
assignment of the buttons. E.g. in firefox (snap) or blender the right wacom 
mouse button works as expected, in nautilus or libre offce it does not. 
Changing the system-settings for the wacom devices make it work in nautilus, 
but break it in firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter-common 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 30 12:09:13 2022
  InstallationDate: Installed on 2020-08-26 (794 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (75 days ago)

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


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

[Desktop-packages] [Bug 1995162] Re: Gnome-shell Portal Helper to help login to Wifi networks is not working

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

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


** This bug has been marked a duplicate of bug 1995134
   WiFi captive portals stopped working after Kinetic upgrade

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

Title:
  Gnome-shell Portal Helper to help login to Wifi networks is not
  working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgrading to 22.10 from 22.04, and now portal helper for Wifi logins
  is not working anymore

  Looking at the logs from journalctl gave this hint:

  gnome-shell-por[20661]: JS ERROR: ImportError: No JS module 'fileUtils' found 
in search path

@resource:///org/gnome/shell/portalHelper/main.js:13:30
@:1:14

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  Uname: Linux 6.0.5-060005-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 13:48:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-06 (145 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-09 (20 days ago)

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


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

[Desktop-packages] [Bug 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade

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

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

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

Title:
  WiFi captive portals stopped working after Kinetic upgrade

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

Bug description:
  After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer
  recognizes captive portals.

  Attempting to run /usr/libexec/gnome-shell-portal-helper produces this
  output:

  (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS 
module 'fileUtils' found in search path
  @resource:///org/gnome/shell/portalHelper/main.js:13:30
  @:1:14

  
  This may be normal because of the environment, but it is the best I have to 
go on now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 19:26:44 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  InstallationDate: Installed on 2019-08-06 (1179 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago)

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


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

[Desktop-packages] [Bug 1995160] Re: Some problem with graphic card driver

Thanks for the bug report. It looks like you don't have a working
graphics driver installed.

Please open the 'Additional Drivers' app and use it to install the
latest NVIDIA driver.


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

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

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

Title:
  Some problem with graphic card driver

Status in Ubuntu:
  Incomplete

Bug description:
  One day, I suddenly got the trouble with the graphics card driver. I
  tried to switch almost the Nvidia driver but it's still not working. I
  got the error message nvidia-gpu ic2 timeout error then only one
  screen worked. Hence I have to use Xorg the default driver then it
  works. But when I share screen, it display black screen, I can't
  share, and performance when I use the default graphic driver is not
  good as well. Please take a look my trouble

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 12:44:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/470.141.03: added
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1660 Ti] [1043:8840]
  InstallationDate: Installed on 2022-06-30 (120 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. B660M Pro RS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1020-oem 
root=UUID=53a88101-e9f6-4e5f-ac27-9c925fc462c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 5.04
  dmi.board.name: B660M Pro RS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.04:bd03/28/2022:br5.24:svnToBeFilledByO.E.M.:pnB660MProRS:pvrToBeFilledByO.E.M.:rvnASRock:rnB660MProRS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: B660M Pro RS
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  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/+bug/1995160/+subscriptions


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

[Desktop-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-520
(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/1995173

Title:
  Lenovo Legion 7 Display Issues : Cannot Control Display Brightness,
  High Pixel Density Issue, and Resolution Issue

Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  The device is Lenovo Legion 7. This laptop has a mux switch to switch
  between dynamic/hybrid or discrete graphics mode. This laptop has a
  high resolution with high pixel density than the other displays out
  there, but I don't know the exact number. Additionally, this laptop
  can adjust the display refresh rate between 60 and 165 Hz.

  ---

  There were 1 problem I encountered in dynamic/hybrid graphics mode:

  - The widgets shown were too small.

  Details:

  The resolution was correct, at 2560x1600, but all widgets shown were
  too small. I suspected this was due to the laptop screen high pixel
  density and the widget size calculation didn't make use of physical
  dimension, but in terms of pixel.

  I thought installing NVIDIA driver would fix this, but no; this worked
  in OpenSUSE Leap with KDE Plasma and I think it was because of the
  inclusion of NVIDIA OpenGL driver.

  The current workaround was to scale by 200% in "Display Settings",
  although the login screen isn't affected by the scaling at all.

  ---

  There were 3 problems I encountered in discrete graphics mode:

  - The widgets were are too small, like the hybrid graphics mode issue.
  - The DE seemed to use wrong screen refresh rate.

  The refresh rate was fixed at 93 Hz in the "Display Settings".

  Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't
  update the 93 Hz in the "Display Settings".

  This didn't happen in the hybrid graphics mode.

  OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
  think it may be either GNOME DE or xorg misconfigurations.

  - Screen brightness was fixed at 100%.

  Details:

  Screen brightness could be adjusted by the keyboard Fn keys, but the
  brightness was fixed at 100%.

  This didn't happen in the hybrid graphics mode.

  This is the most annoying problem and have forced me to use the hybrid
  graphics mode which I don't like.

  My first thought was either a specific NVIDIA issue or xorg
  misconfigurations.

  So I tried adding "acpi_backlight=vendor" and
  "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
  didn't work at all.

  ---

  In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
  below:

  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

  In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
  except that there was no:

  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .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 Open Kernel Module for x86_64  520.56.06  Release 
Build  (dvs-builder@U16-T12-10-2)  Thu Oct  6 21:33:54 UTC 2022
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 18:50:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu

[Desktop-packages] [Bug 1995349] [NEW] [goodix] The enrolled finger is unknown to device

2022-11-01 Thread Andy Chi

Public bug reported:

[Impact]

 * The enrolled finger is unknown to device

[Test Plan]

 * Find a machine with Goodix fingerprint device

 * Clean up the storage of fp device by `manage-prints`

 * Launch `settings` and enable `Fingerprint Login`

 * Enroll left index finger and right index finger

 * Login with right index finger

[Where problems could occur]

 * This is only affected goodix fingerprint device

** Affects: libfprint
 Importance: Unknown
 Status: Unknown

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: Confirmed

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


** Tags: oem-priority originate-from-1990344 somerville

** Tags added: oem-priority originate-from-1990344 somerville

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

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #511
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/511

** Also affects: libfprint via
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/511
   Importance: Unknown
   Status: Unknown

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

Title:
  [goodix] The enrolled finger is unknown to device

Status in libfprint:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in libfprint package in Ubuntu:
  New

Bug description:
  [Impact]

   * The enrolled finger is unknown to device

  [Test Plan]

   * Find a machine with Goodix fingerprint device

   * Clean up the storage of fp device by `manage-prints`

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll left index finger and right index finger

   * Login with right index finger

  [Where problems could occur]

   * This is only affected goodix fingerprint device

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


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

[Desktop-packages] [Bug 1995021] Re: Boot and shutdown take several minutes

Thanks for the bug report.

Next time you experience a slow boot, please then run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


** Tags added: jammy

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

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

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

Title:
  Boot and shutdown take several minutes

Status in Ubuntu:
  Incomplete

Bug description:
  My system has been running smoothly until Kernel 5.15.0-50 (and
  5.15.0-52) was installed. Now boot and shutdown take several minutes.
  I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown
  run witout delay with the Nouveau and Nvidia 390 drivers but the
  OpenCl is unavailable

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


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

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

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

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

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #20

[Desktop-packages] [Bug 1994941] Re: I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc.

Thanks for the bug report.

Please start by removing local extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

If the problem persists after that then please check for crashes by:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  I locked computer after night  I am trying to turn on by open lid and
  am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I locked computer. After night  I am trying to turn on by open lid and
  I am see dark srceen. keyboard does not respond,  can connect only by
  ssh from other pc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 27 14:33:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-10 (17 days ago)
  InstallationMedia: Ubuntu 20.04.4 2022.08.10 LTS "Custom Focal Fossa" 
(20220810)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-10-10 (16 days ago)

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


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

[Desktop-packages] [Bug 1970196] Re: Nautilus crashes when trying to open a second instance using quicklinks

2022-11-01 Thread Sebastian Ilea

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

** Summary changed:

- Nautilus crashes when trying to open a second innstance using quicklinks
+ Nautilus crashes when trying to open a second instance using quicklinks

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

Title:
  Nautilus crashes when trying to open a second instance using
  quicklinks

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04

  Open at least one instance of Nautilus ("Files").

  Now try to open a second instance, using right-click on the Gnome
  Shell Dock (Dash to Dock or whatever is the default in Ubuntu 22.04)
  and selecting one of the quicklinks (such as "Documents", "Downloads",
  "Music", etc.) - so not "New Window" (this does not crash it).

  In my case, Nautilus always crashes when I do this.

  If Nautilus is not already open, I can start it by right-click on its
  icon on the Gnome Dock and selecting one of the quicklinks, without
  issues.

  Edit:
  It appears I don't know how to search in Launchpad.
  This bug was already reported in Ubuntu 21.04 (bug #1934579).
  As reported there, it only happens when using Wayland. This issue is not 
present when using Xorg.

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


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

[Desktop-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

2022-11-01 Thread Sky

vi0oss came up with a clever workaround for getting this spamware off
our systems.

> Can it be overridden with an additional package which Provides, Breaks and 
> Conflicts with ubuntu-advantage-tools?
(From this comment 
https://old.reddit.com/r/assholedesign/comments/yg97tk/ubuntu_includes_ads_in_system_update_theyre/iuj7hug/
 -- I went ahead and attached the deb here for posterity, but it's also in that 
thread)

So far the deb they created is working for me.

Long term solution being to switch to a distro that respects their
users.

** Attachment added: "fake-ubuntu-advantage-tools.deb"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+attachment/5628220/+files/fake-ubuntu-advantage-tools.deb

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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


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

[Desktop-packages] [Bug 1956248] Re: I get two characters in Activities when I press one key for the first key I press...

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Confirmed

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1855
   https://github.com/micheleg/dash-to-dock/issues/1855

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1855
   Importance: Unknown
   Status: Unknown

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

Title:
  I get two characters in Activities when I press one key for the first
  key I press...

Status in Dash to dock:
  Unknown
Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  If I click the Activities in the upper right hand corner of the
  screen, then do NOT click in the search bar and begin to type, I get
  two of whatever character I hit.  At first I thought it was due to my
  keyboard wearing out, but it happens on multiple computers, and
  whatever key I type, even infrequently used ones.  If I click in the
  search bar before I type, then the characters are not duplicated.  If
  I then backspace over the single character that was correctly
  displayed in the search bar and type another character, that character
  is doubled.  Bounce keys will not eliminate this either.  I started
  noticing doubling characters a couple of weeks (approximately) ago.  I
  didn't start to suspect the real reason until recently.

  Thanks for working on this for all of us!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  3 11:43:59 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-19 (990 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 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago)

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


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

[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland

This bug was fixed in the package gnome-shell - 42.5-0ubuntu1

---
gnome-shell (42.5-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1993809)
- Fix switching monitor with Super-P (LP: #1984147)
  * debian/source_gnome-shell.py: Don't try to report nonexistent mouse
gsettings schema

 -- Jeremy Bicha   Fri, 21 Oct 2022 08:03:20 -0400

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

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

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Users using desktop PC is not able to switch monitor mode between mirrored 
and joined mode using Super-P or keyboard shortcut.  This SRU fixes the issue.

  [Test Plan]
  1. Use a desktop PC and start GNOME 3
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  Expected: Display Switcher popup should appear

  Actual: Display Switcher does not popup

  [Where problems could occur]
  Although this change is minimal, the impact should be only on switching 
display mode using the shortcut.

  [Version]
  gnome-shell42.2-0ubuntu0.2
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-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/oem-priority/+bug/1984147/+subscriptions


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

[Desktop-packages] [Bug 1993809] Re: Update gnome-shell to 42.5

This bug was fixed in the package gnome-shell - 42.5-0ubuntu1

---
gnome-shell (42.5-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1993809)
- Fix switching monitor with Super-P (LP: #1984147)
  * debian/source_gnome-shell.py: Don't try to report nonexistent mouse
gsettings schema

 -- Jeremy Bicha   Fri, 21 Oct 2022 08:03:20 -0400

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

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

Title:
  Update gnome-shell to 42.5

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

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


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

[Desktop-packages] [Bug 1984147] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Monitor switcher popup (Super-P) is not displayed on desktop with
  joined display on Wayland

Status in OEM Priority Project:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Users using desktop PC is not able to switch monitor mode between mirrored 
and joined mode using Super-P or keyboard shortcut.  This SRU fixes the issue.

  [Test Plan]
  1. Use a desktop PC and start GNOME 3
  2. Connect the PC with 2 monitors
  3. Use Super-P to switch to joined display (note that using Displays from 
Settings does not trigger the issue)
  4. Use Super-P to switch display mode again

  Expected: Display Switcher popup should appear

  Actual: Display Switcher does not popup

  [Where problems could occur]
  Although this change is minimal, the impact should be only on switching 
display mode using the shortcut.

  [Version]
  gnome-shell42.2-0ubuntu0.2
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-43-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/oem-priority/+bug/1984147/+subscriptions


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

[Desktop-packages] [Bug 1993785] Re: Wrong loader path defined in pkgconfig

2022-11-01 Thread Sebastien Bacher

Installing libgdk-pixbuf-2.0-dev 2.42.8+dfsg-1ubuntu0.2

$ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders

$ ls -lh /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
-rwxr-xr-x 1 root root 15K říj 21 09:26 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders

The pixbuf loaders are still working as expected in for example the
filemanager or viewer

Marked as verified

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

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+subscriptions


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

[Desktop-packages] [Bug 1993809] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-shell to 42.5

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

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


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

[Desktop-packages] [Bug 1995298] Re: Cheese error after long time to start

Same problem with a different webcam:
Bus 003 Device 005: ID 05a3:9530 ARC International USB 2.0 Camera

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Desktop-packages] [Bug 1988625] Re: Left-over cursor visible on second screen

2022-11-01 Thread Andy Chi

Plug a 4k external monitor to XPS 9320, set the external monitor to 100% and 
set the internal monitor to 200%.
Enable -proposed pocket and install mutter (42.5-0ubuntu1), wiggle mouse 20 
times and no cursor left on my internal monitor.

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

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

Title:
  Left-over cursor visible on second screen

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  When I move my mouse between screens, every once in a while a leftover
  cursor remains on the screen I just left. Moving to that screen again
  fixes.

  [ Test Plan ]

  1. Set up a dual-monitor system using open source graphics drivers only.
  2. Log into a Wayland session (usually just "Ubuntu").
  3. Wiggle the mouse between the two monitors.

  Expect: The mouse pointer never gets left behind and frozen on the
  previous monitor.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

  This sounds like (Fix Released) #1724977, but seems to happen on extra
  screens.

  It may be related to different scales of my two displays (100% vs.
  200%).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  3 11:51:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1995298] Re: Cheese error after long time to start

connecting the webcam to a different USB port I see a different problem:
cheese starts in about 6 seconds, the window shows a video that appears
to run at 2-3 frames per second and the terminal shows the messages:

corrado@corrado-n6-kinetic:~$ cheese

(cheese:4088): cheese-WARNING **: 08:49:16.902: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.


(cheese:4088): cheese-WARNING **: 08:49:17.038: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.


(cheese:4088): cheese-WARNING **: 08:49:18.535: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

... this message continues...

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Desktop-packages] [Bug 1995298] Re: Cheese error after long time to start

2022-11-01 Thread Sebastien Bacher

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

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Desktop-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)

2022-11-01 Thread Mathieu letombe

It seems OK for me. I was still starting my TV 10s after the PC and I
didn't want to install any updates. I finally did it because there was
nvidia-graphics-drivers-515 - 515.76+really.515.65.01-0ubuntu1 which was
a fix for https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-515/+bug/1993041. This issue seems specific to RTX30xx cards
plugged on HDMI, this is my case. I rebooted, it works even if I didn't
shut my TV off.

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

Title:
  Can not login after new kernel installed (nvidia driver crashed)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Confirmed
Status in xserver-xorg-video-intel source package in Jammy:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF

[Desktop-packages] [Bug 1995298] Re: Cheese error after long time to start