date:20230913

MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING is deprecated and is replaced by:

  MUTTER_DEBUG_TRIPLE_BUFFERING=never

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep

[Desktop-packages] [Bug 1974054] Re: Without a reason gnome-shell CPU usage gets high

This bug is closed.

Please open a new bug of your own by running:

  ubuntu-bug gnome-shell

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

Title:
  Without a reason gnome-shell CPU usage gets high

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Without a reason, CPU usage for gnome-shell jumps from 4% to 22%.
  All I did this normal workflow, locking/unlocking multiple times over few 
hours and couple of suspends.

  The screenshot is showing 37% because of the screenshot tool, but idling at 
22%.
  And if I re-logged or reboot, it idles at 4% normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 17:24:38 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (103 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago)

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


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

[Desktop-packages] [Bug 2035560] [NEW] CVE-2023-4863: Update Firefox in Ubuntu20.04

2023-09-13 Thread afefuabetlhujeh

Public bug reported:

Hi,

The Package on Focal hasn't been updated yet for the critical in the
wild exploited Zero Day, it has been almost 2 days since the patched
version 117.0.1 was released! But the Ubuntu package is still outdated.

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

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

Title:
  CVE-2023-4863: Update Firefox in Ubuntu20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi,

  The Package on Focal hasn't been updated yet for the critical in the
  wild exploited Zero Day, it has been almost 2 days since the patched
  version 117.0.1 was released! But the Ubuntu package is still
  outdated.

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


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

[Desktop-packages] [Bug 2035220] Re: cve-2023-4863

2023-09-13 Thread Bug Watch Updater

** Changed in: libwebp (Debian)
   Status: New => Confirmed

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  Confirmed

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update

2023-09-13 Thread Launchpad Bug Tracker

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.104.05-0ubuntu4

---
nvidia-graphics-drivers-535 (535.104.05-0ubuntu4) mantic; urgency=medium

  * debian/rules:
- Do not start the systemd services on installation or upgrade, as this can
  lead to a black screen.

 -- Alberto Milone   Thu, 31 Aug 2023
09:06:31 +

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Unrequested kernel update

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

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


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

[Desktop-packages] [Bug 2011244] Re: emacs launching in GNOME is all messed up

2023-09-13 Thread Gregory Smith

As a workaround to the pinning issue, commenting out the StartupWMClass
line in /usr/share/applications/emacsclient.desktop allows pinning the
Emacs (GUI) desktop entry and doesn't add another icon. The two desktop
entries share the same StartupWMClass and I don't know how gnome shell
would be able to associate the windows to icons correctly in that
situation.

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

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  New
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

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


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

[Desktop-packages] [Bug 2034579] Re: [FFe] Use tecla to display keyboard layouts

2023-09-13 Thread Jeremy Bícha

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

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

Title:
[FFe] Use tecla to display keyboard layouts

Status in gnome-control-center package in Ubuntu:
Fix Committed

Bug description:
Explanation of FeatureFreeze exception
===
GNOME 45 includes a new keyboard layout viewer named Tecla to replace
gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for
this was approved in LP: #2026774 but I reverted the switch in the
gnome-control-center, gnome-initial-setup, and gnome-shell packaging because
the first release of Tecla crashed with some keyboard layouts. That issue has
been fixed for the gnome-control-center & gnome-initial-setup integration.

Specific changes

1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup
2. Have gnome-control-center and gnome-initial-setup depend on Tecla
3. Promote Tecla to main. The approved MIR is
https://launchpad.net/bugs/2026774

(Both 1 and 2 have been done in Debian Unstable now.)

Later changes
=
In my testing with GNOME Shell 45 Beta, there are still some issues with the
Tecla integration. I'll file those issues upstream and we'd like to be able to
switch GNOME Shell to use Tecla later this cycle. We would…

4. Drop the Tecla patch from gnome-shell
5. Have gnome-shell depend on Tecla
6. Demote libgnomekbd to Universe

Testing Done

I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from
https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

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

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

[Desktop-packages] [Bug 2029019] Re: PulseAudio doesn't start by logging in after a standby

2023-09-13 Thread Luca Pavan

https://forum.zorin.com/t/no-audio-after-relogging-in/26234

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

Title:
  PulseAudio doesn't start by logging in after a standby

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Often when I log in after a standby PulseAudio doesn't play any audio, the 
service is working but no audio is heard. I noticed that when this happens, if 
I adjust volume the system shows Dummy Output instead of the usual speaker 
small window. Also, one day when I was having right this issue I simply took a 
screenshot to a game that I was playing and audio was played 廊.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca   1456 F pulseaudio
   /dev/snd/pcmC0D0p:   luca   1456 F...m pulseaudio
   /dev/snd/controlC1:  luca   1456 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: zorin:GNOME
  DistroRelease: Zorin OS 16
  InstallationDate: Installed on 2022-10-01 (325 days ago)
  InstallationMedia: Zorin-OS 16.1 Core 64bit
  Package: pulseaudio 1:13.99.1-1ubuntu3.13 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
  Tags: focal third-party-packages
  Uname: Linux 5.15.0-78-generic x86_64
  UnreportableReason: Questo non è un pacchetto ufficiale di Zorin. Rimuovere 
tutti i pacchetti di terze parti, quindi riprovare.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/28/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52N.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52N
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52N.218:bd01/28/2011:br4.6:svnASUSTeKComputerInc.:pnK52N:pvr1.0:rvnASUSTeKComputerInc.:rnK52N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.name: K52N
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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


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

[Desktop-packages] [Bug 2035397] [NEW] I had a problem with HDMI

2023-09-13 Thread Enzo Reis de Oliveira

Public bug reported:

