[Desktop-packages] [Bug 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.

[Launchpad Bug Tracker]

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

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

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

Title:
  Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
  Xorg.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
  and the other bug report that is linked there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 07:17:22 2023
  DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
  InstallationDate: Installed on 2021-05-25 (899 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 1.15
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.15
  dmi.board.name: FJNB288
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.name: LIFEBOOK T935
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1967456] Re: Jammy (and Mantic) doesn't use nvidia driver when executing firefox

[Gon Solo]

Also Google Maps can't be run in 3D mode with llvmpipe. It works with
Firefox Nightly from Mozilla.

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

Title:
  Jammy (and Mantic) doesn't use nvidia driver when executing firefox

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  [Reproduce step]

  1. Install Jammy beta.
  2. Install Nvidia driver by ubuntu-driver install.
  3. Connect monitor to dGPU output port.
  4. Run firefox, type "about:support" in url, and check column "GPU #1"

  [Expected result]

  should see nvidia driver info.

  [Actual result]

  still use llvmpipe

  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1186 F pulseaudio
   /dev/snd/controlC1:  u  1186 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 00:07:47 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: HP HP Z2 Mini G5 Workstation
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: HP
  dmi.bios.version: S50 Ver. 01.00.01
  dmi.board.name: 8754
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.08.03
  dmi.chassis.type: 2
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.8
  dmi.modalias: 
dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z2 Mini G5 Workstation
  dmi.product.sku: 9JD38AV
  dmi.sys.vendor: HP

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


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

[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

[Luis Alvarado]

Same thing is happening here with an Asus Z790. It was working properly
on 23.04. Not on 23.10 the sound works like this:

HiFi 2.0 - Very low sound. I have to crank the sound to max to barely hear it.
HiFi 5.1 - Only the front ones sound (but they sound around 60% when the volume 
is at 100%, meaning, the actual volume of them is not full). The rear speakers 
dont even sound. You have to put your ear to the actual speaker to hear it.
HiFi 7.1 - The front ones work correctly but any others do not.

The headphones still work correctly via bluetooth, but the whole sound
experience basically is dead. Everything is either very low or speaker
mode or nothing at all.

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

[Launchpad Bug Tracker]

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

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

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Desktop-packages] [Bug 2043928] [NEW] mtxdoc.sty in texlive-music

[Lippolis Giuseppe]

Public bug reported:

I'm compiling a latex file 
(https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiax72KxdCCAxUpgP0HHW2ADR0QFnoECBgQAQ&url=https%3A%2F%2Fctan.math.washington.edu%2Ftex-archive%2Fsupport%2Fm-tx%2Fdoc%2Fmtxdoc.ltx&usg=AOvVaw0G5ert5C3-XAwfcEbkoRI9&opi=89978449)
 using pdflatex.
During the compilation I got this error:

! LaTeX Error: File `mtxdoc.sty' not found.

Type X to quit or  to proceed,

The "mtxdoc.sty" is actually present in texlive-music package and I
found it in /usr/share/doc/texlive-doc/generic/m-tx/mtxdoc.sty but
texlive is unable to find it.

my configuration:
lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: latex

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

Title:
  mtxdoc.sty in texlive-music

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  I'm compiling a latex file 
(https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiax72KxdCCAxUpgP0HHW2ADR0QFnoECBgQAQ&url=https%3A%2F%2Fctan.math.washington.edu%2Ftex-archive%2Fsupport%2Fm-tx%2Fdoc%2Fmtxdoc.ltx&usg=AOvVaw0G5ert5C3-XAwfcEbkoRI9&opi=89978449)
 using pdflatex.
  During the compilation I got this error:

  ! LaTeX Error: File `mtxdoc.sty' not found.

  Type X to quit or  to proceed,

  The "mtxdoc.sty" is actually present in texlive-music package and I
  found it in /usr/share/doc/texlive-doc/generic/m-tx/mtxdoc.sty but
  texlive is unable to find it.

  my configuration:
  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/2043928/+subscriptions


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

[Desktop-packages] [Bug 2043942] [NEW] Primary screen does not resume (post power management)

[Daniel LaSalle]

Public bug reported:

On a laptop with a HDMI screen plugged (using same image on all monitors):
It seems that after power management feature kicks in (in my case a blank 
screen) and actions are resumed that the original (laptop) screen remains with 
a full light grey and is unusable.

Recreation steps:
1. plug in a hdmi monitor into the hdmi plug of your laptop;
2. while the laptop remains charged+plugged in the wall watch something with 
celluloid then resume in 2+ hours;
3. on external screen: full working desktop with mouse cursor and colors;
on laptop screen: full light grey screen, no life

nb: by totally unplugging (power and hdmi cable) the laptop it screen remains 
unusable but TTY1-6 will work.
By replugging both cables the desktop will again show on the external screen 
but laptop screen will remain unusable.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov 19 15:45:00 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (270 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (38 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias: 
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

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

Title:
  Primary screen does not resume (post power management)

Status in xorg package in Ubuntu:
  New

Bug description:
  On a laptop with a HDMI screen plugged (using same image on all monitors):
  It seems that after power management feature kicks in (in my case a blank 
screen) and actions are resumed that the original (laptop) screen remains with 
a full light grey and is unusable.

  Recreation steps:
  1. plug in a hdmi monitor into the hdmi plug of your laptop;
  2. while the laptop remains charged+plugged in the wall watch something with 
celluloid then resume in 2+ hours;
  3. on external screen: full working desktop with mouse cursor and colors;
  on laptop screen: full light grey screen, no life

  nb: by totally unplugging (power and hdmi cable) the laptop it screen remains 
unusable but TTY1-6 will work.
  By replugging both cables the desktop will again show on the external screen 
but laptop screen will remain unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Nov 19

[Desktop-packages] [Bug 2043944] [NEW] WISHLIST-Make MOD+LEFT|RIGHT great

[Daniel LaSalle]

Public bug reported:

Dear Santa,

This year I have been augmenting my TTY7 keyboard skillz and in that
respect the MOD+arrow key resizing capabilities.

As we know pressing MOD+right arrow shall flawlessly redraw the
currently selected window into half of the right side of the screen.

Based on my user expertise each and every time I invoke it I always
always always end up having to ALT+TAB to another window that I will
then MOD+left arrow to complement it. And so that I can see both windows
simultaneously.

My wish for this year is to automate the ALT+TAB part yet I have to ask
if this a X feature or if it's a MATE feature or ...? In that respect
this as a xorg bug.

But back to the problem: Redmond has got this feature implemented
already on their end. From our end it just currently looks like it's
halfway implemented. If not made a default behavior then for sure there
should be a way to allow the automated resizing of a 2nd screen once any
combination of the MOD+arrow keys will have been typed.

Cheers,

'lil Dan

PS: by "MOD" I mean the "windoze key" AKA MOD4?

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov 19 15:55:14 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (270 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (38 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias: 
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

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

Title:
  WISHLIST-Make MOD+LEFT|RIGHT great

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear Santa,

  This year I have been augmenting my TTY7 keyboard skillz and in that
  respect the MOD+arrow key resizing capabilities.

  As we know pressing MOD+right arrow shall flawlessly redraw the
  currently selected window into half of the right side of the screen.

  Based on my user expertise each and every time I invoke it I always
  always always end up having to ALT+TAB to another window that I will
  then MOD+left arrow to complement it. And so that I can see both
  windows simultaneously.

  My wish for this year is to automate the ALT+TAB part yet I have to
  ask if this a X feature or if it's a MATE feature or ...? In that
  respect this as a xorg bug.

  But back to the problem: Redmond has got this feature implemented
  already on their end. From our end it just currently looks like it's
  halfway implemented. If not made a default behavior then for sure
  there should be a way to allow the automated resizing of a 2nd screen
  once any combination of t

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[Kerem B]

I have this issue also. Hereby some info over my case:
- This only happens with the device "ID 1b1c:1bac Corsair CORSAIR KATAR PRO XT 
Gaming Mouse". I also have a Logitech M330 and I never have the issue using 
that one. I don't think the Corsair mouse is defect though, because I use it 
also with a Windows PC and it works perfectly there.
- The freeze is for the complete screen, not just the cursor. Sometimes it is 
several seconds long, sometimes a short stutter.
- I don't find anything in systemd journal when this happens.
- My network device also stops during the freezes. If I am streaming radio with 
Rhythmbox I get a seek error.
- It never happened when I am in a game. Only during desktop use.

OS: Ubuntu 22.04.3 LTS x86_64 
Kernel: 6.2.0-36-generic
GPU: AMD ATI Radeon RX 6600/6600 XT/6600M
DE: GNOME 42.9
MESA: 23.0.4

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Noctis Bennington]

How much do we have to wait if this fix is already released but not in
Ubuntu 23.10?

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)

[Noctis Bennington]

I opened a report here in freedesktop:

https://gitlab.freedesktop.org/drm/amd/-/issues/2993#note_2172154

And as Michel Dänzer says, it's possible this is an issue related to
Mutter. Here in these logs from journalctl gnome-shell I attach here,
you can see the messages that appear just when, upon opening a game in
fullscreen, the screen 'disconnects'.


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2993
   https://gitlab.freedesktop.org/drm/amd/-/issues/2993

** Attachment added: "journalctl gnome shell when fullscreen.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+attachment/5721046/+files/journalctl%20gnome%20shell%20when%20fullscreen.txt

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

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

Title:
  [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
  screen (no screen detected)

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

Bug description:
  When I go into "fullscreen" watching a video while browsing in Firefox
  or when playing a game through Steam (fullscreen mode), the screen
  goes black.

  The workaround I have discovered to get back is to enter the gdm from
  "Ctrl + alt + F1" and then return to the session you were in
  (normally, "Ctrl + alt + F2).

  Edit: It happens when I connect a second monitor and use it as the
  primary display while the laptop screen is disabled.

  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  noctis 2095 F wireplumber
   /dev/snd/controlC0:  noctis 2095 F wireplumber
   /dev/snd/seq:noctis 2090 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:00:55 2023
  InstallationDate: Installed on 2023-10-13 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 amdgpudrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17EKAMS.101
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17EK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
  dmi.product.family: Al
  dmi.product.name: Alpha 17 A4DEK
  dmi.product.sku: 17EK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Sean Lanigan]

I have tested evince 42.3-0ubuntu3.1 and apparmor 3.0.4-2ubuntu2.3 from
jammy-proposed, the bug appears to be fixed - I can now click hyperlinks
from PDFs in Evince and Firefox as a Snap package correctly opens a new
tab

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  Fix Committed
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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

[Desktop-packages] [Bug 1859879] Re: PNG images are not displayed

[Bug Watch Updater]

** Changed in: ubuntuone-shotwell-plugin
   Status: New => Fix Released

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

Title:
  PNG images are not displayed

Status in ubuntuone-shotwell-plugin:
  Fix Released
Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  1) Ubuntu 19.10
  2) Shotwell 0.30.7 – “Celle”
  3) If I click on a .png file, shotwell opens and displays "No photos/videos". 
It does not display the png image. If I click on .jpg/.tif/.bmp files, shotwell 
opens and displays the jpg/tif/bmp images. If I drag/drop the .png file into 
Firefox, Firefox displays the .png image.
  4) Shotwell should display the .png image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1859879/+subscriptions


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

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

