[Desktop-packages] [Bug 2020030] [NEW] System 76 Lemur Pro - Light Display Manager failed on boot

2023-05-17 Thread Andrew Barge
Public bug reported:

I have executed a ubuntu-bug lightdm as requested here:
https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709

In my case I did nano /etc/systemd/system/display-manager.service and
double checked Restart=Always was on (it was) and added RestartSec=0.5.
So far it’s booting every single time without issue.

It might be better to  include that in the config by default so less
people run into this issue.  Most of the people who were addressing this
ended up reinstalling Ubuntu Budgie and this fix can avoid that issue
entirely.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service]
Uname: Linux 6.2.6-76060206-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Wed May 17 21:50:52 2023
InstallationDate: Installed on 2022-09-21 (239 days ago)
InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
LightdmConfig:
 [Seat:*]
 greeter-session=slick-greeter
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  System 76 Lemur Pro - Light Display Manager failed on boot

Status in lightdm package in Ubuntu:
  New

Bug description:
  I have executed a ubuntu-bug lightdm as requested here:
  
https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709

  In my case I did nano /etc/systemd/system/display-manager.service and
  double checked Restart=Always was on (it was) and added
  RestartSec=0.5. So far it’s booting every single time without issue.

  It might be better to  include that in the config by default so less
  people run into this issue.  Most of the people who were addressing
  this ended up reinstalling Ubuntu Budgie and this fix can avoid that
  issue entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: lightdm 1.30.0-0ubuntu5 [modified: 
lib/systemd/system/lightdm.service]
  Uname: Linux 6.2.6-76060206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Wed May 17 21:50:52 2023
  InstallationDate: Installed on 2022-09-21 (239 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809.1)
  LightdmConfig:
   [Seat:*]
   greeter-session=slick-greeter
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1793124]

2023-05-17 Thread Netalac359
Please resolve this issue! It would be much appreciated.
Thanks

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

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


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


[Desktop-packages] [Bug 2018458] Re: Screen tearing when playing video

2023-05-17 Thread Daniel van Vugt
Please also check to see if the problem only happens:

  * In full screen mode (bug 1754284)
  * With multiple monitors (bug 1853094)
  * With custom scaling (bug 1846398)

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

Title:
  Screen tearing when playing video

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when
  there is a fast movement on video the picture blurs and shifts, this
  bug is only on X11, on waywand everything is ok

  this is my system:
  6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroRelease: Ubuntu 23.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0]
  MachineType: LENOVO 21E6006WBM
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags: wayland-session lunar ubuntu
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2023
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET47W(1.18)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E6006WBM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4:
  dmi.product.family: ThinkPad E15 Gen 4
  dmi.product.name: 21E6006WBM
  dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4
  dmi.product.version: ThinkPad E15 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2018458] Re: Video glitch

2023-05-17 Thread Daniel van Vugt
Thanks, that's called tearing.

Please log into Xorg again, reproduce the bug and then run:

  xrandr --verbose > xrandr-xorg.txt

and attach the resulting text file here.


** Tags added: tearing

** Summary changed:

- Video glitch
+ Screen tearing when playing video

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

Title:
  Screen tearing when playing video

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when
  there is a fast movement on video the picture blurs and shifts, this
  bug is only on X11, on waywand everything is ok

  this is my system:
  6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroRelease: Ubuntu 23.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0]
  MachineType: LENOVO 21E6006WBM
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags: wayland-session lunar ubuntu
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2023
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET47W(1.18)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E6006WBM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4:
  dmi.product.family: ThinkPad E15 Gen 4
  dmi.product.name: 21E6006WBM
  dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4
  dmi.product.version: ThinkPad E15 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 480516] Re: software sources not appear

2023-05-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  software sources not appear

Status in Launchpad itself:
  Invalid
Status in gconf package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  for futher information see
  http://img20.imageshack.us/img20/7530/screenshot1zx.png

  the problem is "software sources" not appear even i run "gksu
  /usr/bin/software-properties-gtk"..

  root@se7en-laptop:/home/se7en# gksu /usr/bin/software-properties-gtk
  GConf Error: Failed to contact configuration server; some possible causes are 
that you need to enable TCP/IP networking for ORBit, or you have stale NFS 
locks due to a system crash. See http://projects.gnome.org/gconf/ for 
information. (Details -  1: Failed to get connection to session: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.)
  GConf Error: Failed to contact configuration server; some possible causes are 
that you need to enable TCP/IP networking for ORBit, or you have stale NFS 
locks due to a system crash. See http://projects.gnome.org/gconf/ for 
information. (Details -  1: Failed to get connection to session: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.)
  GConf Error: Failed to contact configuration server; some possible causes are 
that you need to enable TCP/IP networking for ORBit, or you have stale NFS 
locks due to a system crash. See http://projects.gnome.org/gconf/ for 
information. (Details -  1: Failed to get connection to session: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.)
  GConf Error: Failed to contact configuration server; some possible causes are 
that you need to enable TCP/IP networking for ORBit, or you have stale NFS 
locks due to a system crash. See http://projects.gnome.org/gconf/ for 
information. (Details -  1: Failed to get connection to session: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.)

  (gksu:3681): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' 
failed
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 110, in 
  app = SoftwarePropertiesGtk(datadir=data_dir, options=options, file=file)
File 
"/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 122, in __init__
  self.show_keys()
File 
"/usr/lib/python2.6/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 716, in show_keys
  for key in self.apt_key.list():
File "/usr/lib/python2.6/dist-packages/softwareproperties/AptAuth.py", line 
54, in list
  p = subprocess.Popen(self.list_opt,stdout=PIPE).stdout
File "/usr/lib/python2.6/subprocess.py", line 621, in __init__
  errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child
  raise child_exception
  OSError: [Errno 8] Exec format error
  root@se7en-laptop:/home/se7en#

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


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


[Desktop-packages] [Bug 2020009] [NEW] F9 no longer hides side pane

2023-05-17 Thread Coeur Noir
Public bug reported:

Hi,

23.04 Ubuntu freshly installed.

In Nautilus F9 key no longer hides side pane as it used to do.

This keyboard shortcut is mentioned though in [ Ctrl ] + [ ? ]

Expected :

ability to hide side pane

Use-case :

easier on eyes and mouse moves when moving elements between two opened
windows of Nautilus.

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


** Tags: gnome lunar nautilus ubuntu-desktop

** Tags added: gnome lunar nautilus

** Tags added: ubuntu-desktop

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

Title:
  F9 no longer hides side pane

Status in nautilus package in Ubuntu:
  New

Bug description:
  Hi,

  23.04 Ubuntu freshly installed.

  In Nautilus F9 key no longer hides side pane as it used to do.

  This keyboard shortcut is mentioned though in [ Ctrl ] + [ ? ]

  Expected :

  ability to hide side pane

  Use-case :

  easier on eyes and mouse moves when moving elements between two opened
  windows of Nautilus.

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


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


[Desktop-packages] [Bug 2019474] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: le sous-processus nouveau firefox paquet pre-installation script a renvoyé un état de sortie d'erreur

2023-05-17 Thread Seth Arnold
Here's the relevant bit from the dpkg logs:

Préparation du dépaquetage de .../firefox_1%3a1snap1-0ubuntu2_amd64.deb ...
=> Installing the firefox snap
==> Checking connectivity with the snap store
==> Installing the firefox snap
erreur : snap "firefox" has "install-snap" change in progress
dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu2_amd64.deb (--unpack) :
 le sous-processus nouveau firefox paquet pre-installation script a renvoyé un 
état de sortie d'erreur 10

Thanks

** Information type changed from Private Security to Public

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: le sous-
  processus nouveau firefox paquet pre-installation script a renvoyé un
  état de sortie d'erreur 10

Status in firefox package in Ubuntu:
  New

Bug description:
  Plz solve my problem with snap firefox

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat May 13 13:15:04 2023
  Dependencies:
   
  ErrorMessage: le sous-processus nouveau firefox paquet pre-installation 
script a renvoyé un état de sortie d'erreur 10
  InstallationDate: Installed on 2023-05-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  SourcePackage: firefox
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: le 
sous-processus nouveau firefox paquet pre-installation script a renvoyé un état 
de sortie d'erreur 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


Re: [Desktop-packages] [Bug 2020003] [NEW] Thunderbird shows accent marks instead of punctuation