I don't know a lot about Linux and Ubuntu, but recently, due to college,
I did a duo boot so I could have both Windows and Linux. But, whenever
im at Linux, for some reason, my screen doesn't share with another
monitor through HDMI, but with Windows it does. So i searched for some
instructions, and ive been told to try and run this code in my therminal
ubuntu-bug xorg, and that's why im here.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 13:56:48 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1116]
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1d05:1116]
InstallationDate: Installed on 2023-08-31 (13 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Avell High Performance A70 LIV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=c99dc4b0-1110-43e9-a231-5487f4e4ce0d ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N.1.07AVE00
dmi.board.asset.tag: Standard
dmi.board.name: Avell A70 LIV
dmi.board.vendor: Avell High Performance
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Avell High Performance
dmi.chassis.version: Standard
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07AVE00:bd02/22/2021:br5.17:efr1.14:svnAvellHighPerformance:pnA70LIV:pvrStandard:rvnAvellHighPerformance:rnAvellA70LIV:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard:skuA70LIV:
dmi.product.family: A70 LIV
dmi.product.name: A70 LIV
dmi.product.sku: A70 LIV
dmi.product.version: Standard
dmi.sys.vendor: Avell High Performance
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  I had a problem with HDMI

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know a lot about Linux and Ubuntu, but recently, due to
  college, I did a duo boot so I could have both Windows and Linux. But,
  whenever im at Linux, for some reason, my screen doesn't share with
  another monitor through HDMI, but with Windows it does. So i searched
  for some instructions, and ive been told to try and run this code in
  my therminal ubuntu-bug xorg, and that's why im here.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 13:56:48 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1116]
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / 
Max-Q] [1d05:1116]
  InstallationDate: Installed on 2023-08-31 (13 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType:

[Desktop-packages] [Bug 2035395] [NEW] windows randomly raise when others close

2023-09-13 Thread Joe Harrington

Public bug reported:

(I am not sure if xwayland is at fault or the session or window manager.
It happens under Wayland using gnome-session and gnome-shell, but not
under X.org.)

When I close a window, even using ^W or ^Q, another seemingly-random
window may raise to the top, possibly under the cursor and intercepting
my typing.

Expected behavior is for other windows to maintain their placement when
a window closes.

I use sloppy focus.  Otherwise, I have a relatively unaltered setup.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xwayland 2:22.1.1-1ubuntu0.6
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 14:52:38 2023
InstallationDate: Installed on 2023-03-18 (179 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_us.ut...@cdate.utf-8
 SHELL=/bin/bash
SourcePackage: xwayland
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  windows randomly raise when others close

Status in xwayland package in Ubuntu:
  New

Bug description:
  (I am not sure if xwayland is at fault or the session or window
  manager. It happens under Wayland using gnome-session and gnome-shell,
  but not under X.org.)

  When I close a window, even using ^W or ^Q, another seemingly-random
  window may raise to the top, possibly under the cursor and
  intercepting my typing.

  Expected behavior is for other windows to maintain their placement
  when a window closes.

  I use sloppy focus.  Otherwise, I have a relatively unaltered setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.1-1ubuntu0.6
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 14:52:38 2023
  InstallationDate: Installed on 2023-03-18 (179 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_us.ut...@cdate.utf-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2035394] [NEW] browser windows get thick black border, resize badly

2023-09-13 Thread Joe Harrington

Public bug reported:

(I am not sure if xwayland is at fault or the session or window manager
or the browser apps. It happens under Wayland using gnome-session and
gnome-shell and to both Firefox and Chrome browser windows, but not to
any other app.  These are the only browsers I use.)

After using a browser for a while (both Chrome and Firefox), the
transparent "halo" around one or more (but not generally all) of its
windows may acquire an opaque color.  This is usually an image of
whatever was behind the window when the bug triggers, but eventually
gets filled in as all black.

Sometimes when this happens, resizing it larger and smaller clears the
problem, sometimes not.

Sometimes when this happens, resizing the window larger will result in
the window staying the same size and place, but the border expanding
into a larger black background rectangle, without the window resizing at
all.

Sometimes when this happens, resizing the window smaller will result in
the window image being truncated without resizing, and upon resizing
larger again, the window maintains its small, truncated size, sitting in
the corner of a larger black rectangle.  If the portion including the
titlebar buttons in the upper-right gets truncated, it becomes
impossible to click maximize, iconify, or close.

A workaround is to open a new browser window, select all the tabs, and
drag them to the new window. That window will act normally for a while
(a few days?) and then may be susceptible to the bug.  The windows that
have this happen to them seem to be the most-used ones, so maybe it's
related to the number of user window interactions or moving between
monitors.  I have some browser windows with tabs I use only rarely.
These stay minimized most of the time and rarely if ever suffer from the
problem.

If it matters, I use sloppy focus.  This is the only substantive change
from default install.

Obviously, expected behavior is not to have any of these things happen.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xwayland 2:22.1.1-1ubuntu0.6
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 14:37:17 2023
InstallationDate: Installed on 2023-03-18 (178 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_us.ut...@cdate.utf-8
 SHELL=/bin/bash
SourcePackage: xwayland
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  browser windows get thick black border, resize badly

Status in xwayland package in Ubuntu:
  New

Bug description:
  (I am not sure if xwayland is at fault or the session or window
  manager or the browser apps. It happens under Wayland using gnome-
  session and gnome-shell and to both Firefox and Chrome browser
  windows, but not to any other app.  These are the only browsers I
  use.)

  After using a browser for a while (both Chrome and Firefox), the
  transparent "halo" around one or more (but not generally all) of its
  windows may acquire an opaque color.  This is usually an image of
  whatever was behind the window when the bug triggers, but eventually
  gets filled in as all black.

  Sometimes when this happens, resizing it larger and smaller clears the
  problem, sometimes not.

  Sometimes when this happens, resizing the window larger will result in
  the window staying the same size and place, but the border expanding
  into a larger black background rectangle, without the window resizing
  at all.

  Sometimes when this happens, resizing the window smaller will result
  in the window image being truncated without resizing, and upon
  resizing larger again, the window maintains its small, truncated size,
  sitting in the corner of a larger black rectangle.  If the portion
  including the titlebar buttons in the upper-right gets truncated, it
  becomes impossible to click maximize, iconify, or close.

  A workaround is to open a new browser window, select all the tabs, and
  drag them to the new window. That window will act normally for a while
  (a few days?) and then may be susceptible to the bug.  The windows
  that have this happen to them seem to be the most-used ones, so maybe
  it's related to the number of user window interactions or moving
  between monitors.  I have some browser windows with tabs I use only
  rarely.  These stay minimized most of the time and rarely if ever
  suffer from the problem.

  If it matters, I use

[Desktop-packages] [Bug 2035391] [NEW] Terminal windows disappear when external monitors connect

2023-09-13 Thread Joe Harrington

Public bug reported:

(I am not sure if xwayland is at fault or the session or window manager
or the GNOME Terminal app. It happens under Wayland using gnome-session
and gnome-shell.)

When I connect external monitors (via a Thunderbolt 4 dock), sometimes
GNOME Terminal windows that stay on the primary display disappear. Using
the Ubuntu dock, I can see the windows in the thumbnails when I click on
the Terminal app, but when I click on the thumbnail, the terminal in the
lower-right corner highlights as though it is the window that was
clicked; the missing window does not reappear.  When I unplug the
monitors, the terminals are still gone, but if I click on the
thumbnails, they restore, usually in the lower-right rather than the
upper-left and upper-right corners they started in.  It seems only to be
these two windows that vanish, not the other four terminals I have on
screen. Terminal borders are contained within the primary laptop screen,
but they do sometimes overlap each other or other windows, and the
transparent halos (or whatever they're called) that the window manager
puts around them are sometimes off-screen.  The windows are on the far
right screen edge and on the left flush with the right edge of the dock,
and both flush with the bottom edge of the Activities bar that runs
across the top of the primary display.

Needless to say, my expected behavior is that they don't move or
disappear when external monitors are connected, since they've never been
pulled to external monitors, and that regardless, they appear when their
thumbnails are clicked.

In the same or a possibly related problem, some windows, notably the
Thunderbird appointment reminder list, get reduced to the tiniest
possible size and put on an external monitor, when one is attached.
This requires finding them (usually there is a piece of the title bar
left) and stretching them out.

I use sloppy focus (follow pointer but keep last focused window when
pointer is over background), if that matters.

GNOME Terminal 3.44.0 for GNOME 42.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xwayland 2:22.1.1-1ubuntu0.6
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 12:09:08 2023
InstallationDate: Installed on 2023-03-18 (178 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_us.ut...@cdate.utf-8
 SHELL=/bin/bash
SourcePackage: xwayland
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Terminal windows disappear when external monitors connect

Status in xwayland package in Ubuntu:
  New

Bug description:
  (I am not sure if xwayland is at fault or the session or window
  manager or the GNOME Terminal app. It happens under Wayland using
  gnome-session and gnome-shell.)

  When I connect external monitors (via a Thunderbolt 4 dock), sometimes
  GNOME Terminal windows that stay on the primary display disappear.
  Using the Ubuntu dock, I can see the windows in the thumbnails when I
  click on the Terminal app, but when I click on the thumbnail, the
  terminal in the lower-right corner highlights as though it is the
  window that was clicked; the missing window does not reappear.  When I
  unplug the monitors, the terminals are still gone, but if I click on
  the thumbnails, they restore, usually in the lower-right rather than
  the upper-left and upper-right corners they started in.  It seems only
  to be these two windows that vanish, not the other four terminals I
  have on screen. Terminal borders are contained within the primary
  laptop screen, but they do sometimes overlap each other or other
  windows, and the transparent halos (or whatever they're called) that
  the window manager puts around them are sometimes off-screen.  The
  windows are on the far right screen edge and on the left flush with
  the right edge of the dock, and both flush with the bottom edge of the
  Activities bar that runs across the top of the primary display.

  Needless to say, my expected behavior is that they don't move or
  disappear when external monitors are connected, since they've never
  been pulled to external monitors, and that regardless, they appear
  when their thumbnails are clicked.

  In the same or a possibly related problem, some windows, notably the
  Thunderbird appointment reminder list, get reduced to the tiniest
  possible size and put on an external monitor,

[Desktop-packages] [Bug 2035220] Re: cve-2023-4863

For your information, Chromium is now in 116.0.5845.187 in x86, and
should be in ARM too tomorrow.

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2035220] Re: cve-2023-4863

2023-09-13 Thread themusicgod1

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

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

** Also affects: firefox-esr (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  New
Status in firefox-esr package in Ubuntu:
  New
Status in libwebp package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

2023-09-13 Thread Gunnar Hjalmarsson

The description looks right to me now.

The thing is that the regional formats value you set is *also*
represented by a line in a user file in the
/var/lib/AccountsService/users directory. There is quite some code which
tries to keep that line in sync with ~/.pam_environment, and by changing
those variables in ~/.pam_environment only they got out of sync. :/

If you want to use a script in connection with preparing a distro, one
way is to change it in both places.

Or probably better: Let the script edit only /etc/default/locale to your
liking and don't create ~/.pam_environment in advance.

A few years ago I figured out a terminal command to change the user's
regional format value the 'right' way:

https://askubuntu.com/a/754519

It's pretty long...

** Changed in: language-selector (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: language-selector (Ubuntu)
   Status: Incomplete => New

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  New

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:

  
  Step 1, identify how to load ~/.pam_environment to `locale`

  * Default Ubuntu MATE 23.04:

  ~/.pam_environment does not exist

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC="en_US.UTF-8"
  LC_TIME="en_US.UTF-8"
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY="en_US.UTF-8"
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT="en_US.UTF-8"
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=

  * Open gnome-language-selector, click on the "Regional Formats" tab, and 
click on the "Display numbers, dates and currency in the usual format for" list 
and select "English (Canada)"
  * Press on the Close button

  $ cat .pam_environment
  LC_NUMERICDEFAULT=en_CA.UTF-8
  LC_TIME   DEFAULT=en_CA.UTF-8
  LC_MONETARY   DEFAULT=en_CA.UTF-8
  LC_PAPER  DEFAULT=en_CA.UTF-8
  LC_NAME   DEFAULT=en_CA.UTF-8
  LC_ADDRESSDEFAULT=en_CA.UTF-8
  LC_TELEPHONE  DEFAULT=en_CA.UTF-8
  LC_MEASUREMENTDEFAULT=en_CA.UTF-8
  LC_IDENTIFICATION DEFAULT=en_CA.UTF-8
  PAPERSIZE DEFAULT=letter

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC="en_US.UTF-8"
  LC_TIME="en_US.UTF-8"
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY="en_US.UTF-8"
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT="en_US.UTF-8"
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=

  * Sign out, and sign in

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_CA.UTF-8
  LC_TIME=en_CA.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_CA.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_CA.UTF-8
  LC_NAME=en_CA.UTF-8
  LC_ADDRESS=en_CA.UTF-8
  LC_TELEPHONE=en_CA.UTF-8
  LC_MEASUREMENT=en_CA.UTF-8
  LC_IDENTIFICATION=en_CA.UTF-8
  LC_ALL=


  
  
  Step 2, demonstrate that ~/.pam_environment can be scripted

  Run this in terminal:

  sudo tee ~/.pam_environment > /dev/null << 'EOF'
  LC_NUMERICDEFAULT=en_DK.UTF-8
  LC_TIME   DEFAULT=en_DK.UTF-8
  LC_MONETARY   DEFAULT=en_DK.UTF-8
  LC_PAPER  DEFAULT=en_DK.UTF-8
  LC_NAME   DEFAULT=en_DK.UTF-8
  LC_ADDRESSDEFAULT=en_DK.UTF-8
  LC_TELEPHONE  DEFAULT=en_DK.UTF-8
  LC_MEASUREMENTDEFAULT=en_DK.UTF-8
  LC_IDENTIFICATION DEFAULT=en_DK.UTF-8
  PAPERSIZE DEFAULT=a4
  EOF

  * Sign out, and sign in to the desktop environment.
  * $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_DK.UTF-8
  LC_TIME=en_DK.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_DK.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_DK.UTF-8
  LC_NAME=en_DK.UTF-8
  LC_ADDRESS=en_DK.UTF-8
  LC_TELEPHONE=en_DK.UTF-8
  LC_MEASUREMENT=en_DK.UTF-8
  LC_IDENTIFICATION=en_DK.UTF-8
  LC_ALL=

  
  Issue:
  * Open gnome-language-selector, click on the "Regional Formats" tab, check 
the "Display numbers, dates and currency in the usual format for" list, it is 
not set to "English (Denmark)"

  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 2035376] Re: Crashed after login in live session

2023-09-13 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2035376

** Tags added: iso-testing

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

Title:
  Crashed after login in  live session

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Crash when selecting 'Try Ubuntu'

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3 [origin: unknown]
  Uname: Linux 6.3.0-7-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 15:22:25 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

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


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

[Desktop-packages] [Bug 2035376] Re: Crashed after login in live session

2023-09-13 Thread Paul White

** Information type changed from Private to Public

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

Title:
  Crashed after login in  live session

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Crash when selecting 'Try Ubuntu'

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3 [origin: unknown]
  Uname: Linux 6.3.0-7-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 15:22:25 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

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


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

[Desktop-packages] [Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"

2023-09-13 Thread wontfix

Can this also apply to 41 to more equalize dependencies with Kinetic, Lunar, 
Mantic and above?
https://launchpad.net/ubuntu/+source/gnome-control-center/1:42.3-2ubuntu1

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

Title:
  gnome-control-centre crashes after enabling "Sharing"

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  gnome-control-center uses gsettings schemas from the gnome-remote-desktop 
package without being able to handle if those schemas are not installed.

  Because gnome-control-center keeps track of which page was last
  opened, it's not possible to simply ignore the Sharing page, a user
  would need to manually open the Settings app to a different page or
  else the Settings app won't run at all.

  ubuntu-desktop and gnome-shell already Recommend gnome-remote-desktop
  so most people won't experience this issue.

  Test Case
  -
  sudo apt remove gnome-remote-desktop
  Run gnome-control-center
  From the left sidebar, click Sharing
  (The app crashes)
  Install the update. The update will install gnome-remote-desktop.
  Run gnome-control-center
  The app should work like normal

  What Could Go Wrong
  ---
  This only adds a hard dependency on gnome-remote-desktop.

  Without this fix, the Sharing panel didn't work at all.

  Original Bug Report
  ---
  After the crash, gnome-control-centre fails to launch again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Jul  3 20:39:04 2022
  InstallationDate: Installed on 2017-05-24 (1866 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-05-31 (33 days ago)

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


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

[Desktop-packages] [Bug 1999934] Re: Can't print on Canon CP800

2023-09-13 Thread marcocassisa

The same here

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

Title:
  Can't print on Canon CP800

Status in gutenprint package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu 22.10 from 22.04 I can no longer print with
  Canon Selphy CP800 using the gutenprint drivers.

  This is a regression in one of the packages:

  printer-driver-gutenprint_5.3.4.20220624T01008808d602-1_amd64.deb
  libgutenprint9_5.3.4.20220624T01008808d602-1_amd64.deb
  libgutenprint-common_5.3.4.20220624T01008808d602-1_all.deb

  The issue is resolved by removing these packages and manually
  installing the packages from Jammy:

  libgutenprint-common/jammy,jammy,now 5.3.3-9 all
  libgutenprint9/jammy,now 5.3.3-9 amd64
  printer-driver-gutenprint/jammy,now 5.3.3-9

  The error logs from cups are:

  E [16/Dec/2022:20:18:02 +0200] [Job 184] Incorrect paper loaded (01 vs 11), 
aborting job!
  W [16/Dec/2022:20:18:03 +0200] [Job 184] Backend returned status 3 (hold job)

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


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

[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list

2023-09-13 Thread Simon Chopin

Hi Dirk,

Thanks for the revised patch. However, it needs to be based on top of
the version currently in -proposed. The archive can't overwrite a
version that's already published, which is basically whenever its
sources hit the -proposed pocket (that happened when Steve accepted the
SRU back in #21).

Unsubscribing ubuntu-sponsors, please resubscribe when you feel the
patch is ready for review :)

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Confirmed
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

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


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

[Desktop-packages] [Bug 1974054] Re: Without a reason gnome-shell CPU usage gets high

2023-09-13 Thread Jorge Sivil

I had the same problem, and my computer graphics felt slow (i.e the side bar 
opening animation).
I had fixed this by messing with the nvidia drivers, using prime-select to 
select nvidia, etc.
However after update plus restart, this started to happen again.

I noticed gnome-shell always at 30% more or less. I disabled the extension 
"Vitals" but had the same issue, and disabled all extensions and the issue 
persisted.
So I logged out and in again, and it started working correctly.
I re-enabled extensions minus-vitals, and so far it is working correctly with 
the animations

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

Title:
  Without a reason gnome-shell CPU usage gets high

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Without a reason, CPU usage for gnome-shell jumps from 4% to 22%.
  All I did this normal workflow, locking/unlocking multiple times over few 
hours and couple of suspends.

  The screenshot is showing 37% because of the screenshot tool, but idling at 
22%.
  And if I re-logged or reboot, it idles at 4% normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 17:24:38 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (103 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (26 days ago)

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


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

Re: [Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs

2023-09-13 Thread James Martin

I am on LOA for work until 9/18. I'll check when I return to work that day
and follow up with you.

On Wed, Sep 13, 2023, 9:51 AM Gabriel Nagy <2024...@bugs.launchpad.net>
wrote:

> Hello,
>
> The issues described for 22.10 and 23.04 were fixed by
> https://github.com/ubuntu/adsys/pull/699 and are available since adsys
> v0.12.0. However this is only available in Mantic which is not yet
> released.
>
> For the "invalid argument" issue encountered in 22.04, could you confirm
> the version of the installed libsmbclient library in 22.04?
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2024377
>
> Title:
>   Adsys can't fetch GPOs
>
> Status in adsys package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Bad, maybe no understandable english ahead.
>
>   Can't find anything related to this on Github, Canonical Forums,
>   Reddit or StackOverflow.
>
>   On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
>   steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
>   backend, I can log with Active Directory users however when adsys is
>   installed I can't fetch GPOs. In this version the error is:
>
>   ERROR Error from server: error while updating policy: can't get
>   policies for "ubuntu": can't download all gpos and assets: one or more
>   error while fetching GPOs and assets: can't download "ubuntuRoot":
>   can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
>   open
>   smb://
> addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI
> 
> :
>   invalid argument
>
>   It happens when using "adsysctl update -m" or "adsysctl update
>   usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
>   "adsysctl update" too.
>
>   I've upgrade the machine to 22.10 and the error changed to:
>
>   ERROR Error from server: error while updating policy: can't get policies
> for "ubuntu": failed to retrieve the list of GPO (exited with 1): exit
> status 1
>   Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
>   Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap':
> LDAP client internal error: NT_STATUS_INVALID_PARAMETER
>   Failed to open session: (1, 'LDAP client internal error:
> NT_STATUS_INVALID_PARAMETER').
>
>   After upgrade to 23.04 the error persist same as the above.
>
>   Full info 22.04 (- verbose):
>
>   INFO No configuration file: Config File "adsys" Not Found in
> "[/home/jzprates /root /etc /usr/sbin]".
>   We will only use the defaults, env variables or flags.
>   DEBUG Connecting as [[2504:109556]]
>   DEBUG New request /service/UpdatePolicy
>   DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
> ubuntu, Krb5Cc:
>   DEBUG NormalizeTargetName for "ubuntu", type "computer"
>   DEBUG Check if grpc request peer is authorized
>   DEBUG Authorized as being administrator
>   DEBUG GetPolicies for "ubuntu", type "computer"
>   DEBUG Getting gpo list with arguments: "--objectclass computer ldap://
> addc01.domain.com.br ubuntu"
>   DEBUG GPO "ubuntuRoot" for "ubuntu" available at "smb://
> addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}
> 
> "
>   DEBUG Analyzing "assets"
>   DEBUG Analyzing "ubuntuRoot"
>   INFO No assets directory with GPT.INI file found on AD, skipping assets
> download
>   ERROR Error from server: error while updating policy: can't get policies
> for "ubuntu": can't download all gpos and assets: one or more error while
> fetching GPOs and assets: can't download "ubuntuRoot": can't check if
> ubuntuRoot needs refreshing: no GPT.INI file: cannot open smb://
> addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI
> :
> invalid argument
>
>   Full info 23.04 (- verbose):
>
>   INFO No configuration file: Config File "adsys" Not Found in
> "[/home/jzprates /root /etc /usr/sbin]".
>   DEBUG Connecting as [[58811:006019]]
>   DEBUG New request /service/UpdatePolicy
>   DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
> ubuntu, Krb5Cc:
>   DEBUG NormalizeTargetName for "ubuntu", type "computer"
>   DEBUG Check if grpc request peer is authorized
>   DEBUG Authorized as being administrator
>   DEBUG GetPolicies for "ubuntu", type "computer"
>   DEBUG Getting gpo list with arguments: "--objectclass computer ldap://
> addc01.domain.com.br ubuntu"
>   ERROR Error from server: error while updating policy: can't get policies
> for "ubuntu": failed to retrieve the list of GPO (exited with 1): exit
> status 1
>   Failed to bind -

[Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs

2023-09-13 Thread Gabriel Nagy

Hello,

The issues described for 22.10 and 23.04 were fixed by
https://github.com/ubuntu/adsys/pull/699 and are available since adsys
v0.12.0. However this is only available in Mantic which is not yet
released.

For the "invalid argument" issue encountered in 22.04, could you confirm
the version of the installed libsmbclient library in 22.04?

Thanks

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

Title:
  Adsys can't fetch GPOs

Status in adsys package in Ubuntu:
  Confirmed

Bug description:
  Bad, maybe no understandable english ahead.

  Can't find anything related to this on Github, Canonical Forums,
  Reddit or StackOverflow.

  On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
  steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
  backend, I can log with Active Directory users however when adsys is
  installed I can't fetch GPOs. In this version the error is:

  ERROR Error from server: error while updating policy: can't get
  policies for "ubuntu": can't download all gpos and assets: one or more
  error while fetching GPOs and assets: can't download "ubuntuRoot":
  can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
  open
  
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
  invalid argument

  It happens when using "adsysctl update -m" or "adsysctl update
  usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
  "adsysctl update" too.

  I've upgrade the machine to 22.10 and the error changed to:

  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
  Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP 
client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to open session: (1, 'LDAP client internal error: 
NT_STATUS_INVALID_PARAMETER').

  After upgrade to 23.04 the error persist same as the above.

  Full info 22.04 (- verbose):

  INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates 
/root /etc /usr/sbin]".
  We will only use the defaults, env variables or flags.
  DEBUG Connecting as [[2504:109556]]
  DEBUG New request /service/UpdatePolicy
  DEBUG Requesting with parameters: IsComputer: true, All: false, Target: 
ubuntu, Krb5Cc:
  DEBUG NormalizeTargetName for "ubuntu", type "computer"
  DEBUG Check if grpc request peer is authorized
  DEBUG Authorized as being administrator
  DEBUG GetPolicies for "ubuntu", type "computer"
  DEBUG Getting gpo list with arguments: "--objectclass computer 
ldap://addc01.domain.com.br ubuntu"
  DEBUG GPO "ubuntuRoot" for "ubuntu" available at 
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
  DEBUG Analyzing "assets"
  DEBUG Analyzing "ubuntuRoot"
  INFO No assets directory with GPT.INI file found on AD, skipping assets 
download
  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": can't download all gpos and assets: one or more error while fetching 
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs 
refreshing: no GPT.INI file: cannot open 
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
 invalid argument

  Full info 23.04 (- verbose):

  INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates 
/root /etc /usr/sbin]".
  DEBUG Connecting as [[58811:006019]]
  DEBUG New request /service/UpdatePolicy
  DEBUG Requesting with parameters: IsComputer: true, All: false, Target: 
ubuntu, Krb5Cc:
  DEBUG NormalizeTargetName for "ubuntu", type "computer"
  DEBUG Check if grpc request peer is authorized
  DEBUG Authorized as being administrator
  DEBUG GetPolicies for "ubuntu", type "computer"
  DEBUG Getting gpo list with arguments: "--objectclass computer 
ldap://addc01.domain.com.br ubuntu"
  ERROR Error from server: error while updating policy: can't get policies for 
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
  Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP 
client internal error: NT_STATUS_INVALID_PARAMETER
  Failed to open session: (1, 'LDAP client internal error: 
NT_STATUS_INVALID_PARAMETER')

  Additional info:

  Domain Controller and machine are on the same subnet without firewall on any 
level;
  Domain Controller is a Windows Server 2019 updated to the last security 
version;
  Both machine and user are on the same OU with "no heritage" enabled and just 
one policy added to permit usern...@domain.com.br to become root;
  The info header directory is

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

2023-09-13 Thread Ernst Sjöstrand

I got it again now with
$HOME/.config/environment.d/debug.conf :

MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
MUTTER_DEBUG_FORCE_KMS_MODE=simple

Of course, all the triple buffering patches are still there. Haven't
tried vanilla mutter/gnome-shell yet.

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10

[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

My original MESA bug report (now closed) is at:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

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


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

[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

In order to test if the system MESA has the fix while the Chromium snaps
does not, I unpacked it and ran the Chromium binary against system
libraries.

The GPU hang doesn't reproduce, suggesting the MESA libraries included
in the Snaps is outdated and should be updated to eg
23.0.4-0ubuntu1~23.04.1.

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9695
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

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


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

[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

System:
  Host: spectre Kernel: 6.2.0-32-generic arch: x86_64 bits: 64
compiler: N/A Desktop: GNOME v: 44.3 tk: GTK v: 3.24.37 wm: gnome-shell
dm: GDM3 Distro: Ubuntu 23.04 (Lunar Lobster)
CPU:
  Info: 9-core model: 12th Gen Intel Core i7-1260P bits: 64 type: MCP
smt: disabled arch: Alder Lake rev: 3 cache: L1: 848 KiB L2: 5.2 MiB
L3: 18 MiB
  Speed (MHz): avg: 2303 high: 2500 min/max: 400/4700:3400 cores: 1: 2500
2: 2500 3: 2500 4: 2500 5: 729 6: 2500 7: 2500 8: 2500 9: 2500
bogomips: 44928
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-12.2 ports: active: eDP-1 empty: DP-1,
DP-2, DP-3, DP-4, DP-5 bus-ID: 00:02.0 chip-ID: 8086:46a6
  Device-2: Intel DG2 [Arc A370M] vendor: Hewlett-Packard driver: vfio-pci
v: N/A arch: Gen-12.7 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
chip-ID: 8086:5693
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8
compositor: gnome-shell driver: X: loaded: N/A
unloaded: fbdev,modesetting,vesa gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: Samsung 0x4174 res: 3840x2400 dpi: 284
diag: 406mm (16")
  API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: Mesa Intel
Graphics (ADL GT2) direct-render: Yes

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

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


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

[Desktop-packages] [Bug 2035360] [NEW] GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Public bug reported:

When opening a SketchUp model (example) in Firefox or Chromium, after ~5
seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank
page. The logs show the GPU hang and browser rendering context failed to
initialise.

This has 100% reproducibility on my 12-gen GPU.

On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock 
Ubuntu kernel or mainline.
Log files as attachment

- the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
- the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' 
is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
- the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

Since I was able to cause failure uncontained to the rendering process
when performing this 5-8 times, there is an argument that this is a
security (DoS) issue, though I'll let someone else make a judgement.

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

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

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


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

[Desktop-packages] [Bug 2035036] Re: [Mantic] dark theme not applied on some apps

2023-09-13 Thread Jeremy Bícha

The GNOME Shell accent color bug is already being tracked at
https://launchpad.net/bugs/2033688

Thanks!

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

Title:
  [Mantic] dark theme not applied on some apps

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  GS 45 rc, latest up to date, Mantic

  When I apply dark theme through usual quick settings, some apps become
  dark (Firefox, Tweaks, System Monitor...) some do not (Synaptic,
  wxMaxima, NVidia settings...).

  Was ok some time ago in Mantic with GS 45.

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


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

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

I updated the top post a lot, please re-read it when you have time
Gunnar, so you understand that I'm 100% informed =)

** Description changed:

  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list, are
  stored in ~/.pam_environment
  
  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
+ 
+ 
+ Step 1, identify how to load ~/.pam_environment to `locale`
  
  * Default Ubuntu MATE 23.04:
  
  ~/.pam_environment does not exist
  
  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC="en_US.UTF-8"
  LC_TIME="en_US.UTF-8"
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY="en_US.UTF-8"
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT="en_US.UTF-8"
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=
  
- 
  * Open gnome-language-selector, click on the "Regional Formats" tab, and 
click on the "Display numbers, dates and currency in the usual format for" list 
and select "English (Canada)"
  * Press on the Close button
  
- $ cat .pam_environment 
+ $ cat .pam_environment
  LC_NUMERICDEFAULT=en_CA.UTF-8
  LC_TIME   DEFAULT=en_CA.UTF-8
  LC_MONETARY   DEFAULT=en_CA.UTF-8
  LC_PAPER  DEFAULT=en_CA.UTF-8
  LC_NAME   DEFAULT=en_CA.UTF-8
  LC_ADDRESSDEFAULT=en_CA.UTF-8
  LC_TELEPHONE  DEFAULT=en_CA.UTF-8
  LC_MEASUREMENTDEFAULT=en_CA.UTF-8
  LC_IDENTIFICATION DEFAULT=en_CA.UTF-8
  PAPERSIZE DEFAULT=letter
  
  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC="en_US.UTF-8"
  LC_TIME="en_US.UTF-8"
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY="en_US.UTF-8"
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT="en_US.UTF-8"
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=
  
- 
  * Sign out, and sign in
  
  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_CA.UTF-8
  LC_TIME=en_CA.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_CA.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_CA.UTF-8
  LC_NAME=en_CA.UTF-8
  LC_ADDRESS=en_CA.UTF-8
  LC_TELEPHONE=en_CA.UTF-8
  LC_MEASUREMENT=en_CA.UTF-8
  LC_IDENTIFICATION=en_CA.UTF-8
  LC_ALL=
  
  
  
- * Run this in the terminal: cp ~/.pam_environment ~/.pam_environment-canada
- * Open gnome-language-selector, click on the "Regional Formats" tab, and 
click on the "Display numbers, dates and currency in the usual format for" list 
and select "English (United States)"
- * Copy the old file: cp ~/.pam_environment-canada ~/.pam_environment
- * Log out/log in
- * `locale` variables is set to "en_CA"
- * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
- * Reboot
- * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
+ 
+ Step 2, demonstrate that ~/.pam_environment can be scripted
  
- How do you make the DE load the new settings from ~/.pam_environment to
- be visible in gnome-language-selector -> Regional Formats, the "Display
- numbers, dates and currency in the usual format for" list?
+ Run this in terminal:
+ 
+ sudo tee ~/.pam_environment > /dev/null << 'EOF'
+ LC_NUMERICDEFAULT=en_DK.UTF-8
+ LC_TIME   DEFAULT=en_DK.UTF-8
+ LC_MONETARY   DEFAULT=en_DK.UTF-8
+ LC_PAPER  DEFAULT=en_DK.UTF-8
+ LC_NAME   DEFAULT=en_DK.UTF-8
+ LC_ADDRESSDEFAULT=en_DK.UTF-8
+ LC_TELEPHONE  DEFAULT=en_DK.UTF-8
+ LC_MEASUREMENTDEFAULT=en_DK.UTF-8
+ LC_IDENTIFICATION DEFAULT=en_DK.UTF-8
+ PAPERSIZE DEFAULT=a4
+ EOF
+ 
+ * Sign out, and sign in to the desktop environment.
+ * $ locale
+ LANG=en_US.UTF-8
+ LANGUAGE=en_US
+ LC_CTYPE="en_US.UTF-8"
+ LC_NUMERIC=en_DK.UTF-8
+ LC_TIME=en_DK.UTF-8
+ LC_COLLATE="en_US.UTF-8"
+ LC_MONETARY=en_DK.UTF-8
+ LC_MESSAGES="en_US.UTF-8"
+ LC_PAPER=en_DK.UTF-8
+ LC_NAME=en_DK.UTF-8
+ LC_ADDRESS=en_DK.UTF-8
+ LC_TELEPHONE=en_DK.UTF-8
+ LC_MEASUREMENT=en_DK.UTF-8
+ LC_IDENTIFICATION=en_DK.UTF-8
+ LC_ALL=
+ 
+ 
+ Issue:
+ * Open gnome-language-selector, click on the "Regional Formats" tab, check 
the "Display numbers, dates and currency in the usual format for" list, it is 
not set to "English (Denmark)"
  
  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

** Description changed:

  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list, are
  stored in ~/.pam_environment
  
  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
- * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
- * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
+ 
+ * Default Ubuntu MATE 23.04:
+ 
+ ~/.pam_environment does not exist
+ 
+ $ locale
+ LANG=en_US.UTF-8
+ LANGUAGE=en_US
+ LC_CTYPE="en_US.UTF-8"
+ LC_NUMERIC="en_US.UTF-8"
+ LC_TIME="en_US.UTF-8"
+ LC_COLLATE="en_US.UTF-8"
+ LC_MONETARY="en_US.UTF-8"
+ LC_MESSAGES="en_US.UTF-8"
+ LC_PAPER="en_US.UTF-8"
+ LC_NAME="en_US.UTF-8"
+ LC_ADDRESS="en_US.UTF-8"
+ LC_TELEPHONE="en_US.UTF-8"
+ LC_MEASUREMENT="en_US.UTF-8"
+ LC_IDENTIFICATION="en_US.UTF-8"
+ LC_ALL=
+ 
+ 
+ * Open gnome-language-selector, click on the "Regional Formats" tab, and 
click on the "Display numbers, dates and currency in the usual format for" list 
and select "English (Canada)"
  * Press on the Close button
- * `locale` variables is set to "en_US"
- * cp ~/.pam_environment ~/.pam_environment-canada
- * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
- * cp ~/.pam_environment-canada ~/.pam_environment
- * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
+ 
+ $ cat .pam_environment 
+ LC_NUMERICDEFAULT=en_CA.UTF-8
+ LC_TIME   DEFAULT=en_CA.UTF-8
+ LC_MONETARY   DEFAULT=en_CA.UTF-8
+ LC_PAPER  DEFAULT=en_CA.UTF-8
+ LC_NAME   DEFAULT=en_CA.UTF-8
+ LC_ADDRESSDEFAULT=en_CA.UTF-8
+ LC_TELEPHONE  DEFAULT=en_CA.UTF-8
+ LC_MEASUREMENTDEFAULT=en_CA.UTF-8
+ LC_IDENTIFICATION DEFAULT=en_CA.UTF-8
+ PAPERSIZE DEFAULT=letter
+ 
+ $ locale
+ LANG=en_US.UTF-8
+ LANGUAGE=en_US
+ LC_CTYPE="en_US.UTF-8"
+ LC_NUMERIC="en_US.UTF-8"
+ LC_TIME="en_US.UTF-8"
+ LC_COLLATE="en_US.UTF-8"
+ LC_MONETARY="en_US.UTF-8"
+ LC_MESSAGES="en_US.UTF-8"
+ LC_PAPER="en_US.UTF-8"
+ LC_NAME="en_US.UTF-8"
+ LC_ADDRESS="en_US.UTF-8"
+ LC_TELEPHONE="en_US.UTF-8"
+ LC_MEASUREMENT="en_US.UTF-8"
+ LC_IDENTIFICATION="en_US.UTF-8"
+ LC_ALL=
+ 
+ 
+ * Sign out, and sign in
+ 
+ $ locale
+ LANG=en_US.UTF-8
+ LANGUAGE=en_US
+ LC_CTYPE="en_US.UTF-8"
+ LC_NUMERIC=en_CA.UTF-8
+ LC_TIME=en_CA.UTF-8
+ LC_COLLATE="en_US.UTF-8"
+ LC_MONETARY=en_CA.UTF-8
+ LC_MESSAGES="en_US.UTF-8"
+ LC_PAPER=en_CA.UTF-8
+ LC_NAME=en_CA.UTF-8
+ LC_ADDRESS=en_CA.UTF-8
+ LC_TELEPHONE=en_CA.UTF-8
+ LC_MEASUREMENT=en_CA.UTF-8
+ LC_IDENTIFICATION=en_CA.UTF-8
+ LC_ALL=
+ 
+ 
+ 
+ * Run this in the terminal: cp ~/.pam_environment ~/.pam_environment-canada
+ * Open gnome-language-selector, click on the "Regional Formats" tab, and 
click on the "Display numbers, dates and currency in the usual format for" list 
and select "English (United States)"
+ * Copy the old file: cp ~/.pam_environment-canada ~/.pam_environment
  * Log out/log in
  * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  
  How do you make the DE load the new settings from ~/.pam_environment to
  be visible in gnome-language-selector -> Regional Formats, the "Display
  numbers, dates and currency in the usual format for" list?
  
  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

** Description changed:

  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list, are
  stored in ~/.pam_environment
  
  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
+ * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
+ * `locale` variables is set to "en_US"
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
+ * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  
  How do you make the DE load the new settings from ~/.pam_environment to
  be visible in gnome-language-selector -> Regional Formats, the "Display
  numbers, dates and currency in the usual format for" list?
  
  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
  * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
  * `locale` variables is set to "en_US"
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
  * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"

  How do you make the DE load the new settings from ~/.pam_environment
  to be visible in gnome-language-selector -> Regional Formats, the
  "Display numbers, dates and currency in the usual format for" list?

  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2035212/+subscriptions


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

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
  * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
  * `locale` variables is set to "en_US"
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
  * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"

  How do you make the DE load the new settings from ~/.pam_environment
  to be visible in gnome-language-selector -> Regional Formats, the
  "Display numbers, dates and currency in the usual format for" list?

  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2035212/+subscriptions


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

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

** Description changed:

  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list, are
  stored in ~/.pam_environment
  
  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  
- How do you make the DE reload the new settings from ~/.pam_environment?
+ How do you make the DE load the new settings from ~/.pam_environment to
+ be visible in gnome-language-selector -> Regional Formats, the "Display
+ numbers, dates and currency in the usual format for" list?
  
  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
  * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
  * `locale` variables is set to "en_US"
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
  * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"

  How do you make the DE load the new settings from ~/.pam_environment
  to be visible in gnome-language-selector -> Regional Formats, the
  "Display numbers, dates and currency in the usual format for" list?

  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2035212/+subscriptions


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

[Desktop-packages] [Bug 2035212] Re: [Feature request]: Command line option

> Right, they are not loaded by Language Support because it grabs the
old value from something called accountsservice. So you kind of mess it
up if you change those variables in ~/.pam_environment manually.

Do you know how to do that with terminal commands so it can be scripted?


> But if you check it with the locale command, you'll find that the
Canadian locales are in effect.

Thanks, it is working! It possible to manually edit ~/.pam_environment,
it will show up in `locale` after you have signed out and signed back
in. However, you don't know 100% what is added by the gnome-language-
selector -> Regional Formats, the "Display numbers, dates and currency
in the usual format for" list. Therefore a command line option to change
the user locale would be useful.


> I have to ask: What is it you try to actually achieve?

I'm trying to change the locale from the command line so distros can be
configured with scripts, because GUIs are inconvenient when you are
evaluating a lot of distros in virt-manager.

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

Title:
  [Feature request]: Command line option

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  The settings for gnome-language-selector -> Regional Formats in the
  "Display numbers, dates and currency in the usual format for" list,
  are stored in ~/.pam_environment

  # How is it possible to make the DE reload the new values from 
~/.pam_environment
  So it's possible to modify ~/.pam_environment with a script. But how do you 
update the system to use the changes? Not even reboot worked. This issue can 
manually be evaluated in order to make sure that the file content is correct:
  * `locale` variables is set to "en_US" -- if you installed the distro with 
the default settings
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (Canada)"
  * Press on the Close button
  * `locale` variables is set to "en_US"
  * cp ~/.pam_environment ~/.pam_environment-canada
  * Set gnome-language-selector -> Regional Formats in the "Display numbers, 
dates and currency in the usual format for" list to "English (United States)"
  * cp ~/.pam_environment-canada ~/.pam_environment
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Log out/log in
  * `locale` variables is set to "en_CA"
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"
  * Reboot
  * Open gnome-language-selector -> Regional Formats, the "Display numbers, 
dates and currency in the usual format for" is still set to "English (United 
States)"

  How do you make the DE load the new settings from ~/.pam_environment
  to be visible in gnome-language-selector -> Regional Formats, the
  "Display numbers, dates and currency in the usual format for" list?

  # [Feature request]: Implement command line option
  Implemented command line options, for both user and system-wide settings, 
would be useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2035212/+subscriptions


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

[Desktop-packages] [Bug 1841810] Re: Ubuntu login screen does not show full name if it's slightly too long (but not really that long)

2023-09-13 Thread Bug Watch Updater

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2237846.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-09-07T09:50:47+00:00 dominik wrote:

gdm displays only user logins instead of their Names for any users who
have a hyphen in their Name.


Reproducible: Always

Steps to Reproduce:
1. Launch GNOME Control Center Users tab (gnome-control-center users)
2. Put something with a hyphen (-) in your Name (e.g. John Foo-Bar)
3. Log out and see the list of users at the login screen

Actual Results:  
Any name with a hyphen (e.g. John Foo-Bar) is not displayed. Instead only login 
name is displayed

Expected Results:  
All names, including those with hyphens and other special characters should be 
displayed.

gdm-44.1-1.fc38.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1841810/comments/4


On 2023-09-07T10:30:45+00:00 dominik wrote:

To avoid confusion:
user login = username (i.e. what you type to log in)
user Name = user display name (descriptive text about user, usually their name, 
a.k.a. GECOS field)

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1841810/comments/5


On 2023-09-07T11:05:42+00:00 dominik wrote:

So the actual issue is not with the hyphen or special characters
but the length of the display name.

Thanks to @fmuellner for informing me of that "feature".

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1841810/comments/6


On 2023-09-07T11:08:18+00:00 dominik wrote:

The user display name that I saw this bug with has 29 characters, so please try 
reproducing with something like:
Abbey Westington-Cloverfield

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1841810/comments/7


On 2023-09-13T07:58:32+00:00 dominik wrote:

This was moved to gnome-shell upstream so moving in Fedora as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1841810/comments/8


** Changed in: gnome-shell (Fedora)
   Status: Unknown => Confirmed

** Changed in: gnome-shell (Fedora)
   Importance: Unknown => Medium

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

Title:
  Ubuntu login screen does not show full name if it's slightly too long
  (but not really that long)

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

Bug description:
  I use Ubuntu 18.04 LTS with gdm3 3.28.3

  My native language is Spanish and my fullname use accents and hyphens
  (Néstor Rodríguez-Triana Domínguez) but it not appear in the gdm3
  login screen, only my username (nrtriana). My locale is configured
  properly as:

  LANG=es_ES.UTF-8
  LANGUAGE=es_ES
  LC_CTYPE="es_ES.UTF-8"
  LC_NUMERIC="es_ES.UTF-8"
  LC_TIME="es_ES.UTF-8"
  LC_COLLATE="es_ES.UTF-8"
  LC_MONETARY="es_ES.UTF-8"
  LC_MESSAGES="es_ES.UTF-8"
  LC_PAPER="es_ES.UTF-8"
  LC_NAME="es_ES.UTF-8"
  LC_ADDRESS="es_ES.UTF-8"
  LC_TELEPHONE="es_ES.UTF-8"
  LC_MEASUREMENT="es_ES.UTF-8"
  LC_IDENTIFICATION="es_ES.UTF-8"
  LC_ALL=es_ES.UTF-8

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


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

[Desktop-packages] [Bug 2035341] Re: gnome-shell crashed with signal 5 in g_log_structured_array()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2034672, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700542/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700544/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700548/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700549/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700550/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700552/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2035341/+attachment/5700553/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 2034672
   gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Mantic Minotaur (development branch) live cd boot

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 09:42:36 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Desktop-packages] [Bug 2033719] Re: Mouse pointer stutters in gnome-shell 45~beta.1 and rc

My new favourite solution is proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3274

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

Title:
  Mouse pointer stutters in gnome-shell 45~beta.1 and rc

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

Bug description:
  The mouse pointer stutters in gnome-shell 45~beta.1 on a lot of
  machines.

  Workaround:

  Put this in /etc/environment and reboot:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

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


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

[Desktop-packages] [Bug 2032812] Re: [FFe] libreoffice 7.6.x for mantic

2023-09-13 Thread Rico Tzschichholz

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

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

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

Title:
  [FFe] libreoffice 7.6.x for mantic

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Libreoffice releases are quite in sync with the Ubuntu release
  schedule and every Ubuntu release receives its new "major" update.

  This cycle there are a few issues. As precaution to prevent breaking
  the archive and blocking transitions the upload is delayed until
  further notice.

  Hereby I am asking for permission to upload libreoffice 7.6.x for
  23.10/mantic when it is ready.

  The package will be prepared at
  https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
  
prereleases/+packages?field.name_filter=_filter=published_filter=mantic

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


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

[Desktop-packages] [Bug 2035036] Re: [Mantic] dark theme not applied on some apps

2023-09-13 Thread Francois Thirioux

Please not that accent colors are not applied to Shell (in apps it's ok).
>From Appearance tab in g-c-c.
Don't know if I have to open another bug.

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

Title:
  [Mantic] dark theme not applied on some apps

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  GS 45 rc, latest up to date, Mantic

  When I apply dark theme through usual quick settings, some apps become
  dark (Firefox, Tweaks, System Monitor...) some do not (Synaptic,
  wxMaxima, NVidia settings...).

  Was ok some time ago in Mantic with GS 45.

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


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

[Desktop-packages] [Bug 2035300] Re: CVE-2023-4863: Heap buffer overflow in libwebp

2023-09-13 Thread Nishit Majithia

Hi @madmike77, Thank you for reporting the issue. The team is working on
it and will publish the new Firefox release with the fixes asap.

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

Title:
  CVE-2023-4863: Heap buffer overflow in libwebp

Status in firefox package in Ubuntu:
  New

Bug description:
  Mozilla released a new version under https://www.mozilla.org/en-
  US/security/advisories/mfsa2023-40/ fixing a critical bug.

  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ apt-cache policy firefox
  firefox:
    Installiert:   1:1snap1-0ubuntu2
    Installationskandidat: 1:1snap1-0ubuntu2
    Versionstabelle:
   *** 1:1snap1-0ubuntu2 500
  500 http://mirror.init7.net/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  As of now the latest version doesn't include this critical fix.

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


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

[Desktop-packages] [Bug 1841810] Re: Ubuntu login screen does not show full name if it's slightly too long (but not really that long)

2023-09-13 Thread Rathann

** Bug watch added: Red Hat Bugzilla #2237846
   https://bugzilla.redhat.com/show_bug.cgi?id=2237846

** Also affects: gnome-shell (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=2237846
   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/1841810

Title:
  Ubuntu login screen does not show full name if it's slightly too long
  (but not really that long)

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  I use Ubuntu 18.04 LTS with gdm3 3.28.3

  My native language is Spanish and my fullname use accents and hyphens
  (Néstor Rodríguez-Triana Domínguez) but it not appear in the gdm3
  login screen, only my username (nrtriana). My locale is configured
  properly as:

  LANG=es_ES.UTF-8
  LANGUAGE=es_ES
  LC_CTYPE="es_ES.UTF-8"
  LC_NUMERIC="es_ES.UTF-8"
  LC_TIME="es_ES.UTF-8"
  LC_COLLATE="es_ES.UTF-8"
  LC_MONETARY="es_ES.UTF-8"
  LC_MESSAGES="es_ES.UTF-8"
  LC_PAPER="es_ES.UTF-8"
  LC_NAME="es_ES.UTF-8"
  LC_ADDRESS="es_ES.UTF-8"
  LC_TELEPHONE="es_ES.UTF-8"
  LC_MEASUREMENT="es_ES.UTF-8"
  LC_IDENTIFICATION="es_ES.UTF-8"
  LC_ALL=es_ES.UTF-8

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


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

[Desktop-packages] [Bug 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

It's not surprising if 0908.2 doesn't have the workaround. It didn't
land for a day or so after that.

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Desktop-packages] [Bug 2035220] Re: cve-2023-4863

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Critical

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  cve-2023-4863

Status in chromium-browser package in Ubuntu:
  In Progress
Status in libwebp package in Ubuntu:
  New
Status in chromium package in Debian:
  New
Status in libwebp package in Debian:
  New

Bug description:
  [$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported 
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at 
The University of Torontoʼs Munk School on 2023-09-06
  
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html

  high profile remote vulnerability

  themusicgod1@eva1:~$ apt-cache policy chromium-browser
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:

  current available snap: 
  chromium 116.0.5845.179 

  fix is in:
  chromium 116.0.5845.187

  ubuntu: 22.04.3 LTS jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:38:06 2023
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   228G  162G   55G  75% /
   tmpfs  tmpfs  3.9G   66M  3.8G   2% /dev/shm
   /dev/sda2  ext4   228G  162G   55G  75% /
  InstallationDate: Installed on 2017-04-18 (2337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179 
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
  Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

Marking Firefox as fix released as well since now Firefox is on core22
and that was confirmed in earlier comments to solve the problem. Please
reset if observed otherwise.

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

Title:
  Hardware acceleration broken for amdgpu/mesa in snap

Status in ubuntu-spotify-app:
  New
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Possible, proposed solutions
  

  Option 1: Please install from these channels and report back with
  success or failure.

    snap refresh --channel candidate/core22 firefox

  Option 2:

    chromium --ozone-platform=wayland
    MOZ_ENABLE_WAYLAND=1 firefox

  If nothing works, it is possible around the issue by disabling
  hardware acceleration.

  Original bug report
  ---

  Snap packages which use hardware accelerated graphics are broken after
  the last routine system upgrade via apt. My system is using AMD Radeon
  RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
  Two snap packages which are now unusable are Mozilla Firefox and
  Chromium browsers. Both display animated speckled color garbage inside
  their windows, overlayed with the correct image. Disabling hardware
  acceleration in the settings for the snap version of Firefox fixed it.
  Also, Firefox version installed from the original Mozilla tarball into
  /opt/ works just fine with the acceleration enabled on the same
  system, as well as glmark2 benchmark. Looks like the issue is only
  affecting snap packages.

  $ snap list firefox chromium
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  109.0.5414.119  2295  latest/stable  canonical✓  -
  firefox   109.0.1-1   2311  latest/stable  mozilla✓-

  $ dpkg -l snapd|grep ^ii
  ii  snapd  2.58+22.10   amd64Daemon and tooling that enable 
snap packages

  $ dpkg -l mesa\* | grep ^ii
  ii  mesa-utils8.5.0-1   amd64Miscellaneous 
Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd64  8.5.0-1   amd64Miscellaneous 
Mesa utilities -- native applications
  ii  mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API 
video acceleration drivers
  ii  mesa-vdpau-drivers:amd64  22.2.5-0ubuntu0.1 amd64Mesa VDPAU video 
acceleration drivers
  ii  mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan 
graphics drivers

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.10
  Release:22.10
  Codename:   kinetic

  $ uname -a
  Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Feb  1 22:55:48 2023
  InstallationDate: Installed on 2020-08-02 (913 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 
640x480 640x480 640x480
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
   tmpfs  tmpfs   16G 0   16G   0% /dev/shm
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-08-02 (914 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" -

Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

Santiago, Spotify is proprietary, there is nothing for us to do. You 
have to request them to update their base from core20 to core22. 
According to 'snap info spotify', their contact link is 
https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux.

** No longer affects: snapd (Ubuntu)

** Changed in: firefox (Ubuntu)
   Status: Confirmed => 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/2004532

Title:
  Hardware acceleration broken for amdgpu/mesa in snap

Status in ubuntu-spotify-app:
  New
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Possible, proposed solutions
  

  Option 1: Please install from these channels and report back with
  success or failure.

    snap refresh --channel candidate/core22 firefox

  Option 2:

    chromium --ozone-platform=wayland
    MOZ_ENABLE_WAYLAND=1 firefox

  If nothing works, it is possible around the issue by disabling
  hardware acceleration.

  Original bug report
  ---

  Snap packages which use hardware accelerated graphics are broken after
  the last routine system upgrade via apt. My system is using AMD Radeon
  RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
  Two snap packages which are now unusable are Mozilla Firefox and
  Chromium browsers. Both display animated speckled color garbage inside
  their windows, overlayed with the correct image. Disabling hardware
  acceleration in the settings for the snap version of Firefox fixed it.
  Also, Firefox version installed from the original Mozilla tarball into
  /opt/ works just fine with the acceleration enabled on the same
  system, as well as glmark2 benchmark. Looks like the issue is only
  affecting snap packages.

  $ snap list firefox chromium
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  109.0.5414.119  2295  latest/stable  canonical✓  -
  firefox   109.0.1-1   2311  latest/stable  mozilla✓-

  $ dpkg -l snapd|grep ^ii
  ii  snapd  2.58+22.10   amd64Daemon and tooling that enable 
snap packages

  $ dpkg -l mesa\* | grep ^ii
  ii  mesa-utils8.5.0-1   amd64Miscellaneous 
Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd64  8.5.0-1   amd64Miscellaneous 
Mesa utilities -- native applications
  ii  mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API 
video acceleration drivers
  ii  mesa-vdpau-drivers:amd64  22.2.5-0ubuntu0.1 amd64Mesa VDPAU video 
acceleration drivers
  ii  mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan 
graphics drivers

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.10
  Release:22.10
  Codename:   kinetic

  $ uname -a
  Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Feb  1 22:55:48 2023
  InstallationDate: Installed on 2020-08-02 (913 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 
640x480 640x480 640x480
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
   tmpfs  tmpfs   16G 0   16G   0%

[Desktop-packages] [Bug 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

2023-09-13 Thread Chris Guiver

I attempted an install QA test of Ubuntu Desktop mantic daily (0908.2) on
- hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)

I didn't see the installer, briefly got one error message (didn't have
time to recognize/read), then screen went white with oh no, something
went wrong... and I was kicked from gnome..

I've tagged this bug report, as I got 502 server errors on ubuntu-bug;
and looking it looks like this is what I had anyway.

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Desktop-packages] [Bug 2035310] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2035310/+attachment/5700513/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2035310/+attachment/5700501/+files/CoreDump.gz

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  gnome-session-binary crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Just started, no apps active

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-session-bin 44.0-4ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 08:02:26 2023
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-09-08 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230904.2)
  ProcCmdline: /usr/libexec/gnome-session-binary --systemd-service 
--session=ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fe746724c41 
:  mov(%rax),%rax
   PC (0x7fe746724c41) ok
   source "(%rax)" (0x7fe0d273ef17) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-session-binary crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Desktop-packages] [Bug 2035310] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/2035310/+attachment/5700512/+files/StacktraceSource.txt

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

Title:
  gnome-session-binary crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Just started, no apps active

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-session-bin 44.0-4ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 08:02:26 2023
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-09-08 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230904.2)
  ProcCmdline: /usr/libexec/gnome-session-binary --systemd-service 
--session=ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fe746724c41 
:  mov(%rax),%rax
   PC (0x7fe746724c41) ok
   source "(%rax)" (0x7fe0d273ef17) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-session-binary crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Desktop-packages] [Bug 2035310] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2035310/+attachment/5700511/+files/Stacktrace.txt

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

Title:
  gnome-session-binary crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Just started, no apps active

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-session-bin 44.0-4ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 08:02:26 2023
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-09-08 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230904.2)
  ProcCmdline: /usr/libexec/gnome-session-binary --systemd-service 
--session=ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fe746724c41 
:  mov(%rax),%rax
   PC (0x7fe746724c41) ok
   source "(%rax)" (0x7fe0d273ef17) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-session-binary crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Desktop-packages] [Bug 2035310] gnome-session-binary crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()