[ExploreWiki]

It's still happening on 23.10 for me

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

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

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

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

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

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

  -

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

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

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

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

[Atlas Yu]

Hi Nitin,

Our next LTS release 24.04[1] will be based on debian's trixie/sid[2],
and this patch is contained since 1.29.1[3]. The libmbim packages in
trixie/sid is based on the upstream tag 1.30.0[4]. So, I suppose it
would be available in our next LTS release (Ubuntu 24.04).

Reference:
1. base-files/os_release:
https://git.launchpad.net/ubuntu/+source/base-files/tree/etc/os-release?h=applied/ubuntu/noble
2. base-files/debian_version:
https://git.launchpad.net/ubuntu/+source/base-files/tree/etc/debian_version?h=applied/ubuntu/noble
3. the related git commit:
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/commit/910db9cb2b6fde303d3b4720890cf6dc6fc00880
4. libmbin versions in debian:
https://packages.debian.org/search?suite=all&searchon=names&keywords=libmbim

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM
  7560), and Lenovo are struggling to give a decent way to run the FCC
  unlock service without this.

  Until the device is unlocked, the end users are not able to use the
  SIM cards, and some of the affected devices have already been shipped.
  The end users now have to go to the Lenovo support website and
  download a few scripts and binaries to unlock the device to make their
  SIM cards work.

  The Lenovo wants this patch to be included in jammy, then they can
  provide the FCC unlock service and manage it in OEM-archive, so the
  end users can use SIM cards as soon as they receive the laptop.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
    - when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

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


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