2023-05-17 Thread tomdean
On 5/17/23 15:59, tomdean wrote:
> Public bug reported:
> 
> I upgraded from 20.04 LTS to 22.04.2 LTS. Since then, thunderbird and
> some other applications show accent marks rather than punctuation marks
> in the title bar.
> 
> For example, wavecable.com is displayed as wavecable^com where ^ is an
> accent mark.
> 
> This has happened since the upgrade.
> 
> If I change language to English_en, I get lots of arabic characters.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: thunderbird 1:102.11.0+build1-0ubuntu0.22.04.1
> ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
> Uname: Linux 5.15.0-71-generic x86_64
> AddonCompatCheckDisabled: False
> ApportVersion: 2.20.11-0ubuntu82.4
> Architecture: amd64
> AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC3:  tomdean2304 F pulseaudio
>   /dev/snd/controlC1:  tomdean2304 F pulseaudio
>   /dev/snd/controlC0:  tomdean2304 F pulseaudio
> BuildID: 20230503190012
> CasperMD5CheckResult: unknown
> Channel: Unavailable
> CurrentDesktop: GNOME
> Date: Wed May 17 15:54:00 2023
> ForcedLayersAccel: False
> IfupdownConfig:
>   auto enp68s0f0
>   iface enp68s0f0 inet dhcp
> IncompatibleExtensions:
>   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
>   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
> InstallationDate: Installed on 2021-05-10 (737 days ago)
> InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
> (20210209.1)
> IpRoute:
>   default via 192.168.1.1 dev enp68s0f0
>   default dev enp68s0f1 scope link metric 1003 linkdown
>   169.254.0.0/16 dev enp68s0f1 proto kernel scope link src 169.254.9.3 
> linkdown
>   192.168.1.0/24 dev enp68s0f0 proto kernel scope link src 192.168.1.105
> PrefErrors: Unexpected character ',' before close parenthesis @ 
> /usr/lib/thunderbird/omni.ja:greprefs.js:306
> PrefSources:
>   prefs.js
>   user.js
> Profiles: Profile0 (Default) - LastVersion=102.11.0/20230503190012 (In use)
> RebootRequiredPkgs: Error: path contained symlinks.
> RunningIncompatibleAddons: True
> SourcePackage: thunderbird
> UpgradeStatus: Upgraded to jammy on 2023-05-16 (1 days ago)
> dmi.bios.date: 11/23/2021
> dmi.bios.release: 5.15
> dmi.bios.vendor: American Megatrends International, LLC.
> dmi.bios.version: FC
> dmi.board.asset.tag: Default string
> dmi.board.name: TRX40 AORUS XTREME
> dmi.board.vendor: Gigabyte Technology Co., Ltd.
> dmi.board.version: Default string
> dmi.chassis.asset.tag: Default string
> dmi.chassis.type: 3
> dmi.chassis.vendor: Default string
> dmi.chassis.version: Default string
> dmi.modalias: 
> dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFC:bd11/23/2021:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSXTREME:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSXTREME:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
> dmi.product.family: Default string
> dmi.product.name: TRX40 AORUS XTREME
> dmi.product.sku: Default string
> dmi.product.version: -CF
> dmi.sys.vendor: Gigabyte Technology Co., Ltd.
> 
> ** Affects: thunderbird (Ubuntu)
>   Importance: Undecided
>   Status: New
> 
> 
> ** Tags: amd64 apport-bug jammy
> 

++
Rebooting did not change the problem.
Umounting loop*, purging snapd, and rebooting fixed the problem.

Please close this bug report.

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

Title:
  Thunderbird shows accent marks instead of punctuation

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I upgraded from 20.04 LTS to 22.04.2 LTS. Since then, thunderbird and
  some other applications show accent marks rather than punctuation
  marks in the title bar.

  For example, wavecable.com is displayed as wavecable^com where ^ is an
  accent mark.

  This has happened since the upgrade.

  If I change language to English_en, I get lots of arabic characters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.11.0+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
  Uname: Linux 5.15.0-71-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  tomdean2304 F pulseaudio
   /dev/snd/controlC1:  tomdean2304 F pulseaudio
   /dev/snd/controlC0:  tomdean2304 F pulseaudio
  BuildID: 20230503190012
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed May 17 15:54:00 2023
  ForcedLayersAccel: False
  IfupdownConfig:
   auto enp68s0f0
   iface enp68s0f0 inet dhcp
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  

[Desktop-packages] [Bug 2020003] [NEW] Thunderbird shows accent marks instead of punctuation

2023-05-17 Thread tomdean
Public bug reported:

I upgraded from 20.04 LTS to 22.04.2 LTS. Since then, thunderbird and
some other applications show accent marks rather than punctuation marks
in the title bar.

For example, wavecable.com is displayed as wavecable^com where ^ is an
accent mark.

This has happened since the upgrade.

If I change language to English_en, I get lots of arabic characters.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:102.11.0+build1-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
Uname: Linux 5.15.0-71-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  tomdean2304 F pulseaudio
 /dev/snd/controlC1:  tomdean2304 F pulseaudio
 /dev/snd/controlC0:  tomdean2304 F pulseaudio
BuildID: 20230503190012
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 17 15:54:00 2023
ForcedLayersAccel: False
IfupdownConfig:
 auto enp68s0f0
 iface enp68s0f0 inet dhcp