[Desktop-packages] [Bug 2043951] [NEW] very slow when charger isn't connect

[Thwin Lin Htet]

Public bug reported:

very slow error my ryzen 7 5700U laptop

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 20 09:56:18 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-10-19 (31 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  very slow when charger isn't connect

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  very slow error my ryzen 7 5700U laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 09:56:18 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-10-19 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 26571] Re: No Sound (realtek ALC861 chip on P5GD1 pro)

[sana balti]

No audio at all. I've tried everything following the GPT guide, but nothing 
helps.

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

Title:
  No Sound (realtek ALC861 chip on P5GD1 pro)

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  No sound, i.e. sound card not properly detected 
  can't really say much about that - tried to google
  for alsa realtek alc861 and there are postings about
  a working driver which i couldn't track down
  (too many broken links).

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


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

[Desktop-packages] [Bug 26571] Re: No Sound (realtek ALC861 chip on P5GD1 pro)

[sana balti]

"No audio at all. I've tried everything following the GPT guide, but nothing 
helps." ubuntu 22.04.3
lts

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

Title:
  No Sound (realtek ALC861 chip on P5GD1 pro)

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  No sound, i.e. sound card not properly detected 
  can't really say much about that - tried to google
  for alsa realtek alc861 and there are postings about
  a working driver which i couldn't track down
  (too many broken links).

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


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

[Desktop-packages] [Bug 2043958] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT") from IA__FcConfigCreate() from FcInitLoadOwnConfig() from FcInitLoadOwnConfigAndFonts() fro

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: lunar mantic noble

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT")
  from IA__FcConfigCreate() from FcInitLoadOwnConfig() from
  FcInitLoadOwnConfigAndFonts() from IA__FcInitLoadConfigAndFonts()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2043957] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv("XDG_CONFIG_HOME") from FcConfigXdgConfigHome() from FcParseInclude() from FcEndElement() from doContent()

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: mantic

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("XDG_CONFIG_HOME")
  from FcConfigXdgConfigHome() from FcParseInclude() from FcEndElement()
  from doContent()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2043956] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from startParsi

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: impish jammy kinetic lunar mantic

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG")
  from getDebugLevel() from ENTROPY_DEBUG() from
  generate_hash_secret_salt() from startParsing()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2039340] Re: gnome-shell (login screen) crashes with SIGSEGV in __GI_getenv("EXPAT_ACCOUNTING_DEBUG")

[Daniel van Vugt]

This is probably fixed by the fix for bug 2036651.

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

Title:
  gnome-shell (login screen) crashes with SIGSEGV in
  __GI_getenv("EXPAT_ACCOUNTING_DEBUG")

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Last time I hacked around a bug like this, it had portions in PAM,
  apparmor, Seahorse, and Gnome so this time I'd like someone more
  focused on broad stability to look at things.

  The problem is simple.  Before the upgrade to 23.10, I could log in
  using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org"
  WMs.  Now I can't.  I can still login using XFCE and TTY.

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


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