IncompatibleExtensions:
 English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
 Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2021-05-10 (737 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
IpRoute:
 default via 192.168.1.1 dev enp68s0f0 
 default dev enp68s0f1 scope link metric 1003 linkdown 
 169.254.0.0/16 dev enp68s0f1 proto kernel scope link src 169.254.9.3 linkdown 
 192.168.1.0/24 dev enp68s0f0 proto kernel scope link src 192.168.1.105
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources:
 prefs.js
 user.js
Profiles: Profile0 (Default) - LastVersion=102.11.0/20230503190012 (In use)
RebootRequiredPkgs: Error: path contained symlinks.
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to jammy on 2023-05-16 (1 days ago)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FC
dmi.board.asset.tag: Default string
dmi.board.name: TRX40 AORUS XTREME
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFC:bd11/23/2021:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSXTREME:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSXTREME:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: TRX40 AORUS XTREME
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug jammy

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

Title:
  Thunderbird shows accent marks instead of punctuation

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I upgraded from 20.04 LTS to 22.04.2 LTS. Since then, thunderbird and
  some other applications show accent marks rather than punctuation
  marks in the title bar.

  For example, wavecable.com is displayed as wavecable^com where ^ is an
  accent mark.

  This has happened since the upgrade.

  If I change language to English_en, I get lots of arabic characters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.11.0+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
  Uname: Linux 5.15.0-71-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  tomdean2304 F pulseaudio
   /dev/snd/controlC1:  tomdean2304 F pulseaudio
   /dev/snd/controlC0:  tomdean2304 F pulseaudio
  BuildID: 20230503190012
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed May 17 15:54:00 2023
  ForcedLayersAccel: False
  IfupdownConfig:
   auto enp68s0f0
   iface enp68s0f0 inet dhcp
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2021-05-10 (737 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.1.1 dev enp68s0f0 
   default dev enp68s0f1 scope link metric 1003 linkdown 
   169.254.0.0/16 dev enp68s0f1 proto kernel scope link src 169.254.9.3 
linkdown 
   192.168.1.0/24 dev enp68s0f0 proto kernel scope link src 

[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Seth Arnold
jammy, lunary, and mantic:

for distro in jammy lunar mantic  ; do for component in main universe
multiverse restricted ; do for-archive
/srv/mirror/ubuntu/dists/$distro/$component/source/Sources.gz
/srv/mirror/ubuntu/ ~/bin/for-archive-tools/unpack-search '/system-
connections' ; done ; done | tee ~/system-connections-$(date
+%d-%H:%M:%S)


** Attachment added: "system-connections-17-10:41:24"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2019940/+attachment/5673652/+files/system-connections-17-10%3A41%3A24

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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


[Desktop-packages] [Bug 2017907] Re: cups-browsed high CPU usage

2023-05-17 Thread Pirouette Cacahuète
same for me, I have not verified what was causing it, this is the first
time it happens for me though I upgraded to 23.04 a few weeks ago
already. Connected over WiFi, as someone mentions.

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

Title:
  cups-browsed high CPU usage

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Using Lunar wifi connected to an enterprise network.
  cups-browsed uses a lot of CPU %, I need to kill it to save my battery.
  2.0rc1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+subscriptions


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


[Desktop-packages] [Bug 2019983] Re: No gear icon to select session type

2023-05-17 Thread Jeremy Bícha
The Firefox issue has a fix in lunar-proposed. See
https://launchpad.net/ubuntu/+source/mutter/44.0-2ubuntu4.23.04.1

Based on your latest comment, I'm closing this bug. Thank you for taking
the time to help make Ubuntu better.

** Changed in: gdm3 (Ubuntu)
   Status: New => Invalid

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

Title:
  No gear icon to select session type

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  be it under Wayland or X11 ;

  login-screen does not show the gear icon at bottom right of the screen
  for choosing session type ;

  hence I had to « force » it through /etc/gdm3/custom.conf

  It's a freshly installed 23.04 from
  https://cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-desktop-
  legacy-amd64.iso

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gdm3 44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 17 17:29:39 2023
  InstallationDate: Installed on 2023-05-16 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2023-05-17T16:46:12.733575

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


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


[Desktop-packages] [Bug 2019995] [NEW] mutter autopkgtest failing on amd64 since May

2023-05-17 Thread Jeremy Bícha
Public bug reported:

The mutter autopkgtest last passed on amd64 on Lunar April 15.
By May 1, the autopkgtest was failing on Mantic & the first time it was retried 
on Lunar after that (May 15), it was failing there.

This points to a change in one of the dependencies. However, by April
15, Lunar was in Final Freeze so not much changed after that date.

The kernel was updated after that date.

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: amd64 lunar mantic update-excuse

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

Title:
  mutter autopkgtest failing on amd64 since May

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The mutter autopkgtest last passed on amd64 on Lunar April 15.
  By May 1, the autopkgtest was failing on Mantic & the first time it was 
retried on Lunar after that (May 15), it was failing there.

  This points to a change in one of the dependencies. However, by April
  15, Lunar was in Final Freeze so not much changed after that date.

  The kernel was updated after that date.

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


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


[Desktop-packages] [Bug 2017229] Re: Update evolution-data-server to 3.48.1

2023-05-17 Thread Jeremy Bícha
I have had evolution-data-server 3.48.1-0ubuntu1 installed on my Ubuntu
23.04 for a couple weeks. Evolution 3.48.1 and GNOME Calendar 44.0 work
normally.

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

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

Title:
  Update evolution-data-server to 3.48.1

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the stable 3.48 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.48.1/NEWS

  It is required to update the evolution app to 3.48.1 (LP: #2017231)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

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

  evolution-data-server is included in all the Ubuntu Desktop flavors
  except for Kubuntu, Lubuntu, and Xubuntu

  Other Info
  --
  There will be new evolution-data-server bugfix releases monthly until 
September.

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


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


[Desktop-packages] [Bug 2019994] [NEW] Update gnome-calendar to 44.1

2023-05-17 Thread Jeremy Bícha
Public bug reported:

Impact
--
There is a new bugfix release in the stable 44 series.
https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/44.1/NEWS

Test Case
-
Complete the test case from

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

What Could Go Wrong
---
GNOME Calendar is included by default in Ubuntu Desktop, Edubuntu, and Ubuntu 
Cinnamon.

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

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

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

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

** Affects: gnome-calendar (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: gnome-calendar (Ubuntu Lunar)
 Importance: Medium
 Status: In Progress


** Tags: lunar upgrade-software-version

** Also affects: gnome-calendar (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-calendar (Ubuntu Lunar)
   Status: New => In Progress

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

Title:
  Update gnome-calendar to 44.1

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Lunar:
  In Progress

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

  Test Case
  -
  Complete the test case from

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

  What Could Go Wrong
  ---
  GNOME Calendar is included by default in Ubuntu Desktop, Edubuntu, and Ubuntu 
Cinnamon.

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

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

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

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

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


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


[Desktop-packages] [Bug 2019989] [NEW] Update libadwaita to 1.3.2

2023-05-17 Thread Jeremy Bícha
Public bug reported:

Impact
--
1. There is a new release in the stable 1.3 series.

https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.2/NEWS

2. This update also updates the Python 3 autopkgtest for compatibility
with GTK 4.10.2

3.

Test Case 0
---
libadwaita includes a build test suite that will fail the build if the tests 
fail.

libadwaita also includes 2 superficial autopkgtests, one for C, one for
Python 3.

Test Case 1
---
After installing the update, open gnome-control-center and nautilus.

Ensure that the apps run and that the on/off switches, checkboxes, and
other visual elements still display correctly.

In gnome-control-center click Appearance in the sidebar.
Verify that switching the style between Light and Dark works correctly.
Also choose a different accent color and verify that elements like folder icons 
in Nautilus and on/off switches have correctly adopted the accent color you 
chose.

Test case 2
---
Run adwaita-1-demo run the style classes demo check that all elements are 
properly visible and check that link color has enough contrast with background.

What Could Go Wrong
---
libadwaita is an addon library to GTK4 to allow apps to easily use more of the 
GNOME style and allow for widgets to be added and improved faster than in the 
normal GTK development cycle.

libadwaita is included in all Ubuntu desktop flavors except for Kubuntu
& Lubuntu.

Many of the default Ubuntu desktop apps in 23.04 use libadwaita.

As a component of GNOME core, there is a micro-release exception for libadwaita.
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: libadwaita-1 (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: libadwaita-1 (Ubuntu Lunar)
 Importance: Medium
 Status: Triaged


** Tags: lunar upgrade-software-version

** Also affects: libadwaita-1 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: libadwaita-1 (Ubuntu Lunar)
   Importance: Undecided => Medium

** Changed in: libadwaita-1 (Ubuntu Lunar)
   Status: New => Triaged

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

Title:
  Update libadwaita to 1.3.2

Status in libadwaita-1 package in Ubuntu:
  Fix Released
Status in libadwaita-1 source package in Lunar:
  Triaged

Bug description:
  Impact
  --
  1. There is a new release in the stable 1.3 series.

  https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.3.2/NEWS

  2. This update also updates the Python 3 autopkgtest for compatibility
  with GTK 4.10.2

  3.

  Test Case 0
  ---
  libadwaita includes a build test suite that will fail the build if the tests 
fail.

  libadwaita also includes 2 superficial autopkgtests, one for C, one
  for Python 3.

  Test Case 1
  ---
  After installing the update, open gnome-control-center and nautilus.

  Ensure that the apps run and that the on/off switches, checkboxes, and
  other visual elements still display correctly.

  In gnome-control-center click Appearance in the sidebar.
  Verify that switching the style between Light and Dark works correctly.
  Also choose a different accent color and verify that elements like folder 
icons in Nautilus and on/off switches have correctly adopted the accent color 
you chose.

  Test case 2
  ---
  Run adwaita-1-demo run the style classes demo check that all elements are 
properly visible and check that link color has enough contrast with background.

  What Could Go Wrong
  ---
  libadwaita is an addon library to GTK4 to allow apps to easily use more of 
the GNOME style and allow for widgets to be added and improved faster than in 
the normal GTK development cycle.

  libadwaita is included in all Ubuntu desktop flavors except for
  Kubuntu & Lubuntu.

  Many of the default Ubuntu desktop apps in 23.04 use libadwaita.

  As a component of GNOME core, there is a micro-release exception for 
libadwaita.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2019989/+subscriptions


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


[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2023-05-17 Thread TomaszChmielewski
Same issue on LG Gram 17Z90R - no audio.

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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


[Desktop-packages] [Bug 1966413] Re: --no-oem option is broken

2023-05-17 Thread Olivier Gayot
We might need to use this option in subiquity and it indeed seems
broken.

There are actually two possible usages:

$ ubuntu-drivers --no-oem install => which results in an exception
$ ubuntu-drivers install --no-oem => which does not result in an exception 
but ignores the option

I've opened a PR to fix it: https://github.com/tseliot/ubuntu-drivers-
common/pull/82

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

Title:
  --no-oem option is broken

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

Bug description:
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 376, in greet
  config.no_oem = install_oem_meta
  NameError: name 'install_oem_meta' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 25 11:44:15 2022
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-kitty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1966413] Re: --no-oem option is broken

2023-05-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  --no-oem option is broken

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

Bug description:
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 376, in greet
  config.no_oem = install_oem_meta
  NameError: name 'install_oem_meta' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 25 11:44:15 2022
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-kitty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2019983] [NEW] No gear icon to select session type

2023-05-17 Thread Coeur Noir
Public bug reported:

Hi,

be it under Wayland or X11 ;

login-screen does not show the gear icon at bottom right of the screen
for choosing session type ;

hence I had to « force » it through /etc/gdm3/custom.conf

It's a freshly installed 23.04 from
https://cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-desktop-
legacy-amd64.iso

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 44.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 17 17:29:39 2023
InstallationDate: Installed on 2023-05-16 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-05-17T16:46:12.733575

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


** Tags: amd64 apport-bug lunar

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

Title:
  No gear icon to select session type

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Hi,

  be it under Wayland or X11 ;

  login-screen does not show the gear icon at bottom right of the screen
  for choosing session type ;

  hence I had to « force » it through /etc/gdm3/custom.conf

  It's a freshly installed 23.04 from
  https://cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-desktop-
  legacy-amd64.iso

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gdm3 44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 17 17:29:39 2023
  InstallationDate: Installed on 2023-05-16 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2023-05-17T16:46:12.733575

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


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


[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket

2023-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package speech-dispatcher - 0.11.4-2ubuntu1

---
speech-dispatcher (0.11.4-2ubuntu1) mantic; urgency=medium

  [ Nathan Pratta Teodosio ]
  * patches/systemd-socket-activation: Added.
- Enables activating Speech Dispatcher via a Systemd socket, it's needed
for confined clients to be able to activate the service (LP: #1991022).
  * control: remove deprecated lsb-base package.

  [ Sebastien Bacher]
  * debian/control:
- Build-Depends on libsystemd-dev
  * debian/speech-dispatcher.install:
- install the new systemd units

 -- Sebastien Bacher   Mon, 15 May 2023 13:43:36
+0200

** Changed in: speech-dispatcher (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Service activation via Systemd socket

Status in speech-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Mantic and verified that
  running spd-say from inside a snap causes the host's dispatcher to
  spawn and emit sound — see 'Reproduction case' for more details.

  The installed socket needs to be started manually to function
  correctly, or else the system needs to be rebooted.

  [Reproduction case]

  Install the proposed speech-dispatcher from the PPA[3] and the snap[4]
  with spd-say. Then,

systemctl start --user speech-dispatcher.socket
snap run --shell geheim
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi

  [1] https://github.com/brailcom/speechd/issues/335
  [2] https://github.com/brailcom/speechd/pull/763
  [3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882
  [4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions


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


[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch

2023-05-17 Thread Coeur Noir
And still broken in 23.04

** Attachment added: "lunar_calendar.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970800/+attachment/5673579/+files/lunar_calendar.png

** Tags added: lunar

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

Title:
  Clicking a calendar date in the bottom row of the panel calendar
  causes a graphical glitch

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

Bug description:
  If you click a calendar date in the bottom row of the top panel
  calendar, the backdrop shrinks and the dates overflow out of the
  backdrop boundaries.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 28 16:25:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD 
Graphics] [1462:129c]
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 
1650 Mobile / Max-Q] [1462:129c]
  InstallationDate: Installed on 2022-04-22 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2019976] [NEW] gdm3(8) manual page is actually gdm-screenshot

2023-05-17 Thread Valery Ushakov
Public bug reported:

There is no manual page for gdm3.

The one that is shipped:

$ dpkg-query -S /usr/share/man/man8/gdm3.8.gz 
gdm3: /usr/share/man/man8/gdm3.8.gz

is actually

$ man gdm3 | sed 1q
GDM-SCREENSHOT.1(8)Debian GNU/LinuxGDM-SCREENSHOT.1(8)

(also note bogus .1 at the end of the man page title name).

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

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

Title:
  gdm3(8) manual page is actually gdm-screenshot

Status in gdm3 package in Ubuntu:
  New

Bug description:
  There is no manual page for gdm3.

  The one that is shipped:

  $ dpkg-query -S /usr/share/man/man8/gdm3.8.gz 
  gdm3: /usr/share/man/man8/gdm3.8.gz

  is actually

  $ man gdm3 | sed 1q
  GDM-SCREENSHOT.1(8)Debian GNU/LinuxGDM-SCREENSHOT.1(8)

  (also note bogus .1 at the end of the man page title name).

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


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


[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

2023-05-17 Thread Rex Tsai
** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  New
Status in OEM Priority Project:
  Triaged
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

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


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


[Desktop-packages] [Bug 1973264] Re: when switching to another workspace, focus is lost

2023-05-17 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1969598 ***
https://bugs.launchpad.net/bugs/1969598

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

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

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

Title:
  when switching to another workspace, focus is lost

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Good morning,

  Since upgrading to 22.04 there is an annoying bug when switching to
  another workspace. After the switch to one of the other workspaces,
  the desktop has the focus, instead of an application window. Until
  now, the window that most recently had focus on that workspace, would
  get the focus again, which I would consider normal behaviour.

  This bug leads to confusing (sometimes funny) situations, like

  - me switching to another WS
  - press ctrl A to select all text in the window I assume is active
  - nothing seems to happen, but (not visible for me) everything on the desktop 
is selected
  - better not press Del now :)  

  Best,

  Joolz.

  P.S. I hope I filed this in the right section, not sure which
  framework causes this

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


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


[Desktop-packages] [Bug 2019958] [NEW] 23.04 : all windows and shell animations are suddenly gone away

2023-05-17 Thread Coeur Noir
Public bug reported:

Hi,

once of a sudden, all shell and windows animations are gone away.
maximizing / minimizing windows / app's or activities views, all animations.

Login logout session → no change.
Disabling / removing gnome-shell extensions change nothing either.
Same on next reboot.

It was ok during live-session ( trying without installing ).

It was ok a long moment after installation.
I can't « see » which event stopped animations.

org.gnome.desktop.interface enable-animations true

django@ASGARD:~$ gnome-shell --force-animations
libmutter-Message: 14:51:45.811: Running GNOME Shell (using mutter 44.0) as a 
X11 window and compositing manager
org.gnome.Shell already exists on bus and --replace not specified
django@ASGARD:~$ 


↑ is the X11 window expected here ? ↑

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 17 14:35:13 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-16 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.0-2ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

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

Title:
  23.04 : all windows and shell animations are suddenly gone away

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  once of a sudden, all shell and windows animations are gone away.
  maximizing / minimizing windows / app's or activities views, all animations.

  Login logout session → no change.
  Disabling / removing gnome-shell extensions change nothing either.
  Same on next reboot.

  It was ok during live-session ( trying without installing ).

  It was ok a long moment after installation.
  I can't « see » which event stopped animations.

  org.gnome.desktop.interface enable-animations true

  django@ASGARD:~$ gnome-shell --force-animations
  libmutter-Message: 14:51:45.811: Running GNOME Shell (using mutter 44.0) as a 
X11 window and compositing manager
  org.gnome.Shell already exists on bus and --replace not specified
  django@ASGARD:~$ 

  
  ↑ is the X11 window expected here ? ↑

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 17 14:35:13 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-05-16 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  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/2019958/+subscriptions


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


[Desktop-packages] [Bug 2018155] Re: Can't login to Xorg sessions if desktop zoom was already enabled

2023-05-17 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

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

Title:
  Can't login to Xorg sessions if desktop zoom was already enabled

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

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 'org.gnome.ScreenSaver'
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session[7361]: 
gnome-session-binary[7361]: WARNING: Could not retrieve current screensaver 
active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient 
disconnected from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session-binary[7361]: 
WARNING: Could not retrieve current screensaver active state: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.impl.portal.desktop.gtk'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.portal.Desktop'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal.service - Portal service.
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: New theme: 
gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: All 
available theme snaps installed
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7984]: libEGL warning: 
DRI2: failed to authenticate
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: gnome-shell[7863]: 
segfault at 18 ip 7f7af86b2004 sp 7ffeb1dc3a18 error 4 in 
libmutter-12.so.0.0.0[7f7af864a000+13d000] likely on CPU 15 (core 15, socket 0)
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: Code: 00 00 00 00 66 90 f3 
0f 1e fa 48 63 05 79 67 16 00 48 8b 04 07 c3 f3 0f 1e fa 48 8b 87 40 01 00 00 
c3 0f 1f 40 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 
8b 47 28 c3 0f
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Failed with result 'core-dump'.
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: Failed to start 
org.gnome.Shell@x11.service - GNOME Shell on X11.
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 

[Desktop-packages] [Bug 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames

2023-05-17 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => 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/2018731

Title:
  Graphics memory (VRAM) leak in mutter-x11-frames

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

Bug description:
  I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two 
screens.
  After launching nvidia-smi, I can clearly see that there's a memory leak in 
mutter-x11-frames, which uses around 10-12 GB of VRAM.
  nvidia-drivers-525
  Ubuntu 23.04
  X11

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  8 14:28:13 2023
  DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2023-02-09 (87 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 82N6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago)
  dmi.bios.date: 03/07/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN60WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

2023-05-17 Thread Lukas Märdian
** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  The Netplan Everywhere NetworkManager fails to supply Netplan with
  networking information until a connection is deleted and re-created

Status in netplan:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a 
WiFi adapter. (I used Lubuntu Lunar.)
  2. Connect to WiFi and install all updates.
  3. Enable the Netplan Everywhere PPA and install the updated NetworkManager 
from it (further details at 
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
  4. When the installation finishes, run "sudo netplan get".

  Expected result: Networking information related to the WiFi connection
  should appear in the "sudo netplan get" output.

  Actual result: "sudo netplan get" returns the following:

  ** (process:4088): WARNING **: 12:41:41.394; Permissions for 
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration 
should NOT be accessible by others.
  network:
    version: 2
    renderer: NetworkManager

  End of output. Additionally, the /etc/netplan folder does not contain
  files that I would expect to be there that would contain the
  networking info.

  Additional information:

  If I disconnect from WiFi, then delete my WiFi connection entirely in
  nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
  get" returns the expected networking information. /etc/netplan is also
  properly populated after doing this.

  This bug seems like it will probably cause unintended behavior after
  an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
  (which is supposed to be using the Netplan Everywhere NetworkManager).
  People probably won't know to entirely delete the WiFi and other
  connections and then reconnect them in order for the netplan output to
  be usable.

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


-- 
Mailing list: https://launchpad.net/~desktop-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

2023-05-17 Thread Treviño
So, that "fix" won't probably be accepted.

We've worked on a solution that works for some cases, but still missing
few edge ones.

-- 
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 2018672] Re: Gnome 44: GDM background configurable with gsettings

2023-05-17 Thread Treviño
** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks)

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

Title:
  Gnome 44: GDM background configurable with gsettings

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  The prior implementation of exposing the login screen background setting via 
`gsettings` is not working as expected in Gnome 44 and Ubuntu 23.04. 
Specifically, the background image is infact set, however, the default Gnome 
theme appears as an overlay on top of the com.ubuntu.login-screen schema.

  This appears as the default grey background with a remarkably high
  alpha value of 0.975 from my inspection. If you set a very high
  contrast background image, you can just make out the outline in
  beneath the greeter.

  My expectation would be that we can set the greeter parameters using
  the provided gsettings keys, and set the background-color to
  transparent to only display the configured background-picture-uri key.

  gdm@zen:~$ gsettings list-keys com.ubuntu.login-screen 
  background-color
  background-picture-uri
  background-repeat
  background-size

  [Test Case]
  1. Boot a desktop session
  2. Verify that the default aubergine background is displayed in the greeter.
  3. Login as the administrator of the machine
  4. Install systemd-container
  5. Switch to the GDM user:
$ sudo machinectl shell gdm@ /bin/bash
  6. Apply a different background with the command:
$ gsettings set com.ubuntu.login-screen background-picture-uri 
'file:///usr/share/backgrounds/Lunar-lobster-side_by_Gixo-light.png'
  7. Logout
  8. Verify that the image 'Lunar-lobster-side_by_Gixo-light.png' is displayed 
as the background of the greeter.
  9. Observe the remaining grey overlay with high alpha value. After login, the 
background image is briefly displayed without the overlay before initiating the 
user gnome shell session.

  [Further Investigation]
  PRATAP-KUMAR has done some excellent work overcoming this with their GitHub 
project, and it appears that modifying the Gnome theme with this script 
correctly sets the transparency. However, perhaps there are two layers to the 
greeter, and even though the background image is set, the additional layer is 
not exposed for configuration via gsettings.

  https://github.com/PRATAP-KUMAR/ubuntu-gdm-set-
  background/blob/main/ubuntu-gdm-set-
  background-23.04-transparent#L168-L171

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


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


[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
We should run the same query on the Ubuntu archive, too. The security
team (sespiros / sarnold) might be able to help with this in the future.

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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


[Desktop-packages] [Bug 2018458] Re: Video glitch

2023-05-17 Thread Stoyan Dimitrov
it doesn't matter if it's 1080p, 720p, avi, mkv or mp4

** Attachment added: "PXL_20230517_102804992.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2018458/+attachment/5673547/+files/PXL_20230517_102804992.mp4

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

Title:
  Video glitch

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when
  there is a fast movement on video the picture blurs and shifts, this
  bug is only on X11, on waywand everything is ok

  this is my system:
  6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroRelease: Ubuntu 23.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0]
  MachineType: LENOVO 21E6006WBM
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags: wayland-session lunar ubuntu
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2023
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET47W(1.18)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E6006WBM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4:
  dmi.product.family: ThinkPad E15 Gen 4
  dmi.product.name: 21E6006WBM
  dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4
  dmi.product.version: ThinkPad E15 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2018458] Re: Video glitch

2023-05-17 Thread Stoyan Dimitrov
** Attachment added: "PXL_20230517_102927982.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2018458/+attachment/5673546/+files/PXL_20230517_102927982.mp4

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

Title:
  Video glitch

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when
  there is a fast movement on video the picture blurs and shifts, this
  bug is only on X11, on waywand everything is ok

  this is my system:
  6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroRelease: Ubuntu 23.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0]
  MachineType: LENOVO 21E6006WBM
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags: wayland-session lunar ubuntu
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2023
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET47W(1.18)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E6006WBM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4:
  dmi.product.family: ThinkPad E15 Gen 4
  dmi.product.name: 21E6006WBM
  dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4
  dmi.product.version: ThinkPad E15 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2019951] [NEW] [MIR] libmysofa

2023-05-17 Thread Sebastien Bacher
Public bug reported:

[Availability]
The package libmysofa is already in Ubuntu universe.
The package libmysofa build for the architectures it is designed to work on.
It currently builds and works for architetcures: amd64 arm64 armhf i386 ppc64el 
riscv64 s390x
Link to package https://launchpad.net/ubuntu/+source/libmysofa

[Rationale]
- The package libmysofa is required in Ubuntu main as a (optional) depends of 
pipewire
- the library parses spatial audio files which are used by 3D audio systems
- the libmysofa1 binary needs to be promoted

- There is no other/better way to solve this that is already in main or
  should go universe->main instead of this.

- The package libmysofa is required in Ubuntu main no later than August 17th
  due to mantic feature freeze

[Security]
- Had 15 security issues in the past, sorted out by their status on 
https://ubuntu.com/security/cves?package=libmysofa
Released
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16095
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16094
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16093
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16092
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16091
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10672
Needed
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3756
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6860
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20063
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20016
Needs triage
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36152
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36151
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36150
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36149
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36148

those are also listed in https://security-
tracker.debian.org/tracker/source-package/libmysofa

- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024)
- Packages does not contain extensions to security-sensitive software

[Quality assurance - function/usage]
- The package works well right after install

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and only has minor 
open bugs
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libmysofa/+bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libmysofa
  - Upstream https://github.com/hoene/libmysofa/issues
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
TOFIX
- The package does not run a test at build time, Debian disabled them because 
they were hanging?

- The package runs an autopkgtest, and is currently passing on
  amd64 arm64 armhf ppc64el
https://autopkgtest.ubuntu.com/packages/libm/libmysofa

- The tests fail on i386 due to installability issues of depends which isn't an 
issue
- The s390x failure might be an endian problem and worth investigating though 
we don't support desktop on that architecture so it should probably not be a 
blocker
the issue had been reported upstream (but closed since) on 
https://github.com/hoene/libmysofa/issues/129

[Quality assurance - packaging]
- debian/watch is present and works

- debian/control defines a correct Maintainer

- This package has no lintian warnings

- Please link to a recent build log of the package
https://launchpadlibrarian.net/632293649/buildlog_ubuntu-lunar-amd64.libmysofa_1.3.1~dfsg0-1_BUILDING.txt.gz
- Please attach the full output you have got from `lintian --pedantic`

# lintian --pedantic libmysofa_1.3.1~dfsg0-1_amd64.changes
#

- Lintian overrides are not present

- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies

- The package will be installed by default, but does not ask debconf
questions

- Packaging and build is easy, link to debian/rules
https://salsa.debian.org/multimedia-
team/libmysofa/-/blob/master/debian/rules

[UI standards]
- Application is not end-user facing (does not need translation)

[Dependencies]
- No further depends or recommends dependencies that are not yet in main

[Standards compliance]
- This package correctly follows FHS and Debian Policy

[Maintenance/Owner]
- Owning Team will be desktop-packages
- Team is already subscribed to the package

- This does not use static builds
- This does not use vendored code
- This package is not rust based
- The package has been built in the archive more recently than the last
- The package successfully built during the most recent test rebuild

[Background information]
The Package description explains the 

[Desktop-packages] [Bug 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames

2023-05-17 Thread Daniel van Vugt
Upstream thinks this should be fixed in mutter 44.1, but we're yet to
confirm.

** No longer affects: xorg (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2816
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2816

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

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

** Tags added: nvidia

** Tags added: gnome-shell-leak

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

Title:
  Graphics memory (VRAM) leak in mutter-x11-frames

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

Bug description:
  I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two 
screens.
  After launching nvidia-smi, I can clearly see that there's a memory leak in 
mutter-x11-frames, which uses around 10-12 GB of VRAM.
  nvidia-drivers-525
  Ubuntu 23.04
  X11

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  8 14:28:13 2023
  DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2023-02-09 (87 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 82N6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago)
  dmi.bios.date: 03/07/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN60WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2018706] Re: Second Monitor not detected

2023-05-17 Thread Daniel van Vugt
> I just use nvidia Graphics.

It appears the opposite is true. Only the built-in Intel GPU is active
so any secondary monitor connected to the Nvidia GPU won't work...

Please open the 'Additional Drivers' app and use it to reinstall the
Nvidia driver. Try choosing one that's not the "Open" Nvidia driver.


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

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

** Summary changed:

- Second Monitor not detected
+ Nvidia Xorg driver not installed

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

Title:
  Nvidia Xorg driver not installed

Status in Ubuntu:
  Incomplete

Bug description:
  I just use nvidia Graphics. Before i changed it from xorg i can use my
  second monitor but after i change it, update it.I can't use my second
  monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  530.41.03  Release 
Build  (dvs-builder@U16-T02-35-3)  Thu Mar 16 19:33:35 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1)
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  8 06:58:52 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] 
[1d05:1099]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited TU117M [GeForce GTX 1650 Ti Mobile] 
[1d05:1099]
  InstallationDate: Installed on 2022-12-05 (153 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: MONSTER ABRA A5 V15.10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=49c05d00-8d9a-4953-9075-be6351ac7576 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.07
  dmi.board.asset.tag: Standard
  dmi.board.name: ABRA A5 V15.10
  dmi.board.vendor: MONSTER
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: MONSTER
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.07:bd09/08/2020:br5.17:efr1.19:svnMONSTER:pnABRAA5V15.10:pvrStandard:rvnMONSTER:rnABRAA5V15.10:rvrStandard:cvnMONSTER:ct10:cvrStandard:sku0001:
  dmi.product.family: CML
  dmi.product.name: ABRA A5 V15.10
  dmi.product.sku: 0001
  dmi.product.version: Standard
  dmi.sys.vendor: MONSTER
  nvidia-settings: ERROR: A query to find an object was unsuccessful
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings

2023-05-17 Thread Daniel van Vugt
Regressed in 44? See bug 2018672

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

Title:
  [FFe] GDM background configurable with gsettings

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

Bug description:
  [Description]
  Customization of the greeter is a requirement from Corporate customers.

  Currently the background (plain color or image) of the greeter is hard
  coded in the style embedded in the theme. Customizing this background
  requires to extract the style sheet from gnome-shell gresource file,
  modify it manually, recompile and deploy the new gresource, and add an
  alternative to it.

  This feature adds 4 gsettings keys to make the background of the
  greeter configurable via gsettings. The default value defined the in
  the theme is used for keys that are not set.

  [Rationale]
  Corporate customers use LTS releases and ultimately this will be released for 
20.04.
  This changeset needs to land in hirsute before it can be SRUd into prior 
Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute 
first.

  [Risks]
  The changeset is minimal, isolated and can be easily reverted.
  In case of error in the code, GDM will fail to load and it will be 
immediately visible.

  [Build]
  Builds and tested successfully locally.
  Besides the updated JS is not compiled as part of build.

  [Upstream Issue]
  https://gitlab.gnome.org/GNOME/gdm/-/issues/684

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


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


[Desktop-packages] [Bug 2018672] Re: Gnome 44: GDM background configurable with gsettings

2023-05-17 Thread Daniel van Vugt
** Tags added: lunar

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

Title:
  Gnome 44: GDM background configurable with gsettings

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  The prior implementation of exposing the login screen background setting via 
`gsettings` is not working as expected in Gnome 44 and Ubuntu 23.04. 
Specifically, the background image is infact set, however, the default Gnome 
theme appears as an overlay on top of the com.ubuntu.login-screen schema.

  This appears as the default grey background with a remarkably high
  alpha value of 0.975 from my inspection. If you set a very high
  contrast background image, you can just make out the outline in
  beneath the greeter.

  My expectation would be that we can set the greeter parameters using
  the provided gsettings keys, and set the background-color to
  transparent to only display the configured background-picture-uri key.

  gdm@zen:~$ gsettings list-keys com.ubuntu.login-screen 
  background-color
  background-picture-uri
  background-repeat
  background-size

  [Test Case]
  1. Boot a desktop session
  2. Verify that the default aubergine background is displayed in the greeter.
  3. Login as the administrator of the machine
  4. Install systemd-container
  5. Switch to the GDM user:
$ sudo machinectl shell gdm@ /bin/bash
  6. Apply a different background with the command:
$ gsettings set com.ubuntu.login-screen background-picture-uri 
'file:///usr/share/backgrounds/Lunar-lobster-side_by_Gixo-light.png'
  7. Logout
  8. Verify that the image 'Lunar-lobster-side_by_Gixo-light.png' is displayed 
as the background of the greeter.
  9. Observe the remaining grey overlay with high alpha value. After login, the 
background image is briefly displayed without the overlay before initiating the 
user gnome shell session.

  [Further Investigation]
  PRATAP-KUMAR has done some excellent work overcoming this with their GitHub 
project, and it appears that modifying the Gnome theme with this script 
correctly sets the transparency. However, perhaps there are two layers to the 
greeter, and even though the background image is set, the additional layer is 
not exposed for configuration via gsettings.

  https://github.com/PRATAP-KUMAR/ubuntu-gdm-set-
  background/blob/main/ubuntu-gdm-set-
  background-23.04-transparent#L168-L171

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


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


[Desktop-packages] [Bug 2018662] Re: .

2023-05-17 Thread Daniel van Vugt
Tracking in
https://errors.ubuntu.com/problem/e1aa60358f2573f9692d2339890fc97ad0ea07b1

** Tags added: mantic

** Summary changed:

- .
+ gnome-shell crashed with SIGSEGV in clutter_actor_collect_event_actors() from 
clutter_actor_collect_event_actors() from create_event_emission_chain() from 
clutter_stage_emit_event() from emit_event()

** Tags added: lunar

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018662/+attachment/5671441/+files/CoreDump.gz

** Description changed:

- .
+ https://errors.ubuntu.com/problem/e1aa60358f2573f9692d2339890fc97ad0ea07b1
  
  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 44.0-2ubuntu3
  Uname: Linux 6.2.0-21-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  6 22:51:04 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1680272303
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/la9ui
  ProcEnviron:
-  LANG=nb_NO.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=nb_NO.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  clutter_actor_collect_event_actors() from
  clutter_actor_collect_event_actors() from
  create_event_emission_chain() from clutter_stage_emit_event() from
  emit_event()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 44.0-2ubuntu3
  Uname: Linux 6.2.0-21-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  6 22:51:04 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1680272303
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/la9ui
  ProcEnviron:
   LANG=nb_NO.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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


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


[Desktop-packages] [Bug 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

2023-05-17 Thread Dominik Viererbe
I can not replicate the state when the "Orientation" setting in the
"Display Settings" Menu shows no dropdown menu when clicked.

I will set this bug also to "Incomplete" for "gnome-shell (Ubuntu)"

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

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

Title:
  ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

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


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


[Desktop-packages] [Bug 2019945] Re: gnome-shell crashed with SIGSEGV in clutter_actor_collect_event_actors() from clutter_actor_collect_event_actors() from create_event_emission_chain() from clutter_

2023-05-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2018662 ***
https://bugs.launchpad.net/bugs/2018662

** Summary changed:

- 
/usr/bin/gnome-shell:11:clutter_actor_collect_event_actors:clutter_actor_collect_event_actors:create_event_emission_chain:clutter_stage_emit_event:emit_event
+ gnome-shell crashed with SIGSEGV in clutter_actor_collect_event_actors() from 
clutter_actor_collect_event_actors() from create_event_emission_chain() from 
clutter_stage_emit_event() from emit_event()

** This bug has been marked a duplicate of private bug 2018662

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

Title:
  gnome-shell crashed with SIGSEGV in
  clutter_actor_collect_event_actors() from
  clutter_actor_collect_event_actors() from
  create_event_emission_chain() from clutter_stage_emit_event() from
  emit_event()

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 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/e1aa60358f2573f9692d2339890fc97ad0ea07b1 
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/2019945/+subscriptions


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


[Desktop-packages] [Bug 2019945] [NEW] gnome-shell crashed with SIGSEGV in clutter_actor_collect_event_actors() from clutter_actor_collect_event_actors() from create_event_emission_chain() from clutte

2023-05-17 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 2018662 ***
https://bugs.launchpad.net/bugs/2018662

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 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/e1aa60358f2573f9692d2339890fc97ad0ea07b1 
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

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

Title:
  gnome-shell crashed with SIGSEGV in
  clutter_actor_collect_event_actors() from
  clutter_actor_collect_event_actors() from
  create_event_emission_chain() from clutter_stage_emit_event() from
  emit_event()

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 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/e1aa60358f2573f9692d2339890fc97ad0ea07b1 
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/2019945/+subscriptions


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


[Desktop-packages] [Bug 2018603] Re: Inconsistent cursor size with fractional scaling

2023-05-17 Thread Daniel van Vugt
Workaround:

  gnome-extensions disable d...@rastersoft.com

** Package changed: mutter (Ubuntu) => gnome-shell-extension-desktop-
icons-ng (Ubuntu)

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

Title:
  Inconsistent cursor size with fractional scaling

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Triaged

Bug description:
  When fractional scaling is enabled (I use 250%), the mouse cursor
  becomes very large when hovering over the desktop and in some
  applications. It returns to its normal size when moved over the panel,
  dock and most Gnome apps (evince is a notable exception here). The
  issue appeared after the update to 23.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: mutter 44.0-2ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  5 15:41:32 2023
  InstallationDate: Installed on 2019-10-31 (1282 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to lunar on 2023-05-05 (0 days ago)

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


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


[Desktop-packages] [Bug 2018535] Re: Dialog boxes are displayed on background (hidden) on second monitor

2023-05-17 Thread Daniel van Vugt
** Tags added: multimonitor

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

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

Title:
  Dialog boxes are displayed on background (hidden) on second monitor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Dialog boxes of applications opened on the second screen (side by side mode) 
are displayed hidden behind the main application window.
  The same problem does not happen if the application is open on the first 
screen.

  When trying to take a screenshot to send here the image is updated and
  the dialog is displayed over the main application window.

  How to reproduce it:
  Open gnome text editor and when open preferences dialog. If you do it on the 
first screen you can see the dialog box but do it on the second screen you 
cannot see the dialog box.

  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-12 (481 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-27 (10 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 2018458] Re: Video glitch

2023-05-17 Thread Daniel van Vugt
Please make a video of the problem using a phone and then attach it
here.

** Tags removed: wayland-session

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Video glitch

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when
  there is a fast movement on video the picture blurs and shifts, this
  bug is only on X11, on waywand everything is ok

  this is my system:
  6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroRelease: Ubuntu 23.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0]
  MachineType: LENOVO 21E6006WBM
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags: wayland-session lunar ubuntu
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2023
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET47W(1.18)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E6006WBM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4:
  dmi.product.family: ThinkPad E15 Gen 4
  dmi.product.name: 21E6006WBM
  dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4
  dmi.product.version: ThinkPad E15 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2018297] Missing required logs.

2023-05-17 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2018297

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

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


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


[Desktop-packages] [Bug 2018155] Re: Can't login to Xorg sessions if desktop zoom was already enabled

2023-05-17 Thread Daniel van Vugt
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2815
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2815

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

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

Title:
  Can't login to Xorg sessions if desktop zoom was already enabled

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 'org.gnome.ScreenSaver'
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session[7361]: 
gnome-session-binary[7361]: WARNING: Could not retrieve current screensaver 
active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient 
disconnected from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session-binary[7361]: 
WARNING: Could not retrieve current screensaver active state: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.impl.portal.desktop.gtk'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.portal.Desktop'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal.service - Portal service.
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: New theme: 
gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: All 
available theme snaps installed
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7984]: libEGL warning: 
DRI2: failed to authenticate
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: gnome-shell[7863]: 
segfault at 18 ip 7f7af86b2004 sp 7ffeb1dc3a18 error 4 in 
libmutter-12.so.0.0.0[7f7af864a000+13d000] likely on CPU 15 (core 15, socket 0)
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: Code: 00 00 00 00 66 90 f3 
0f 1e fa 48 63 05 79 67 16 00 48 8b 04 07 c3 f3 0f 1e fa 48 8b 87 40 01 00 00 
c3 0f 1f 40 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 
8b 47 28 c3 0f
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Main process exited, 

[Desktop-packages] [Bug 2018155] Re: Can't login to Xorg sessions if desktop zoom was already enabled

2023-05-17 Thread Daniel van Vugt
Confirmed - the segfault is mentioned in the log but failing to leave
any crash file.

I've reconfigured my system to produce core files instead and got:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2456
Downloading source file 
/usr/src/mutter-44.0-2ubuntu4/obj-x86_64-linux-gnu/../src/core/display.c
2456  return display->x11_display;  
[Current thread is 1 (Thread 0x7f495063c600 (LWP 2641))]
(gdb) bt
#0  meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2456
#1  0x7f4954ae206b in meta_cursor_sprite_xfixes_initable_init
(initable=0x5643a0a1b1e0, cancellable=, 
error=0x7ffeb6a7cf00) at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:134
#2  0x7f49550a89c4 in g_initable_new_valist
(object_type=, first_property_name=0x7f4954ba6c50 "display", 
var_args=var_args@entry=0x7ffeb6a7ce10, cancellable=cancellable@entry=0x0, 
error=error@entry=0x7ffeb6a7cf00) at ../../../gio/ginitable.c:250
#3  0x7f49550a8abd in g_initable_new
(object_type=, cancellable=cancellable@entry=0x0, 
error=error@entry=0x7ffeb6a7cf00, 
first_property_name=first_property_name@entry=0x7f4954ba6c50 "display") at 
../../../gio/ginitable.c:164
#4  0x7f4954aea82e in meta_cursor_sprite_xfixes_new
(error=0x7ffeb6a7cf00, cursor_tracker=0x56439f897810, display=0x0)
at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:110
#5  ensure_xfixes_cursor (tracker_x11=tracker_x11@entry=0x56439f897810)
at ../src/backends/x11/meta-cursor-tracker-x11.c:94
#6  0x7f4954aea8bd in meta_cursor_tracker_x11_get_sprite
(tracker=0x56439f897810)
at ../src/backends/x11/meta-cursor-tracker-x11.c:162
#7  0x7f4954a76fde in meta_cursor_tracker_get_sprite
(tracker=) at ../src/backends/meta-cursor-tracker.c:361
#8  0x7f4954c2a8b6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#9  0x7f4954c2734d in ffi_call_int
(cif=cif@entry=0x5643a0a06b60, fn=, rvalue=, 
avalue=, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#10 0x7f4954c29f33 in ffi_call
(cif=0x5643a0a06b60, fn=, rvalue=, 
avalue=) at ../src/x86/ffi64.c:710
#11 0x7f4954de51f9 in Gjs::Function::invoke(JSContext*, JS::CallArgs 
const&, JS::Handle, _GIArgument*)
(this=, context=0x56439fb35460, args=, 
this_obj=..., r_value=)
at /usr/src/gjs-1.76.0-3/obj-x86_64-linux-gnu/../gi/function.cpp:1050

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

Title:
  Can't login to Xorg sessions if desktop zoom was already enabled

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated 

[Desktop-packages] [Bug 2018363] Re: Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings

2023-05-17 Thread Daniel van Vugt
** Summary changed:

- Connection button is disabled in Bluetooth settings
+ Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings

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

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

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

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

Title:
  Sony LE_WH-1000XM5 Connection button is disabled in Bluetooth settings

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

Bug description:
  Device appears as paired but the Connection button is disabled. I can't click 
the button to connect the device.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-09-28 (222 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 21D8CTO1WW
  Package: gnome-control-center
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=20c02ac6-394b-416e-8c15-f3f909240844 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev root sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/09/2023
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3EET29W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21D8CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3EET29W(1.15):bd03/09/2023:br1.15:efr1.12:svnLENOVO:pn21D8CTO1WW:pvrThinkPadP15vGen3:rvnLENOVO:rn21D8CTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D8_BU_Think_FM_ThinkPadP15vGen3:
  dmi.product.family: ThinkPad P15v Gen 3
  dmi.product.name: 21D8CTO1WW
  dmi.product.sku: LENOVO_MT_21D8_BU_Think_FM_ThinkPad P15v Gen 3
  dmi.product.version: ThinkPad P15v Gen 3
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 3C:E9:F7:5A:31:C3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:20013 acl:0 sco:0 events:3219 errors:0
TX bytes:790999 acl:0 sco:0 commands:3217 errors:0

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


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


[Desktop-packages] [Bug 2018296] Re: 23.04 org.gnome.Shell wayland.service dumped randomly

2023-05-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2012230 ***
https://bugs.launchpad.net/bugs/2012230

Thanks, that's bug 2012230.

** This bug has been marked a duplicate of bug 2012230
   gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from destroy_data_offer() from destroy_resource()

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

Title:
  23.04 org.gnome.Shell wayland.service dumped randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I would like to report an issue with "org.gnome.Shell wayland.service".
  The process seem to randomly crash with a code dumped, leading to getting 
disconnected from the session.

  1751786184:May 02 12:52:01 lapbios systemd[336486]:
  org.gnome.Shell[at]wayland.service: Main process exited, code=dumped,
  status=11/SEGV

  I found a similar report on AskUbuntu
  (https://askubuntu.com/questions/1465560/lunar-lobster-wayland-
  crashes) without answer yet.

  I'm running Ubuntu 23.04 on a Razer Blade 15 2019 (i7, RTX 2070). This
  issue appeared after upgrade to 23.04.

  I identified a few cases where the bug occurs, 100% chance when
  dragging a tab in Firefox over the taskbar. Sometimes when dragging an
  icon on the desktop. Sometimes when the screen dim to lock the laptop.

  I am not sure where to find the core dump or crash report. (Apport
  never showed up) I will gladly help gather more information !

  Thanks

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


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


[Desktop-packages] [Bug 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

2023-05-17 Thread Daniel van Vugt
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

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


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


[Desktop-packages] [Bug 2018316] Re: wireplumber sometime segfault on bluez devices disconnect

2023-05-17 Thread Daniel van Vugt
** Also affects: pipewire via
   https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/430
   Importance: Unknown
   Status: Unknown

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

Title:
  wireplumber sometime segfault on bluez devices disconnect

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Jammy:
  Confirmed
Status in pipewire source package in Lunar:
  Fix Committed

Bug description:
  * Impact

  wireplumber sometime segfault on bluez devices disconnect leading to
  non working pipewire audio

  * Test case

  Connect and disconnect bluetooth audio devices and ensure
  wireplumber/pipewire-pulse don't hit an error and sound keeps working
  in the desktop (sound settings testsound, rhythmbox, firefox playing
  video)

  and check that error reports stop on 
  https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53

  * Regression potential

  The change is in the pipewire bluez plugin so the testing should focus
  on bluetooth audio devices

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


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


[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Alkis Georgopoulos
** Changed in: ltsp (Ubuntu)
   Status: New => Invalid

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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


[Desktop-packages] [Bug 2017523] Re: Launched application in second to last position in dock

2023-05-17 Thread Daniel van Vugt
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Launched application in second to last position in dock

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

Bug description:
  Action: Launch an application, when other applications are running
  that are not pinned.

  Expected result: The icon of the newly launched application appears at
  the end of the list of running applications.

  Actual result: The icon of the newly launched application appears in
  second to last position in the running applications in the dock.

  
  Ubuntu 22.04.2 LTS
  gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1

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


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


[Desktop-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
** Tags added: rls-mm-incoming

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

Title:
  Outdated documentation about NetworkManager keyfiles

Status in debian-handbook package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in fai package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in wifi-qr package in Ubuntu:
  New

Bug description:
  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions


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


[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
netcfg is not part of Ubuntu anymore (got dropped post Focal)

** Changed in: netcfg (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  New
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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


[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
Netplan deals with keyfiles in /run/NetworkManager/system-connections
not /etc/...

** Changed in: netplan.io (Ubuntu)
   Status: New => Won't Fix

** Tags added: rls-mm-incoming

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  New
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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


[Desktop-packages] [Bug 2019940] [NEW] Directly manipulating NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
Public bug reported:

The affected packages can manipulate NetworkManager keyfiles directly on
disk, which might not be appropriate anymore on Ubuntu, since the
Netplan integration was enabled in NetworkManager (starting with
Mantic), migrating any keyfile configuration from
/etc/NetworkManager/system-connections/*[.nmconnection] to
/etc/netplan/90-NM-*.yaml

See Netplan's documentation for how connections are handled:
https://netplan.readthedocs.io/en/latest/netplan-everywhere/

PS: Packages were queried using:
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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

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

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: cruft-ng (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: forensic-artifacts (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: guestfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: netcfg (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

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

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

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

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

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


** Tags: netplan-everywhere rls-mm-incoming

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: guestfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cruft-ng (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: forensic-artifacts (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  New
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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

[Desktop-packages] [Bug 2018155] Re: Having desktop zoom enabled prevents X11 logins

2023-05-17 Thread Daniel van Vugt
** Summary changed:

- gnome-magnifier prevents starting a graphical session
+ Having desktop zoom enabled prevents X11 logins

** Summary changed:

- Having desktop zoom enabled prevents X11 logins
+ Can't login to Xorg sessions if desktop zoom was already enabled

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

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

Title:
  Can't login to Xorg sessions if desktop zoom was already enabled

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 'org.gnome.ScreenSaver'
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session[7361]: 
gnome-session-binary[7361]: WARNING: Could not retrieve current screensaver 
active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient 
disconnected from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session-binary[7361]: 
WARNING: Could not retrieve current screensaver active state: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.impl.portal.desktop.gtk'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.portal.Desktop'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal.service - Portal service.
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: New theme: 
gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: All 
available theme snaps installed
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7984]: libEGL warning: 
DRI2: failed to authenticate
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: gnome-shell[7863]: 
segfault at 18 ip 7f7af86b2004 sp 7ffeb1dc3a18 error 4 in 
libmutter-12.so.0.0.0[7f7af864a000+13d000] likely on CPU 15 (core 15, socket 0)
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: Code: 00 00 00 00 66 90 f3 
0f 1e fa 48 63 05 79 67 16 00 48 8b 04 07 c3 f3 0f 1e fa 48 8b 87 40 01 00 00 
c3 0f 1f 40 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 
8b 47 28 c3 0f
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Failed with 

[Desktop-packages] [Bug 2017523] Re: Launched application in second to last position in dock

2023-05-17 Thread Daniel van Vugt
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Launched application in second to last position in dock

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

Bug description:
  Action: Launch an application, when other applications are running
  that are not pinned.

  Expected result: The icon of the newly launched application appears at
  the end of the list of running applications.

  Actual result: The icon of the newly launched application appears in
  second to last position in the running applications in the dock.

  
  Ubuntu 22.04.2 LTS
  gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1

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


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


[Desktop-packages] [Bug 2019939] [NEW] Outdated documentation about NetworkManager keyfiles

2023-05-17 Thread Lukas Märdian
Public bug reported:

The affected packages contain documentation or examples about
NetworkManager keyfiles, which might not be appropriate anymore on
Ubuntu, since the Netplan integration was enabled in NetworkManager
(starting with Mantic), migrating any keyfile configuration from
/etc/NetworkManager/system-connections/*[.nmconnection] to
/etc/netplan/90-NM-*.yaml

See Netplan's documentation for how connections are handled:
https://netplan.readthedocs.io/en/latest/netplan-everywhere/

PS: Packages were queried using:
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

** Affects: debian-handbook (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

** Affects: wifi-qr (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: netplan-everywhere rls-mm-incoming

** Also affects: debian-handbook (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml
  
  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/
+ 
+ PS: Packages were queried using:
+ 
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

** Also affects: wifi-qr (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-user-docs (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: network-manager-l2tp (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Netplan Everywhere: Outdated documentation about NetworkManager keyfiles
+ Outdated documentation about NetworkManager keyfiles

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

Title:
  Outdated documentation about NetworkManager keyfiles

Status in debian-handbook package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in fai package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in wifi-qr package in Ubuntu:
  New

Bug description:
  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions


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


[Desktop-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje

2023-05-17 Thread Daniel van Vugt
** Changed in: ayatana-indicator-messages (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: ayatana-indicator-messages (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  indicator-messages-service crashed with SIGSEGV in
  g_type_check_instance() from g_signal_handlers_disconnect_matched()
  from act_user_manager_finalize() from g_object_unref() from
  im_accounts_service_dispose()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in ayatana-indicator-messages package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-messages.  This problem was most recently seen with package version 
13.10.1+18.10.20180918-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 
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/accountsservice/+bug/2015962/+subscriptions


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


[Desktop-packages] [Bug 1990089] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

2023-05-17 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


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

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

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

Thank you!

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  

[Desktop-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

2023-05-17 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


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

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

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

Thank you!

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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


[Desktop-packages] [Bug 2015577] Re: middle click to lower window no longer works for xwayland windows

2023-05-17 Thread Daniel van Vugt
** No longer affects: xwayland (Ubuntu)

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

Title:
  middle click to lower window no longer works for xwayland windows

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

Bug description:
  i have titlebar middle-click set to lower windows in Tweaks.  In
  kinetic, this works for xwayland windows, while in lunar it no longer
  does.  (native wayland gtk3 and gtk4 apps do appear to work though,
  which was a long time coming!)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xwayland 2:22.1.8-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Fri Apr  7 08:54:02 2023
  InstallationDate: Installed on 2019-08-17 (1329 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago)

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


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


[Desktop-packages] [Bug 2017142] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

2023-05-17 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)


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

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

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

Thank you!

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

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


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


[Desktop-packages] [Bug 2000940] Re: Application "Startup Application Preferences" is not translated

2023-05-17 Thread Daniel van Vugt
** Tags added: lunar

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

Title:
  Application "Startup Application Preferences" is not translated

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  The application "Startup Application Preferences" is not translated.
  See image below.
  Regards,
  Roxfr

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


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


[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

2023-05-17 Thread Daniel van Vugt
Sounds like we have two bugs:

1. gnome-shell-extension-appindicator

2. AnyDesk

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

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


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


[Desktop-packages] [Bug 2015962] Proposed package upload rejected

2023-05-17 Thread Chris Halse Rogers
An upload of ayatana-indicator-messages to lunar-proposed has been
rejected from the upload queue for the following reason: "Rejecting from
the queue as this is still missing SRU information, and that should
notify someone who cares :). The diff itself looks fine, although the it
now also needs fixing in mantic and the lunar upload needs a non-
conflicting version number. Please feel free to reupload with those
fixed.".

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

Title:
  indicator-messages-service crashed with SIGSEGV in
  g_type_check_instance() from g_signal_handlers_disconnect_matched()
  from act_user_manager_finalize() from g_object_unref() from
  im_accounts_service_dispose()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in ayatana-indicator-messages package in Ubuntu:
  Incomplete
Status in indicator-messages package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-messages.  This problem was most recently seen with package version 
13.10.1+18.10.20180918-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 
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/accountsservice/+bug/2015962/+subscriptions


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


[Desktop-packages] [Bug 1970615] Re: WebGL does not work in snap firefox

2023-05-17 Thread Daniel van Vugt
> I experience the same, should I open a new bug report?

Yes please.

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

Title:
  WebGL does not work in snap firefox

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since upgrading to Ubuntu 22.04 LTS I am no longer able to use WebGL
  on firefox.

  If I go to https://get.webgl.org/ it says
  "Hmm. While your browser seems to support WebGL, it is disabled or 
unavailable. If possible, please ensure that you are running the latest drivers 
for your video card."

  This is the case on my laptop with Intel HD4600 Graphics and on my
  desktop with AMD Vega 56 Graphics. Both are on Ubuntu 22.04 LTS with
  snap firefox.

  troels@troels-thinkpad:~$ glxinfo | grep OpenGL
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
  OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1
  OpenGL core profile shading language version string: 4.60
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 22.0.1
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
  OpenGL ES profile extensions:

  
  I therefore have to use Chrome instead for developement using three.js

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


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


[Desktop-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)

2023-05-17 Thread Daniel van Vugt
This bug is about the open source nouveau driver only.

The issue in comment #38 is covered in bug 938751.

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Workaround/Fix]

  1. When starting the Ubuntu live image, select the option 'Ubuntu
  (safe graphics)' from the boot menu.

  2. During installation be sure to select the third-party software
  option checkbox in order to get the right Nvidia driver installed.

  [Original Description]

  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2015674] Re: Unread mail notifications do not update

2023-05-17 Thread Dror
I found the reason for this:
The number icons (not just for Thunderbird) are actually indicating the 
notifications in the main notification window of Ubuntu (under the date at the 
top bar of Ubuntu) and not the actual unread emails.

So even after reading an email, as the notification still exists in the
main notification window, the number icon will not disappear.

If we remove/clear/click the notification in the main notification
window, it will clear the number icon (even if the email is still unread
in Thunderbird)

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

Title:
  Unread mail notifications do not update

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The Thunderbird icon on the dock shows the count of new mails
  correctly, but the icon does not update itself once the emails have
  been read. Even restarting the app will not update the icon.

  I would expect the notification icon to show zero (new emails) once
  the mails have been read.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: thunderbird 1:102.10.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BuildID: 20230405152512
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  9 12:11:34 2023
  ForcedLayersAccel: False
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Finnish Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2022-03-22 (382 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 
600
  MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-af991e4b-f99c-455f-8b24-2a1ee2160904
   bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
  UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
  dmi.bios.date: 06/27/2022
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET72W(1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UH001AMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.41
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UH001AMX
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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


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


[Desktop-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-05-17 Thread Daniel van Vugt
I'm not sure why the mode would be limited to 60Hz but you should know
that Xorg's multi-monitor support is very limited. It can only update
all monitors at the same time at the same rate. So if you have a 60Hz
monitor connected then it's possible Xorg will limit all monitors to
60Hz.

Even if all your monitors are the same refresh rate, Xorg is still a
menace because it tries to update all of them at the same time even if
their clocks aren't in sync. This means you might see tearing.

Wayland solves all of the above.

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

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  Add to /etc/environment (in Ubuntu 22.04):

    MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

  or in Ubuntu 22.10 and later:

    MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and then reboot.

  [ Upstream bugs ]

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2749

  [ Original report ]

  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

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


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


[Desktop-packages] [Bug 1854222] Re: Screen keyboard improperly appears on laptops with touchscreen

2023-05-17 Thread Daniel van Vugt
** Tags added: osk

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

Title:
  Screen keyboard improperly appears on laptops with touchscreen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 18.04.3 LTS
  gnome-shell version 3.28.4-0ubuntu18.04.2

  Directions to produce bug:
  * Install Ubuntu 18.04 onto a laptop with a touchscreen.
  * Install uxterm package.
  * Upgrade software packages to most recent version.
  * Confirm "Screen Keyboard" and "Typing Assist" are disabled in Universal 
Access.
  * Reboot.
  * Log in and start "uxterm".
  * Switch focus to another window.
  * Touch the "uxterm" window.

  Expected proper behavior: "uxterm" window gets focus, no other
  actions.

  Actual inappropriate behavior: "uxterm" window gets focus, and screen
  keyboard appears in defiance of "Screen Keyboard: off" setting and
  presence of undetachable physical keyboard.

  Empirical testing indicates that the screen keyboard doesn't appear
  for every touch, but seems to appear for every touch to any area that
  accepts text input, or perhaps for all areas that aren't internally
  marked somehow as not accepting text.

  This is a reappearance of Bug #1723857.  The reappearance was noted in
  comments 61 and 62 of that bug, but apparently ignored because the bug
  is closed.  I am creating this as a new bug per the guidance in
  1723857#60: "This bug is closed so if you experience any problem at
  all then please open a new one." by Daniel van Vugt (vanvugt).

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


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


[Desktop-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep

2023-05-17 Thread Arthur
Happens with me too after sleep/wakeup lenovo x1 carbon gen8 / HDMI LG 27GL850 
which should run at 2460x1440@60hz but instead its 1920x1080@60hz.
In my case only restart works. One thing I noticed is that my screen is 
initally determined as LG Electronics 31" but its actually 27" monitor

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

Title:
  [amdgpu] Wrong external screen resolution after wake up from sleep

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

Bug description:
  After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
  running KDE) I started experiencing a problem with external screen
  resolution after the wake up from sleep. The monitor resolution is
  small (1280x768) and doesn't respect the setting prior the sleep
  (1920x1200).

  After the wake up from sleep:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  There is an error when trying to change the setting to the highest
  resolution supported by the monitor (which is not included in the
  above list).

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  xrandr: cannot find mode 1920x1200
  ```

  After the turn off and turn on of the external monitor, the resolution
  is somehow added to the xrandr list:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95 +
 # a list of resolutions
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  Now it is possible to change the resolution:

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  # no output, the resolution was successfully changed
  ```   

  After the change, the resolution is successfully changed and xrandr
  gives proper output:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95*+
 # a list of lower resolutions
  ```

  The problem is not present on fresh start. However, it is consistently
  present after the wake up from sleep.

  What can cause the problem and how may I fix it?

  Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
  external monitor is connected via USB-C. There are no problems with
  laptop screen resolution, only external monitor is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jun 16 18:12:05 2022
  DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2019-08-21 (1030 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20NE000BMC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
  dmi.bios.date: 01/26/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET44W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NE000BMC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  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: 

[Desktop-packages] [Bug 2015543] Re: Update to the upstream 1.12.1 bugfix version

2023-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package wpebackend-fdo - 1.12.1-0ubuntu1

---
wpebackend-fdo (1.12.1-0ubuntu1) jammy; urgency=medium

  * New bugfix version (lp: #2015543)

 -- Sebastien Bacher   Fri, 07 Apr 2023 11:50:27
+0200

** Changed in: wpebackend-fdo (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update to the upstream 1.12.1 bugfix version

Status in wpebackend-fdo package in Ubuntu:
  Fix Released
Status in wpebackend-fdo source package in Jammy:
  Fix Released

Bug description:
  * Impact

  The update fixes memory handling issues which could potential have
  security implication. It was requested by the MIR team on
  https://bugs.launchpad.net/ubuntu/+source/wpebackend-
  fdo/+bug/1973033/comments/11 as we need to promote the package for
  incoming webkitgtk security updates

  Fedora issues an update on similar concern
  https://bodhi.fedoraproject.org/updates/FEDORA-2022-f98ab9f311

  * Testcase

  Unfortunately it's not easy to test wpebackend-fdo since the project
  has no tests nor demo utility. The backend is used mostly by webkitgtk
  but the current archive version is built without that option. It is a
  requirement for newer webkitgtk series though and such for incoming
  security update (since newer webkitgtk series are rolled out as
  security updates)

  * Regression potential

  The changes are small fixes for memory management issues but if those
  were wrong then it could lead to rendering issues or crashes in
  webkitgtk clients once webkitgtk is build with libwpe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/2015543/+subscriptions


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