[Desktop-packages] [Bug 2036651] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from guess_category_value() from __dcigettext()

[Daniel van Vugt]

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

** Tags added: fixed-in-gnome-shell-46 fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from
  guess_category_value() from __dcigettext()

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

Bug description:
  Crash on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Sep 19 22:38:53 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-09-12 (7 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f706ee45e6d <__GI_getenv+77>:   cmp
(%rbx),%r12b
   PC (0x7f706ee45e6d) ok
   source "(%rbx)" (0x55fd90525) not located in a known VMA region (needed 
readable region)!
   destination "%r12b" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=name@entry=0x7f706efc0257 "LANGUAGE") at 
./stdlib/getenv.c:31
   guess_category_value (categoryname=0x7f706efa5493 <_nl_category_names+51> 
"LC_MESSAGES", category=5) at ./intl/dcigettext.c:1569
   __dcigettext (domainname=0x7f706f79e126 "glib20", msgid1=0x7f706f985c68 "The 
sockets address family to use for socket construction", msgid2=0x0, plural=0, 
n=0, category=5) at ./intl/dcigettext.c:647
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_type_class_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: Upgraded to mantic on 2023-09-18 (1 days ago)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2027830] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("MESSAGES_DEBUG") from [g_getenv() from] should_drop_message()

[Daniel van Vugt]

This is probably fixed by the fix for bug 2036651.


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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("MESSAGES_DEBUG") from
  [g_getenv() from] should_drop_message()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  New install today.  Tested switching to another user on this system
  which was successful but when I switch back this crash was waithing.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 44.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Jul 14 14:58:47 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-07-14 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230712.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f8686e3f95d <__GI_getenv+173>:  cmp
(%rbx),%r12w
   PC (0x7f8686e3f95d) ok
   source "(%rbx)" (0x37970fcf9c425fae) not located in a known VMA region 
(needed readable region)!
   destination "%r12w" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7f86877a93e7 "MESSAGES_DEBUG") at ./stdlib/getenv.c:84
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_writer_default () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2034524] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTITY_DEBUG") from getDebugLevel() from parserInit()

[Daniel van Vugt]

This is probably fixed by the fix for bug 2036651.

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTITY_DEBUG")
  from getDebugLevel() from parserInit()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashes when session is locked - either manually or as a
  result of a timeout event as configured under security/power
  management settings.

  Session is lost I have to log back in once this happens.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  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
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Sep  6 08:34:06 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1693259374
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-09-26 (345 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7f8a241b7def "EXPAT_ENTITY_DEBUG") at 
./stdlib/getenv.c:31
   ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
   ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
   ??? () at /lib/x86_64-linux-gnu/libexpat.so.1
   ??? () at /lib/x86_64-linux-gnu/libfontconfig.so.1
  UpgradeStatus: Upgraded to mantic on 2023-06-16 (82 days ago)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 2043958] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT") from IA__FcConfigCreate() from FcInitLoadOwnConfig() from FcInitLoadOwnConfigAndFonts() from

[Daniel van Vugt]

Likely fixed with bug 2036651.

** Summary changed:

- 
/usr/bin/gnome-shell:11:__GI_getenv:IA__FcConfigCreate:FcInitLoadOwnConfig:FcInitLoadOwnConfigAndFonts:IA__FcInitLoadConfigAndFonts
+ gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT") from 
IA__FcConfigCreate() from FcInitLoadOwnConfig() from 
FcInitLoadOwnConfigAndFonts() from IA__FcInitLoadConfigAndFonts()

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT")
  from IA__FcConfigCreate() from FcInitLoadOwnConfig() from
  FcInitLoadOwnConfigAndFonts() from IA__FcInitLoadConfigAndFonts()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2043957] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("XDG_CONFIG_HOME") from FcConfigXdgConfigHome() from FcParseInclude() from FcEndElement() from doContent()

[Daniel van Vugt]

Likely fixed with bug 2036651.

** Summary changed:

- 
/usr/bin/gnome-shell:11:__GI_getenv:FcConfigXdgConfigHome:FcParseInclude:FcEndElement:doContent
+ gnome-shell crashed with SIGSEGV in __GI_getenv("XDG_CONFIG_HOME") from 
FcConfigXdgConfigHome() from FcParseInclude() from FcEndElement() from 
doContent()

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("XDG_CONFIG_HOME")
  from FcConfigXdgConfigHome() from FcParseInclude() from FcEndElement()
  from doContent()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2043956] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from startParsing

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/gnome-shell:11:__GI_getenv:getDebugLevel:ENTROPY_DEBUG:generate_hash_secret_salt:startParsing
+ gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from 
getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from 
startParsing()

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG")
  from getDebugLevel() from ENTROPY_DEBUG() from
  generate_hash_secret_salt() from startParsing()

Status in gnome-shell package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()

[Daniel van Vugt]

At least errors.ubuntu.com suggests there are zero of these crashes in
45.1

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
  st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
  from GjsAutoPointer()

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Fedora:
  Confirmed

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

  #0  0x7f3aa429dd82 in clutter_actor_remove_effect 
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at 
../clutter/clutter/clutter-actor.c:14830
  __inst = 0x55d6101c48a0
  __t = 94377826055744
  __r = 
  _g_boolean_var_274 = 
  __func__ = "clutter_actor_remove_effect"
  #1  0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at 
../src/st/st-scroll-view.c:246
  priv = 0x55d60fa59a00
  #2  0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at 
../../../gobject/gobject.c:3891
  _pp = 
  gaig_temp = 
  gaig_temp = 
  weak_locations = 
  nqueue = 0x55d60fa6da60
  _ptr = 
  object = 0x55d60fa59e90
  old_ref = 
  retry_atomic_decrement1 = 
  __func__ = "g_object_unref"
  #3  0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, &g_object_unref, 
&g_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
  old_ptr = 
  #4  GjsAutoPointer<_GObject, void, &g_object_unref, 
&g_object_ref>::~GjsAutoPointer (this=, this=) at 
../gjs/jsapi-util.h:172
  No locals.
  #5  GjsSmartPointer<_GObject>::~GjsSmartPointer (this=, 
this=) at ../gjs/jsapi-util.h:349
  No locals.
  #6  ObjectInstance::release_native_object (this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
  No locals.
  #7  ObjectInstance::release_native_object (this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
  No locals.
  #8  0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
  was_using_toggle_refs = false
  had_toggle_up = false
  had_toggle_down = 
  had_toggle_up = 
  had_toggle_down = 
  was_using_toggle_refs = 
  #9  GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
  No locals.
  #10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820, 
this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
  query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6 
"StScrollView", class_size = 664, instance_size = 48}
  query = 
  _g_boolean_var_74 = 
  #11 GIWrapperBase::finalize 
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
  priv = 0x55d60fa0ce80

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


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

[Desktop-packages] [Bug 1904547] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_

[Daniel van Vugt]

Looks like this was fixed by https://gitlab.gnome.org/GNOME/gnome-
control-center/-/merge_requests/899 a couple of years ago.

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  cc_display_config_get_panel_orientation_managed() from
  reset_current_config() from on_screen_changed() from
  on_screen_changed() from g_closure_invoke()

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Debian:
  New

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

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


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

[Desktop-packages] [Bug 2043599] Re: snap anydesk creates gray zone on my pc

[Daniel van Vugt]

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

I'm going to assume this is bug 2012388.

** This bug has been marked a duplicate of bug 2012388
   X11 window (usually AnyDesk) at top-right of the screen is invisible and 
steals mouse clicks

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

Title:
  snap anydesk creates gray zone on my pc

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  eta.Rectangle is deprecated, use Mtk.Rectangle instead
  2023-11-15T15:58:57.390111+00:00 fm-pc gnome-shell[3123]: message repeated 4 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T15:58:57.390656+00:00 fm-pc gnome-shell[3123]: Window manager 
warning: Ping serial 506432 was reused for window 0x203, previous use was 
for window 0x219.
  2023-11-15T15:59:03.476506+00:00 fm-pc ubuntu-report[2562]: level=error 
msg="data were not delivered successfully to metrics server, retrying in 480s"
  2023-11-15T16:01:16.179875+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:18.736925+00:00 fm-pc gnome-shell[3123]: message repeated 2 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:01:18.738491+00:00 fm-pc gnome-shell[3123]: Window manager 
warning: Ping serial 647791 was reused for window 0x3c03765, previous use was 
for window 0x3ca.
  2023-11-15T16:01:19.073417+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:20.001063+00:00 fm-pc gnome-shell[3123]: message repeated 2 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:01:22.046959+00:00 fm-pc systemd[2529]: 
snap.snap-store.snap-store-8f2738fb-1063-458d-b982-c6d88466650e.scope: Consumed 
3.497s CPU time.
  2023-11-15T16:01:22.052072+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:24.407957+00:00 fm-pc gnome-shell[3123]: message repeated 
113 times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:01:25.992272+00:00 fm-pc gnome-shell[3123]: 
polkitAuthenticationAgent: Received 2 identities that can be used for 
authentication. Only considering one.
  2023-11-15T16:01:31.556235+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:37.335480+00:00 fm-pc gnome-shell[3123]: message repeated 
118 times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:01:37.338969+00:00 fm-pc systemd[2529]: Started 
app-flatpak-com.google.Chrome-9774.scope.
  2023-11-15T16:01:37.351612+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:37.485373+00:00 fm-pc gnome-shell[3123]: message repeated 29 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:01:37.514093+00:00 fm-pc systemd[2529]: Started 
app-flatpak-com.google.Chrome-9817.scope.
  2023-11-15T16:01:37.556682+00:00 fm-pc flatpak-portal[4602]: 9817 already 
exited, skipping SpawnStarted
  2023-11-15T16:01:40.871833+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:01:41.132631+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:02:52.943490+00:00 fm-pc PackageKit: daemon quit
  2023-11-15T16:02:52.962371+00:00 fm-pc systemd[1]: packagekit.service: 
Deactivated successfully.
  2023-11-15T16:02:57.389909+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:02:57.391477+00:00 fm-pc gnome-shell[3123]: Window manager 
warning: Ping serial 746431 was reused for window 0x203, previous use was 
for window 0x219.
  2023-11-15T16:02:59.115367+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:03:23.630271+00:00 fm-pc gnome-shell[3123]: message repeated 2 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:03:23.631736+00:00 fm-pc gnome-shell[3123]: Window manager 
warning: Ping serial 772680 was reused for window 0x3ca, previous use was 
for window 0x3c03765.
  2023-11-15T16:03:26.543566+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:03:26.764547+00:00 fm-pc gnome-shell[3123]: message repeated 51 
times: [ Meta.Rectangle is deprecated, use Mtk.Rectangle instead]
  2023-11-15T16:03:27.986017+00:00 fm-pc gnome-shell[3123]: 
polkitAuthenticationAgent: Received 2 identities that can be used for 
authentication. Only considering one.
  2023-11-15T16:03:33.523813+00:00 fm-pc gnome-shell[3123]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
  2023-11-15T16:03:35.893063+00:00 fm-pc gnome-shell[3123]: mess

[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

[Daniel van Vugt]

That's not related to this bug. Please open a new bug.

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

Title:
  Mouse lag/stutter (missed frames) in Wayland sessions

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem
  didn't occur in previous version of ubuntu based on xorg.

  Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc 
or when heavy operations are done on it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-13 (50 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom of screen

[Daniel van Vugt]

This bug has been closed for over three years so if you have any ongoing
issue please open a new bug.

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

Title:
  Ubuntu dock does not allow drag and move icons at bottom of screen

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  the dock placed left or right it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2030963] Re: Window/app switcher highlights hard to see

[Daniel van Vugt]

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

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

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

Title:
  Window/app switcher highlights hard to see

Status in GNOME Shell:
  New
Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  In 22.04's default theme, it's almost impossible for me to make out
  which app or window is the currently selected one in the window
  switcher (alt-tab) or the application switcher (super-tab). The
  "highlighted" item is just a slightly different shade of grey. I mean,
  I can make it out if I squint at it, but ... that just isn't a
  *highlight*. This is a use where Ubuntu Orange shines, too. :-(

  "Ok, boomer, you're blind. I can see that just fine". Fair enough. Are
  you under thirty and (thus still) have 20:20 vision, by any chance?
  The point is, it isn't good UI design either way. What's worse, the
  high contrast accessibility setting doesn't touch any of it, and that
  is definitely a bug.

  ==

  EDIT: Rearranged the submission so that the bit this bug is meant to
  be primarily about is on top. The below bits are preserved so that the
  discussion still makes sense.

  Similarly, the active workspace in the workspace overview (?) does get
  an orange frame, but it's very thin, much too thin to see unless you
  look closely. Again, that's not a highlight. A highlight is supposed
  to pop out.

  In comparison, the highlighting for the current tab in Terminal is ok-
  ish. I'd *prefer* for the entire tab to become orange, or to become a
  lighter colour in addition to the orange bar, but it's usable.

  (I could go on. For example, windows' title bars are now white vs the iconic 
Ubuntu Brown, which makes it hard to tell where the title bar is vs the window 
contents. Many applications also have buttons in the title bar now. It's no 
longer possible to just grab a window and move it on auto-pilot ... If the 
title bar can't be a different colour any more, at least separate it with a 
thick line or something.
  In any case, 22.04 is a massive regression in terms of visual UI design vs 
18.04. Form should follow function, not the other way around.)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
  Uname: Linux 6.2.0-1009-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 10 12:58:31 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-02 (7 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2037121] Re: Freeze when going full screen while watching video

[Daniel van Vugt]

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

This bug is closed as a duplicate of bug 2035016 which is also closed.
So if you have any ongoing issues please open new bugs for them.

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

Title:
  Freeze when going full screen while watching video

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  The screen freezes when I switch a running video into fullscreen mode.
  It happens with Gnome Totem, VLC, Firefox, so the issue is not
  connected to a certain app.

  I can hear the audio playing in the background while the video output
  gets stuck. The keyboard keeps working but switching to another app
  via keyboard doesn't work because the screen keeps stuck with the
  video.

  Way to reproduce:

  1) Boot Ubuntu
  2) Close lid and let the laptop go to sleep mode
  3) Open the lid and login
  4) Start a random video on Youtube/VLC/Totem
  5) Switch to fullscreen
  -> Immediate freeze of the screen

  Workaround after the video froze:
  1) Press ESC key (As if you would usually leave the fullscreen mode, however, 
the screen will stay stuck)
  2) Close the lid
  3) Wait until the laptop goes into sleep mode
  4) Open the lid and login again

  Step 1) is necessary to leave the fullscreen before going to sleep.
  Otherwise after sleep and logging in again the screen gets stuck again
  immediately because the video is continued in fullscreen.

  Syslog tell me this:

  gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Ubuntu 23.10 beta with all updates of 22.09.2023
  Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic

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


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

[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[Daniel van Vugt]

^^^
Bug 1717878

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  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/linux/+bug/2034619/+subscriptions


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