date:20230118

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

** Tags added: fixed-in-mutter-44 fixed-upstream

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

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

Title:
  gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv()
  from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from
  create_renderer_gpu_data_gbm()

Status in mutter package in Ubuntu:
  Fix Committed

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 
43.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd 
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/mutter/+bug/1994011/+subscriptions


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

[Desktop-packages] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon

2023-01-18 Thread Kai-Chuan Hsieh

Test on Precision 5750 with jammy.

xorg-server (2:21.1.3-2ubuntu2.5) will gets below error:

Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]: X Error of failed 
request:  BadValue (integer parameter out of range for operation)
Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]:   Major opcode of 
failed request:  140 (RANDR)
Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]:   Minor opcode of 
failed request:  35 (RRSetProviderOutputSource)
Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]:   Value in failed 
request:  0x45
Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]:   Serial number 
of failed request:  16
Jan 19 09:23:14 u-Precision /usr/libexec/gdm-x-session[2139]:   Current serial 
number in output stream:  17

xorg-server (2:21.1.3-2ubuntu2.6), the error didn't occur.

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

Title:
  Xorg crashed with SIGABRT in xf86ModeVRefresh() from
  drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from
  xf86ProbeOutputModes() from xf86InitialConfiguration()

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed
Status in xorg-server source package in Lunar:
  Confirmed

Bug description:
  [Impact]
  The recent SRU'd patch had a bug in it that caused a crash if 
xf86ModeVRefresh returned 0. Amend the patch to fix this.

  [Test case]
  Would need an affected system to test this on, but we haven't been able to 
reproduce this even on an identical system as on one of the reported errors 
(XPS 15 9560).

  [Where things could go wrong]
  This only adds a new check.

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:21.1.4-2ubuntu1.2, the problem page at 
https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 
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/xorg-server/+bug/1999008/+subscriptions


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

[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions

Anas,

Please open your own bug by running:

  ubuntu-bug gnome-shell

so that we can analyse your system separately.

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Desktop-packages] [Bug 2003283] [NEW] Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

2023-01-18 Thread edwin

Public bug reported:

Ubuntu 22.04 Remote Desktop can only show the screen of the main monitor
but not for the second monitor. It did work in Ubuntu 20.04 without any
problem on the same computer.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
Uname: Linux 6.1.4-060104-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 19 11:03:30 2023
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2023-01-10 (8 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Ubuntu22.04 Remote Desktop doesn't support to display the screen of
  the second monitor

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

Bug description:
  Ubuntu 22.04 Remote Desktop can only show the screen of the main
  monitor but not for the second monitor. It did work in Ubuntu 20.04
  without any problem on the same computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
  Uname: Linux 6.1.4-060104-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 19 11:03:30 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-01-10 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions

2023-01-18 Thread Anas Bouzid

After updating nvidia to 525.78.01 the lag reappears, the external
monitor is extremly slow again. I've tries purging nvidia* and xserver-
xorg-video-amdgpu but no luck.

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

Title:
  Displaylink is extremely slow in Xorg sessions

Status in Nouveau Xorg driver:
  New
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Hirsute:
  Won't Fix
Status in xorg-server source package in Impish:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  New
Status in xserver-xorg-video-nouveau source package in Jammy:
  New

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Desktop-packages] [Bug 2003237] Re: Monitor does not turn off after idle timeout is reached

** Tags added: amdgpu

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

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

Title:
  Monitor does not turn off after idle timeout is reached

Status in mutter package in Ubuntu:
  New

Bug description:
  My Screen Blank setting is set to 15 minutes. My Lock Screen settings
  are also set to automatically lock the system after the blank screen
  timeout is reached.

  After 15 minutes Ubuntu does lock me out, but the monitor does not
  power off as it's supposed to - the screen is simply black. Please see
  the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 18 23:48:13 2023
  DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
     Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2018-03-17 (1768 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago)
  dmi.bios.date: 05/29/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4211
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-D
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

Scott,

Please open a new bug by running:

  ubuntu-bug gnome-shell

so that we can investigate your system separately.

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

I was expecting upstream to say "won't fix". Aside from the protocol
saying it's the expected behaviour, we also wouldn't want to impact
performance of fullscreen games just because they accidentally used RGBA
instead of RGBX or RGB. So disallowing anything to show through in full
screen makes sense to me, on balance.

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

** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues 
#116
   https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116

** Also affects: wayland via
   https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116
   Importance: Unknown
   Status: Unknown

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

** Changed in: mutter (Ubuntu)
   Status: Triaged => Won't Fix

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

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in Mutter:
  New
Status in wayland:
  Unknown
Status in mutter package in Ubuntu:
  Won't Fix
Status in wayland package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

That's probably not as good as sticking to nouveau because it will fall
back to software rendering instead. But the third and best option is to
install an Nvidia driver using the 'Additional Drivers' app.

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  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/linux/+bug/2003031/+subscriptions


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

[Desktop-packages] [Bug 1752680] Re: Night light does not work after resume from suspend or unlock.

** Tags added: gamma nightlight

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

Title:
  Night light does not work after resume from suspend or unlock.

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic N/A
   linux-firmware 1.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Desktop-packages] [Bug 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen

** Tags added: nightlight

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

Title:
  Night light does not work on laptop screen when disconnecting from
  external screen

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When I turn on my laptop while it is connected to an external screen
  (my display settings are such that only the external screen is used
  while it is connected) and later disconnect it, Night Light does not
  work on the laptop screen (it did on the external screen). I have
  Night Light on "Manual Schedule" from 00:00 to 23:59 so it would
  always be on. Turning the Night Light setting off and on again does
  not help.

  After restarting the laptop while it is not connected to the external
  screen, Night Light will work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 21:27:17 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-09 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago)

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


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

[Desktop-packages] [Bug 1772212] Re: [nvidia] Night light doesn't cover all monitors fully

** Tags added: gamma nightlight

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

Title:
  [nvidia] Night light doesn't cover all monitors fully

Status in GNOME Settings Daemon:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  The GNOME night light only seems to work on the first half of the
  first screen within a dual monitor setup (Ubuntu 18.04 stock, using
  X11 with Gefore GT240, NVIDIA proprietary drivers).  See attached
  screenshots.

  br, Koen.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  koen   1820 F pulseaudio
   /dev/snd/controlC1:  koen   1820 F pulseaudio
   /dev/snd/controlC3:  koen   1820 F pulseaudio
   /dev/snd/controlC2:  koen   1820 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=9b7457bf-328f-4fe5-9e46-ed14b65d4fb2
  InstallationDate: Installed on 2018-05-05 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp0s10   no wireless extensions.
  MachineType: . .
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5dcdbe58-6afd-4f90-ab58-1f53f5cfa9f4 ro
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 07/31/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: AN-M2HD(MCP68)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Unknow
  dmi.chassis.type: 3
  dmi.chassis.vendor: nVIDIA
  dmi.chassis.version: Unknow
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/31/2008:svn.:pn.:pvrUnknow:rvnhttp//www.abit.com.tw/:rnAN-M2HD(MCP68):rvr1.x:cvnnVIDIA:ct3:cvrUnknow:
  dmi.product.name: .
  dmi.product.version: Unknow
  dmi.sys.vendor: .

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


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

[Desktop-packages] [Bug 1995783] Re: Nightlight fails after suspend

** Tags added: nightlight

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

Title:
  Nightlight fails after suspend

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Nightlight activates when turned on in settings but after closing the
  lid or otherwise suspending and then resuming power nightlight fails
  to change the color temperature.  Settings still indicates that
  nightlight is on.  If nightlight setting is cycled nightlight works
  again until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 
UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 22:03:14 2022
  DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.154, 5.15.0-52-generic, x86_64: installed
   nvidia/390.154, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:212b]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b]
  InstallationDate: Installed on 2019-01-15 (1390 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK Computer Inc. N55SL
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SL.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.family: N
  dmi.product.name: N55SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  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/mutter/+bug/1995783/+subscriptions


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

[Desktop-packages] [Bug 1999122] Re: Gnome 42.5 Nigth Light does not work properly with dual monitors

** Package changed: gnome-shell (Ubuntu) => mutter (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/1999122

Title:
  Gnome 42.5 Nigth Light does not work properly with dual monitors

Status in mutter package in Ubuntu:
  New

Bug description:
  I`am using dual monitors Huawei Mateview GT 27'', VA, QHD, 165Hz,
  1500R, HDR, Display on my working PC. They are connected to AMD Radeon
  RX5500XT video card with HDMI (one monitor) and Display port (second
  monitor).

  The problem is that Gnome Night Light works only to one monitor
  (connected to DP). There is no matter whether you are using Wayland or
  Xorg session. The result is always the same. I have tested Redshift
  which  works only with Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  8 09:11:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-11-03 (35 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  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/mutter/+bug/1999122/+subscriptions


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

[Desktop-packages] [Bug 2003266] Re: 22.04 package lacks GSSAPI support

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

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

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

Title:
  22.04 package lacks GSSAPI support

Status in neon27 package in Ubuntu:
  Confirmed

Bug description:
  For more information, please see
  https://github.com/notroj/neon/issues/102.

  The 22.04 built package of neon lacks GSSAPI support, whereas previous
  versions (e.g. 18.04) had this support built-in. This appears to be
  due to a recent-ish change in the build logic for neon, which changes
  when GSSAPI is compiled in to the library
  
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

  We were able to get a work around building from source with the
  following envvar during build-time:
  KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR:
  KRB5_CONFIG became KRB5_CONF_TOOL.

  Version information:

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

  $ apt show libneon27
  Package: libneon27
  Version: 0.32.2-1
  Priority: optional
  Section: universe/libs
  Source: neon27
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Laszlo Boszormenyi (GCS) 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 233 kB
  Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
  Homepage: https://notroj.github.io/neon/
  Download-Size: 102 kB
  APT-Manual-Installed: no
  APT-Sources: [corporate Launchpad mirror]
  Description: HTTP and WebDAV client library

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


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 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/2003104

Title:
  gnome-terminal transparency ignored in full screen mode

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

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 1999008] Autopkgtest regression report (xorg-server/2:21.1.4-2ubuntu1.4)

2023-01-18 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted xorg-server (2:21.1.4-2ubuntu1.4) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

libsoup2.4/2.74.3-1 (s390x)
sphinx/4.5.0-4 (armhf)
xcolorsel/1.1a-22 (armhf)
spyder/5.3.2+dfsg-1 (arm64, armhf)
mutter/43.0-1ubuntu4 (amd64, armhf)
aptdaemon/1.1.1+bzr982-0ubuntu39 (amd64, s390x)
jsurf-alggeo/0.4.1+ds-3 (s390x)
openmsx-catapult/18.0-1 (armhf)
pipewalker/0.9.4-6 (armhf)
gtk4/4.8.1+ds-1ubuntu1 (armhf)
notepadqq/2.0.0~beta1-3 (armhf)
xautomation/1.09-4 (armhf)
xautolock/1:2.2-7 (armhf)


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/kinetic/update_excuses.html#xorg-server

[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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1999008

Title:
  Xorg crashed with SIGABRT in xf86ModeVRefresh() from
  drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from
  xf86ProbeOutputModes() from xf86InitialConfiguration()

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed
Status in xorg-server source package in Lunar:
  Confirmed

Bug description:
  [Impact]
  The recent SRU'd patch had a bug in it that caused a crash if 
xf86ModeVRefresh returned 0. Amend the patch to fix this.

  [Test case]
  Would need an affected system to test this on, but we haven't been able to 
reproduce this even on an identical system as on one of the reported errors 
(XPS 15 9560).

  [Where things could go wrong]
  This only adds a new check.

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:21.1.4-2ubuntu1.2, the problem page at 
https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 
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/xorg-server/+bug/1999008/+subscriptions


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 Thread Jeremy Bicha

I verified that this regression also shows in Fedora 37. I verified
there because Fedora and Ubuntu ship a patch to enable transparency in
gnome-terminal; gnome-terminal upstream does not have that feature.

I also verified that this regression was introduced in mutter 43.1.
(transparency works in 43.0 but not in 43.1).

With that information, I found an upstream bug report. The initial
response was that the new behavior conforms to the specification and it
was suggested to maximize gnome-terminal instead of using fullscreen
mode if you want this feature.

** Changed in: mutter (Ubuntu)
Assignee: Jeremy Bicha (jbicha) => (unassigned)

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

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

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

Title:
gnome-terminal transparency ignored in full screen mode

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

Bug description:
Ubuntu 23.04 running wayland
gnome-terminal 3.46.7-1ubuntu1

In gnome-terminal, I have set the transparency to some amount. When I
go to full screen (F11), the transparency is lost and the default
transparency is used. When I exit full screen, the transparency comes
back and I can see in the profile settings that the transparency has
not changed.

It seems that tranparency was accidentally removed, and then re-added via

https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

However, maybe something was missed with regards to full screen.

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

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

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

2023-01-18 Thread Scott Carey

I tried the lines:

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple

in /etc/environment as suggested.


It does not help.  Or it did not help much.  I think the keyboard lag might be 
less prevalent, but the mouse is still problematic.


My symptoms remain the same:

1. everything is fine right after the window manager starts
2. After between 1 and 4 days (depending on usage), the mouse starts to skip 
and lag and stutter.  During this condition, moving the mouse in small circles 
is enough to send 'gnome-shell' CPU use to 100% and cause updates to the 
display to stall or pause for long intervals, sometimes many seconds, until I 
take a break with the mouse movement -- for example  Gnome System Monitor won't 
update its contents or rarely will, until I pause the mouse movement.  I am 
using the integrated GPU on my laptop in this case (no discrete GPU, Ryzen 
4750U processor).  'radontop' indicates about half of the 2GB memory reserved 
for the GPU is used, and GPU usage drops to 0% during the stalls.
3. If I log out of my user and log back in, everything is back to normal, for a 
few days.

Switching to xorg fixes it (but causes other problems).

I recently updated to 22.10 to see if that helped, it does not.

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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


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

[Desktop-packages] [Bug 2003266] [NEW] 22.04 package lacks GSSAPI support

2023-01-18 Thread Ian Williams

Public bug reported:

For more information, please see
https://github.com/notroj/neon/issues/102.

The 22.04 built package of neon lacks GSSAPI support, whereas previous
versions (e.g. 18.04) had this support built-in. This appears to be due
to a recent-ish change in the build logic for neon, which changes when
GSSAPI is compiled in to the library
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

We were able to get a work around building from source with the
following envvar during build-time:
KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG
became KRB5_CONF_TOOL.

Version information:

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

$ apt show libneon27
Package: libneon27
Version: 0.32.2-1
Priority: optional
Section: universe/libs
Source: neon27
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Laszlo Boszormenyi (GCS) 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 233 kB
Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
Homepage: https://notroj.github.io/neon/
Download-Size: 102 kB
APT-Manual-Installed: no
APT-Sources: [corporate Launchpad mirror]
Description: HTTP and WebDAV client library

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

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

Title:
  22.04 package lacks GSSAPI support

Status in neon27 package in Ubuntu:
  New

Bug description:
  For more information, please see
  https://github.com/notroj/neon/issues/102.

  The 22.04 built package of neon lacks GSSAPI support, whereas previous
  versions (e.g. 18.04) had this support built-in. This appears to be
  due to a recent-ish change in the build logic for neon, which changes
  when GSSAPI is compiled in to the library
  
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

  We were able to get a work around building from source with the
  following envvar during build-time:
  KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR:
  KRB5_CONFIG became KRB5_CONF_TOOL.

  Version information:

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

  $ apt show libneon27
  Package: libneon27
  Version: 0.32.2-1
  Priority: optional
  Section: universe/libs
  Source: neon27
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Laszlo Boszormenyi (GCS) 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 233 kB
  Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
  Homepage: https://notroj.github.io/neon/
  Download-Size: 102 kB
  APT-Manual-Installed: no
  APT-Sources: [corporate Launchpad mirror]
  Description: HTTP and WebDAV client library

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


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

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

2023-01-18 Thread Scott Carey

I tried the lines:

MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple

in /etc/environment as suggested.


It does not help.  Or it did not help much.  I think the keyboard lag might be 
less prevalent, but the mouse is still problematic.


My symptoms remain the same:

1. everything is fine right after the window manager starts
2. After between 1 and 4 days (depending on usage), the mouse starts to skip 
and lag and stutter.  During this condition, moving the mouse in small circles 
is enough to send 'gnome-shell' CPU use to 100% and cause updates to the 
display to stall or pause for long intervals, sometimes many seconds, until I 
take a break with the mouse movement -- for example  Gnome System Monitor won't 
update its contents or rarely will, until I pause the mouse movement.  I am 
using the integrated GPU on my laptop in this case (no discrete GPU, Ryzen 
4750U processor).  'radontop' indicates about half of the 2GB memory reserved 
for the GPU is used, and GPU usage drops to 0% during the stalls.
3. If I log out of my user and log back in, everything is back to normal, for a 
few days.

Switching to xorg fixes it (but causes other problems).

I recently updated to 22.10 to see if that helped, it does not.

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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


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

[Desktop-packages] [Bug 1983181] Re: Cheese Internal data stream error

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

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

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

Title:
  Cheese Internal data stream error

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  corrado@corrado-n4-kk-0718:~$ cheese

  (cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller
  than 65535 pixels are not supported

  (cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: cheese 41.1-2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 30 16:21:11 2022
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  RelatedPackageVersions:
   cheese41.1-2
   cheese-common 41.1-2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  corrado1757 F wireplumber
   /dev/snd/controlC0:  corrado1757 F wireplumber
   /dev/snd/seq:corrado1754 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-07-19 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220711.gitdfa29317-0ubuntu1
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wayland-session kinetic
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed

2023-01-18 Thread Till Kamppeter

Note that this is reported for "cups-filters" for now as the actual
packages are not yet uploaded to Lunar. You can find them, plus the new
cups-filters source package with the appropriate components removed, in
this PPA:

https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch-
dev/+packages


** Changed in: cups-filters (Ubuntu)
Milestone: None => ubuntu-23.04-feature-freeze

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This is a simplified MIR for the splitting of the cups-filters source
  package.

  With the second generation (2.x) cups-filters upstream got split into
  5 independent component repositories:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  See

  https://openprinting.github.io/cups-filters-Second-Generation-First-
  Beta-Release/

  braille-printer-app still needs some upstream work for getting
  released, the others were already released as 2.0b2.

  libcupsfilters, cups-filters, and cups-browsed contain mainly the code
  from the former cups-filters (1.x) which is already in Main. libppd
  contains code from CUPS (libcups and cups-ppdc) which is also in Main.

  As of

  https://github.com/canonical/ubuntu-mir

  --
  If a new source package contains only code which is already in main (e.g. the 
result of a source package split or rename, or source packages with a version 
in the name), it may not need a full review. Submitting a MIR bug with an 
explanation (but without the full template) or updating/extending on the 
existing old MIR bug and re-opening it by setting it to "NEW" is sufficient.
  --

  This report does not need the full template.

  The original packages (cups-filters and cups) are in Main already for
  more than a decade, so repetition of the original MIR would not be
  useful. cups was already in Ubuntu from the very beginning on and
  therefore probably in Main since the differentiation of Main and
  Universe got introduced.

  The binary packages are named as before (except SONAME of libraries
  being 2 instead of 1 now), binary packages for libppd added. So
  current dependencies and seeding should pull in everything (libppd is
  a library and cups-filters depends on it).

  libfontembed has been discontinued (folded into libcupsfilters, API
  removed) but no package uses it (except the components of cups-filters
  1.x thenselves).

  braille-printer-app will be added to this report (or a new simplified
  MIR report created) as soon as it gets released upstream. Its binary
  package(s) will need to get seeded.

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


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

[Desktop-packages] [Bug 2003259] [NEW] [MIR] libcupsfilters libppd cups-browsed

2023-01-18 Thread Till Kamppeter

Public bug reported:

This is a simplified MIR for the splitting of the cups-filters source
package.

With the second generation (2.x) cups-filters upstream got split into 5
independent component repositories:

- libcupsfilters
- libppd
- cups-filters
- braille-printer-app
- cups-browsed

See

https://openprinting.github.io/cups-filters-Second-Generation-First-
Beta-Release/

braille-printer-app still needs some upstream work for getting released,
the others were already released as 2.0b2.

libcupsfilters, cups-filters, and cups-browsed contain mainly the code
from the former cups-filters (1.x) which is already in Main. libppd
contains code from CUPS (libcups and cups-ppdc) which is also in Main.

As of

https://github.com/canonical/ubuntu-mir

--
If a new source package contains only code which is already in main (e.g. the 
result of a source package split or rename, or source packages with a version 
in the name), it may not need a full review. Submitting a MIR bug with an 
explanation (but without the full template) or updating/extending on the 
existing old MIR bug and re-opening it by setting it to "NEW" is sufficient.
--

This report does not need the full template.

The original packages (cups-filters and cups) are in Main already for
more than a decade, so repetition of the original MIR would not be
useful. cups was already in Ubuntu from the very beginning on and
therefore probably in Main since the differentiation of Main and
Universe got introduced.

The binary packages are named as before (except SONAME of libraries
being 2 instead of 1 now), binary packages for libppd added. So current
dependencies and seeding should pull in everything (libppd is a library
and cups-filters depends on it).

libfontembed has been discontinued (folded into libcupsfilters, API
removed) but no package uses it (except the components of cups-filters
1.x thenselves).

braille-printer-app will be added to this report (or a new simplified
MIR report created) as soon as it gets released upstream. Its binary
package(s) will need to get seeded.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-filters package in Ubuntu:
  New

Bug description:
  This is a simplified MIR for the splitting of the cups-filters source
  package.

  With the second generation (2.x) cups-filters upstream got split into
  5 independent component repositories:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  See

  https://openprinting.github.io/cups-filters-Second-Generation-First-
  Beta-Release/

  braille-printer-app still needs some upstream work for getting
  released, the others were already released as 2.0b2.

  libcupsfilters, cups-filters, and cups-browsed contain mainly the code
  from the former cups-filters (1.x) which is already in Main. libppd
  contains code from CUPS (libcups and cups-ppdc) which is also in Main.

  As of

  https://github.com/canonical/ubuntu-mir

  --
  If a new source package contains only code which is already in main (e.g. the 
result of a source package split or rename, or source packages with a version 
in the name), it may not need a full review. Submitting a MIR bug with an 
explanation (but without the full template) or updating/extending on the 
existing old MIR bug and re-opening it by setting it to "NEW" is sufficient.
  --

  This report does not need the full template.

  The original packages (cups-filters and cups) are in Main already for
  more than a decade, so repetition of the original MIR would not be
  useful. cups was already in Ubuntu from the very beginning on and
  therefore probably in Main since the differentiation of Main and
  Universe got introduced.

  The binary packages are named as before (except SONAME of libraries
  being 2 instead of 1 now), binary packages for libppd added. So
  current dependencies and seeding should pull in everything (libppd is
  a library and cups-filters depends on it).

  libfontembed has been discontinued (folded into libcupsfilters, API
  removed) but no package uses it (except the components of cups-filters
  1.x thenselves).

  braille-printer-app will be added to this report (or a new simplified
  MIR report created) as soon as it gets released upstream. Its binary
  package(s) will need to get seeded.

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


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 Thread Jeremy Bicha

Thank you for reporting this bug and helpinig to make Ubuntu better.

I'm going to collect more data to report this issue upstream since this
issue is blocking us from being able to successfully SRU 43.2 to Ubuntu
22.10.

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

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

** Tags added: regression-release

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-18 Thread beadon

I have blacklisted this now using:

sudo vim /etc/modprobe.d/blacklist-nouveau.conf

adding:

blacklist nouveau
options nouveau modeset=0

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

Title:
  gnome-shell crashes in the kernel at drm_atomic_check_only and the
  kernel says "adding CRTC not allowed without modesets: requested 0x4,
  affected 0x7"

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  GJS crashes - here's the crashdump.  I saw the crash occur after a
  screensaver had been running, and the screens had gone blank.  I
  assume this means they were turned off by the sleep timer.  When I
  worke the machine, I was presented with a prompt, I *quickly* entered
  my login credentials and momentarily saw the desktop and all open
  programs on it.  Then, the screens (3) flickered and I saw the login
  prompt again.   I logged in (again), and all applications had been
  shut down.

  I checked /var/log/syslog and saw the following details -- see (log).
  Uploaded file, and the crashdump.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 20:52:55 2023
  DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
   8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
   nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
  InstallationDate: Installed on 2023-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  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/linux/+bug/2003031/+subscriptions


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

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

2023-01-18 Thread betteropensource

apport information

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

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

Title:
  Nautilus still says "do not unplug the device" even if the writing
  process is finished

Status in nautilus package in Ubuntu:
  New

Bug description:
  After I click on the "unmount" icon next to the USB device in the file
  tree sidebar on Nautilus, the notification appears with the text "do
  not unplug/remove the device".

  The problem is that the notification doesn't go away for several time,
  even if the writing process is already finished, also with that
  notification still visible in the right top corner I can remount the
  USN by clicking its name in Nautilus, use it, and unmount it.

  If I copy something in the USB, the "copying files" popup process
  should finish only if the writing process is really completed (as it
  was in the previous Ubuntu versions...).

  I'm using Ubuntu 22.04.1 LTS.

  apt-cache policy nautilus:
  nautilus:
    Installato: 1:42.2-0ubuntu1
    Candidato:  1:42.2-0ubuntu1
    Tabella versione:
   *** 1:42.2-0ubuntu1 100
  100 /var/lib/dpkg/status
   1:42.0-1ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-10-06 (103 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: nautilus 1:42.2-0ubuntu1 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Tags: jammy third-party-packages wayland-session
  Uname: Linux 5.15.0-56-generic x86_64
  UnreportableReason: Questo non sembra essere un pacchetto ufficiale Ubuntu. 
Riprova dopo aver aggiornato gli indici dei pacchetti disponibili, se non 
funziona rimuovere i relativi pacchetti di terze parti e riprovare.
  UpgradeStatus: Upgraded to jammy on 2022-10-06 (103 days ago)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 2003108] Re: Nautilus still says "do not unplug the device" even if the writing process is finished

2023-01-18 Thread betteropensource

apport information

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

** Description changed:

  After I click on the "unmount" icon next to the USB device in the file
  tree sidebar on Nautilus, the notification appears with the text "do not
  unplug/remove the device".
  
  The problem is that the notification doesn't go away for several time,
  even if the writing process is already finished, also with that
  notification still visible in the right top corner I can remount the USN
  by clicking its name in Nautilus, use it, and unmount it.
  
  If I copy something in the USB, the "copying files" popup process should
  finish only if the writing process is really completed (as it was in the
  previous Ubuntu versions...).
  
  I'm using Ubuntu 22.04.1 LTS.
  
  apt-cache policy nautilus:
  nautilus:
    Installato: 1:42.2-0ubuntu1
    Candidato:  1:42.2-0ubuntu1
    Tabella versione:
   *** 1:42.2-0ubuntu1 100
  100 /var/lib/dpkg/status
   1:42.0-1ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ GsettingsChanges:
+  b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
+  b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
+  b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
+  b'org.gnome.nautilus.window-state' b'maximized' b'true'
+ InstallationDate: Installed on 2022-10-06 (103 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: nautilus 1:42.2-0ubuntu1 [origin: unknown]
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
+ Tags: jammy third-party-packages wayland-session
+ Uname: Linux 5.15.0-56-generic x86_64
+ UnreportableReason: Questo non sembra essere un pacchetto ufficiale Ubuntu. 
Riprova dopo aver aggiornato gli indici dei pacchetti disponibili, se non 
funziona rimuovere i relativi pacchetti di terze parti e riprovare.
+ UpgradeStatus: Upgraded to jammy on 2022-10-06 (103 days ago)
+ UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ usr_lib_nautilus:
+  evince42.3-0ubuntu2
+  file-roller   3.42.0-1
+  nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
+  nautilus-share0.7.3-2ubuntu6

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

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

Title:
  Nautilus still says "do not unplug the device" even if the writing
  process is finished

Status in nautilus package in Ubuntu:
  New

Bug description:
  After I click on the "unmount" icon next to the USB device in the file
  tree sidebar on Nautilus, the notification appears with the text "do
  not unplug/remove the device".

  The problem is that the notification doesn't go away for several time,
  even if the writing process is already finished, also with that
  notification still visible in the right top corner I can remount the
  USN by clicking its name in Nautilus, use it, and unmount it.

  If I copy something in the USB, the "copying files" popup process
  should finish only if the writing process is really completed (as it
  was in the previous Ubuntu versions...).

  I'm using Ubuntu 22.04.1 LTS.

  apt-cache policy nautilus:
  nautilus:
    Installato: 1:42.2-0ubuntu1
    Candidato:  1:42.2-0ubuntu1
    Tabella versione:
   *** 1:42.2-0ubuntu1 100
  100 /var/lib/dpkg/status
   1:42.0-1ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-10-06 (103 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: nautilus 1:42.2-0ubuntu1 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Tags: jammy third-party-packages

[Desktop-packages] [Bug 2003237] Re: Monitor does not turn off after idle timeout is reached

2023-01-18 Thread Sergey Zolotarev

** Attachment added: "Video"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003237/+attachment/5642297/+files/bug.mp4

** Description changed:

  My Screen Blank setting is set to 15 minutes. My Lock Screen settings
  are also set to automatically lock the system after the blank screen
  timeout is reached.
  
  After 15 minutes Ubuntu does lock me out, but the monitor does not power
- off as it's supposed to - the screen is simply black.
+ off as it's supposed to - the screen is simply black. Please see the
+ attached video.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 18 23:48:13 2023
  DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
-Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
+  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
+    Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2018-03-17 (1768 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago)
  dmi.bios.date: 05/29/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4211
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-D
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  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

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

Title:
  Monitor does not turn off after idle timeout is reached

Status in xorg package in Ubuntu:
  New

Bug description:
  My Screen Blank setting is set to 15 minutes. My Lock Screen settings
  are also set to automatically lock the system after the blank screen
  timeout is reached.

  After 15 minutes Ubuntu does lock me out, but the monitor does not
  power off as it's supposed to - the screen is simply black. Please see
  the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 18 23:48:13 2023
  DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev

[Desktop-packages] [Bug 2003237] [NEW] Monitor does not turn off after idle timeout is reached

2023-01-18 Thread Sergey Zolotarev

Public bug reported:

My Screen Blank setting is set to 15 minutes. My Lock Screen settings
are also set to automatically lock the system after the blank screen
timeout is reached.

After 15 minutes Ubuntu does lock me out, but the monitor does not power
off as it's supposed to - the screen is simply black.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 18 23:48:13 2023
DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
InstallationDate: Installed on 2018-03-17 (1768 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago)
dmi.bios.date: 05/29/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4211
dmi.board.asset.tag: Default string
dmi.board.name: H110M-D
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Monitor does not turn off after idle timeout is reached

Status in xorg package in Ubuntu:
  New

Bug description:
  My Screen Blank setting is set to 15 minutes. My Lock Screen settings
  are also set to automatically lock the system after the blank screen
  timeout is reached.

  After 15 minutes Ubuntu does lock me out, but the monitor does not
  power off as it's supposed to - the screen is simply black.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 18 23:48:13 2023
  DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2018-03-17 (1768 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg

[Desktop-packages] [Bug 1999008] Autopkgtest regression report (xorg-server/2:21.1.3-2ubuntu2.6)

2023-01-18 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted xorg-server (2:21.1.3-2ubuntu2.6) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.5-0ubuntu1 (arm64)
imagination/3.6-1build1 (amd64)
soqt/1.6.0+ds1-3 (armhf)
gscan2pdf/2.12.6-1 (amd64)
sasview/5.0.4-1 (armhf)


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#xorg-server

[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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1999008

Title:
  Xorg crashed with SIGABRT in xf86ModeVRefresh() from
  drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from
  xf86ProbeOutputModes() from xf86InitialConfiguration()

Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server source package in Jammy:
  Fix Committed
Status in xorg-server source package in Kinetic:
  Fix Committed
Status in xorg-server source package in Lunar:
  Confirmed

Bug description:
  [Impact]
  The recent SRU'd patch had a bug in it that caused a crash if 
xf86ModeVRefresh returned 0. Amend the patch to fix this.

  [Test case]
  Would need an affected system to test this on, but we haven't been able to 
reproduce this even on an identical system as on one of the reported errors 
(XPS 15 9560).

  [Where things could go wrong]
  This only adds a new check.

  --

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:21.1.4-2ubuntu1.2, the problem page at 
https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 
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/xorg-server/+bug/1999008/+subscriptions


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

[Desktop-packages] [Bug 2003231] [NEW] Replace the Livepatch step by Ubuntu Pro

2023-01-18 Thread Sebastien Bacher

Public bug reported:

* Impact

We want desktop integration with Ubuntu Pro, that will also replace the
custom registration code we had for Livepatch which is integrated with
the new service

* Test case

- log in an Ubuntu session

- ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed)
$ pro status
and `$ pro deteach` if needed

- start the wizard
$ rm ~/.config/gnome-initial-setup-done
$ /usr/libexec/gnome-initial-setup --existing-user

the second step should be 'Enable Ubuntu Pro'

- Let Skip selected and click 'Next'
-> verify that it moves to the next page

- Click 'Previous'
-> it goes back to 'Enable Ubuntu Pro'

- Select 'Enable Ubuntu Pro' and click 'Next'
-> the first option 'Enter code on ubuntu.com/pro/attach' is selected and a PIN 
is display

- go to http://ubuntu.com/pro/attach and enter the PIN
-> the UI should update to display 'Valid token' nex to the PIN

- click 'Next'
a password prompt is displayed which is required to attach the machine
then a spinner is activated while the machine is behind attached to the service
once the registration is done it's moving to the 'Ubuntu Pro Services' page
-> enabled services should list ESM infra/ESM apps/livepatch

- go to a cmdline and do
$ pro status
the machine should be listed as attached

- check the top panel, the livepatch indicator should be displayed

- click 'Next'
-> it moves to the next page 'Help Improve Ubuntu'

go through the remaining wizard steps

* Regression Potential

There could be problems in the UI
The new service could be not working as expected
Strings are new and currently have no translations

Note that the changes aren't available in Lunar since the feature is
going to be provided by the new subiquity based desktop installer going
forward (gnome-inital-setup got ported from GTK3 to GTK4 in Kinetic so
we can't simply use the current changeset until that point)

** Affects: gnome-initial-setup (Ubuntu)
 Importance: High
 Status: In Progress

** Changed in: gnome-initial-setup (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-initial-setup (Ubuntu)
   Status: New => In Progress

** Description changed:

  * Impact
  
- The livepatch service is part of Ubuntu Pro now, the change integrate
- the desktop with the new service
+ We want desktop integration with Ubuntu Pro, that will also replace the
+ custom registration code we had for Livepatch which is integrated with
+ the new service
  
  * Test case
  
  - log in an Ubuntu session
  
  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed)
  $ pro status
  and `$ pro deteach` if needed
  
  - start the wizard
- $ rm ~/.config/gnome-initial-setup-done 
+ $ rm ~/.config/gnome-initial-setup-done
  $ /usr/libexec/gnome-initial-setup --existing-user
  
  the second step should be 'Enable Ubuntu Pro'
  
  - Let Skip selected and click 'Next'
  -> verify that it moves to the next page
  
  - Click 'Previous'
  -> it goes back to 'Enable Ubuntu Pro'
  
  - Select 'Enable Ubuntu Pro' and click 'Next'
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected and a 
PIN is display
  
  - go to http://ubuntu.com/pro/attach and enter the PIN
  -> the UI should update to display 'Valid token' nex to the PIN
  
  - click 'Next'
  a password prompt is displayed which is required to attach the machine
  then a spinner is activated while the machine is behind attached to the 
service
  once the registration is done it's moving to the 'Ubuntu Pro Services' page
  -> enabled services should list ESM infra/ESM apps/livepatch
  
  - go to a cmdline and do
  $ pro status
  the machine should be listed as attached
  
  - check the top panel, the livepatch indicator should be displayed
  
  - click 'Next'
  -> it moves to the next page 'Help Improve Ubuntu'
  
  go through the remaining wizard steps
  
- 
  * Regression Potential
  
  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations
  
  Note that the changes aren't available in Lunar since the feature is
  going to be provided by the new subiquity based desktop installer going
  forward (gnome-inital-setup got ported from GTK3 to GTK4 in Kinetic so
  we can't simply use the current changeset until that point)

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

Title:
  Replace the Livepatch step by Ubuntu Pro

Status in gnome-initial-setup package in Ubuntu:
  In Progress

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - log in an Ubuntu session

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not

[Desktop-packages] [Bug 2000423] Re: "Alternate Characters Key" UI not reflecting current choice

2023-01-18 Thread Gunnar Hjalmarsson

I accomplished the steps in the test plan using gnome-control-
center{,-data} 1:41.7-0ubuntu0.22.04.6 from jammy-proposed. Issue fixed
as expected.

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

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

Title:
  "Alternate Characters Key" UI not reflecting current choice

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  Fix Committed
Status in gnome-control-center source package in Kinetic:
  Won't Fix

Bug description:
  [ Impact ]

  When you set an "Alternate Characters Key", only two of the available
  options — "None" and "Right Alt" — are correctly reflected in the UI.
  If you select some of the other options, the UI tells you that "None"
  is selected. The xkb-options dconf value is correct, though.

  As an example: If I pick Right Ctrl, xkb-options is correctly changed
  to ['lv3:ralt_alt', 'lv3:switch']. So it looks like it parses
  lv3:ralt_alt instead of lv3:switch, and incorrectly concludes that the
  current value is "None".

  [ Test Plan ]

  * Install gnome-control-center from jammy-proposed.

  * Go to Settings -> Keyboard -> Alternate Characters Key
and pick some other option but "None" or "Right Alt".

  * Make sure that the option you selected is correctly
reflected in the UI.

  [ Where problems could occur ]

  This is a targeted fix which only affects a specific control in
  Settings. Considering the current broken state, I'd say that the risk
  is minimal that the change would make it worse.

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


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

[Desktop-packages] [Bug 2003223] Re: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned

2023-01-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Upgrading from 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 18 16:31:31 2023
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2021-08-30 (505 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2003223/+subscriptions


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

[Desktop-packages] [Bug 2003223] [NEW] package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned

2023-01-18 Thread LLego LLaS

Public bug reported:

Upgrading from 20.04 to 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Jan 18 16:31:31 2023
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2021-08-30 (505 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 jammy

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

Title:
  package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Upgrading from 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 18 16:31:31 2023
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2021-08-30 (505 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2003223/+subscriptions


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

[Desktop-packages] [Bug 1799580] Re: Settings made by qasmixer are lost on next reboot

2023-01-18 Thread Franny FooFoo

I have been frustrated by this before on several distro versions.   in
settings, there is the option of "from last session" in the startup
section.  i assume you have this selected, as well as "close to system
tray"  and "show tray icon" in the system tray section.a problem is,
that when you "close to tray" via the close window icon you are not
actually exiting the program, your setup is only written as permanent
when you exit the program. (select "close qasmixer"  from the tray
icon,or CtrlQ from the main qasmixer window,  this writes your
preferences / setup to file.  note :  rebooting doesnt "close qasmixer".
please excuse my overly verbalness, I'm not trying to talk down to you,
'tis my long winded way of preparing for my question to you:   is
qasmixer still running / not being fully shutdown before reboot? perhaps
qasmixers process tree still has branches?

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

Title:
  Settings made by qasmixer are lost on next reboot

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  I use qasmixer to set the "Synth" volume to full, on my SoundBlaster
  Live sound-card.

  On prior levels of Ubuntu (through 18.04), any settings I make are
  preserved over reboots.

  On the latest level of Ubuntu (18.10) the settings are effective only
  as long as the system is running.  The next time I reboot, the
  settings are gone, and I have to use qasmixer to set them all over
  again.

  I expected the settings made by qasmixer to be preserved on the next
  reboot, as with past levels of Ubuntu.

  The settings made by qasmixer are not preserved over a reboot on
  Ubuntu 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: qasmixer 0.21.0-1.1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: LXQt
  Date: Tue Oct 23 14:59:06 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release i386 
(20181017.2)
  SourcePackage: qastools
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

Yes, it is. I tested it in a VM, and can reproduce it.

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Merge proposal linked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435960

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  In Progress

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

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

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  In Progress

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 Thread Jeremy Bicha

Sergio, you mean that it looks like this bug was triggered when your
system updated from mutter 43.0-1ubuntu5 to
https://launchpad.net/ubuntu/+source/mutter/43.2-4ubuntu1 right?

** Summary changed:

- Transparency ignored in full screen mode
+ gnome-terminal transparency ignored in full screen mode

** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu)

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Merge proposal unlinked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

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

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Merge proposal linked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435957

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Merge proposal linked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  In Progress
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Description changed:

  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported
  
  [Impact]
  This affects users using applications that have docked windows
  
  [Test Case]
  
  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash
+ 
+ * Fix: install fix from ppa: 
+ * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
+ * sudo apt update
+ * sudo reboot # or alternatively, restart display manager
+ * run python3 Untitled.py
+ * Undock one of the application's child windows
+ * Minimize main window
  * Expectation: it should not crash and the application should be minimized.
  
  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.
  
  -
  
  Bug Version: 1:3.36.1-1 / 1:3.44.0-1
  
  Metacity is running without the composite manager.
  
  Users cannot minimize an application with an undocked child window
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  New
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash

  * Fix: install fix from ppa: 
  * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0
  * sudo apt update
  * sudo reboot # or alternatively, restart display manager
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003192] [NEW] thunderbird snap does not work without x11 interface connected

2023-01-18 Thread A333

Public bug reported:

When I disconnect the thunderbird from the x11 interface thunderbird
crashes saying it can not find the wayland socket. If I add a link to
the wayland socket inside the container thunderbird works fine. That is
on kubuntu 22.04 in a plasma/wayland session, MOZ_ENABLE_WAYLAND=1 is
set on the host and in the container as well.

This also probably means that the thunderbird snap actually never uses
native wayland and falls back to xwayland (because the wayland socket
can not be found).

This unintended use of xwayland could be construed as a security issue,
but someone who mistrusts snaps using x11 (like me) will remove the
permission which leads to failure instead of a security issue.

$ snap run thunderbird   ## BROKEN
...
[GFX1-]: glxtest: libpci missing
[GFX1-]: glxtest: Could not connect to wayland socket
[GFX1-]: No GPUs detected via PCI

(thunderbird:103861): Gtk-WARNING **: 12:37:14.162: cannot open display: :1
ExceptionHandler::GenerateDump cloned child 103976
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

$ snap run --shell thunderbird   ## FIXING IT
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

user@user-mycomputer:/$ ln -s /run/user/1000/wayland-0 $XDG_RUNTIME_DIR/ ; exit
$ snap run thunderbird   ## NOW IT WORKS

$ lsb_release -rd   ## UBUNTU VERSION
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ snap interfaces thunderbird  ## SNAP CONFIGURATION
Slot Plug
gnome-3-38-2004:gnome-3-38-2004  thunderbird
gtk-common-themes:gtk-3-themes   thunderbird
gtk-common-themes:icon-themesthunderbird
gtk-common-themes:sound-themes   thunderbird
:audio-playback  thunderbird
:browser-support thunderbird:browser-sandbox
:cups-controlthunderbird
:desktop thunderbird
:desktop-legacy  thunderbird
:gsettings   thunderbird
:homethunderbird
:network thunderbird
:opengl  thunderbird
:system-filesthunderbird:etc-thunderbird-policies
:wayland thunderbird
thunderbird:dbus-daemon  -
-thunderbird:avahi-observe
-thunderbird:camera
-thunderbird:gpg-keys
-thunderbird:network-control
-thunderbird:removable-media
-thunderbird:u2f-devices
-thunderbird:x11

$ snap info thunderbird  ## THUNDERBIRD SNAP VERSION
...
installed:  102.7.0-1(288) 106MB -

$ snap --version  ## SNAPD etc VERSION
snap2.58
snapd   2.58
series  16
ubuntu  22.04
kernel  5.15.0-57-generic

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

** Description changed:

- When I disconnect the thunderbird from the x11 interface, thunderbird
- crashes saying it cant find the wayland socket. If I add a link to the
- wayland socket inside the container, thunderbird works fine. That is on
- ubuntu 22.04.
+ When I disconnect the thunderbird from the x11 interface thunderbird
+ crashes saying it can not find the wayland socket. If I add a link to
+ the wayland socket inside the container thunderbird works fine. That is
+ on ubuntu 22.04.
  
  This also probably means that the thunderbird snap actually never uses
  native wayland and falls back to xwayland (because the wayland socket
  can not be found).
  
  This unintended use of xwayland could be construed as a security issue,
  but someone who mistrusts snaps using x11 (like me) will remove the
  permission which leads to failure instead of a security issue.
- 
  
  $ snap run thunderbird   ## BROKEN
  ...
  [GFX1-]: glxtest: libpci missing
  [GFX1-]: glxtest: Could not connect to wayland socket
  [GFX1-]: No GPUs detected via PCI
  
  (thunderbird:103861): Gtk-WARNING **: 12:37:14.162: cannot open display: :1
  ExceptionHandler::GenerateDump cloned child 103976
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  
- 
  $ snap run --shell thunderbird   ## FIXING IT
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.
  
  user@user-mycomputer:/$ ln -s /run/user/1000/wayland-0 $XDG_RUNTIME_DIR/ ; 
exit
  $ snap run thunderbird   ## NOW IT WORKS
  
- 
  $ lsb_release -rd   ## UBUNTU VERSION
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
- 
  
  $ snap interfaces thunderbird  ## SNAP CONFIGURATION
  Slot Plug
  gnome-3-38-2004:gnome-3-38-2004  thunderbird
  gtk-common-themes:gtk-3-themes   thunderbird

[Desktop-packages] [Bug 2003184] [NEW] gtk-key-theme Emacs has no effect in 22.10

2023-01-18 Thread Rovanion

Public bug reported:

Setting the key binding theme for GTK to Emacs through the usual method
of running

```
gsettings set org.gnome.desktop.interface gtk-key-theme Emacs
```

has no effect. Opening Nautilus, typing a word, and then pressing ctrl-a
will select the whole word instead of moving the caret to the beginning
of the line. The same behaviour can be observed in other GTK inputs such
as the search field of Gnome Shell.

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


└$ gnome-shell --version
GNOME Shell 43.1
```

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

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

Title:
  gtk-key-theme Emacs has no effect in 22.10

Status in gtk4 package in Ubuntu:
  New

Bug description:
  Setting the key binding theme for GTK to Emacs through the usual
  method of running

  ```
  gsettings set org.gnome.desktop.interface gtk-key-theme Emacs
  ```

  has no effect. Opening Nautilus, typing a word, and then pressing
  ctrl-a will select the whole word instead of moving the caret to the
  beginning of the line. The same behaviour can be observed in other GTK
  inputs such as the search field of Gnome Shell.

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

  
  └$ gnome-shell --version
  GNOME Shell 43.1
  ```

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


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

[Desktop-packages] [Bug 2003104] Re: Transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

It's not random, at least in my system. Also, the tricks in that bug
report don't work: I tried changing the transparency value, disabling
and enabling again, but no dice.

If I had to bet, I would say that the problem is in the fullscreen
redirection to avoid composition overload with games... but I don't know
if Wayland has that...

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

Title:
Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
Confirmed

Bug description:
Ubuntu 23.04 running wayland
gnome-terminal 3.46.7-1ubuntu1

It seems that tranparency was accidentally removed, and then re-added via

https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

However, maybe something was missed with regards to full screen.

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

[Desktop-packages] [Bug 2003104] Re: Transparency ignored in full screen mode

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

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

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

Title:
  Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 2003104] Re: Transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

Confirmed that this happens when libmutter/mutter-common are updated to
version 11.

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

Title:
  Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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


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

[Desktop-packages] [Bug 1968588] Re: Cannot create or add VPN in connection editor

2023-01-18 Thread Bug Watch Updater

** Changed in: network-manager-applet
   Status: New => Fix Released

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

Title:
  Cannot create or add VPN in connection editor

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Jammy:
  Confirmed
Status in network-manager-vpnc source package in Jammy:
  Confirmed

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

** Description changed:

  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
- * The fix is already included in 3.46.0 version: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
- * Focal(3.36.1) and Jammy (3.44.0) needs the fix to be backported
+ * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
+ * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
+ * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
+ * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported
  
  [Impact]
  This affects users using applications that have docked windows
  
  [Test Case]
  
  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
- * Result: Metacity will crash 
+ * Result: Metacity will crash
  * Expectation: it should not crash and the application should be minimized.
  
  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.
  
  -
  
  Bug Version: 1:3.36.1-1 / 1:3.44.0-1
  
  Metacity is running without the composite manager.
  
  Users cannot minimize an application with an undocked child window
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  New
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child

Reproducer script:

** Attachment added: "Untitled.py"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5642194/+files/Untitled.py

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  New
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


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

[Desktop-packages] [Bug 2003176] [NEW] SRU: metacity crashes while minimizing a windows that has undocked child

Public bug reported:

[General information about the SRU]
* It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
* The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
* The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
* The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
* Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

[Impact]
This affects users using applications that have docked windows

[Test Case]

* Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
* Start a graphical session with metacity
* run python3 Untitled.py
* Undock one of the application's child windows
* Minimize main window
* Result: Metacity will crash
* Expectation: it should not crash and the application should be minimized.

[Regression Potential]
The fix is small in size and localized, it should not cause any regressions.

-

Bug Version: 1:3.36.1-1 / 1:3.44.0-1

Metacity is running without the composite manager.

Users cannot minimize an application with an undocked child window

ProblemType: Bug
DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
Package: metacity 1:3.36.1-1 / 1:3.44.0-1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64

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

** Affects: metacity (Ubuntu Focal)
 Importance: Undecided
 Assignee: Mustafa Kemal Gilor (mustafakemalgilor)
 Status: New

** Affects: metacity (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Mustafa Kemal Gilor (mustafakemalgilor)
 Status: New

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

** Also affects: metacity (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: metacity (Ubuntu Focal)
 Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor)

** Changed in: metacity (Ubuntu Jammy)
 Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor)

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

Title:
  SRU: metacity crashes while minimizing a windows that has undocked
  child

Status in metacity package in Ubuntu:
  New
Status in metacity source package in Focal:
  New
Status in metacity source package in Jammy:
  New

Bug description:
  [General information about the SRU]
  * It includes the fix for the bug 
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
  * The fix is already included in 3.46.0 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
  * The reproducer also revealed another issue with docked windows, undocked 
windows are not being restored after parent window is minimized and restored
  * The fix for restore is included in 3.46.1 release: 
https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9
  * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported

  [Impact]
  This affects users using applications that have docked windows

  [Test Case]

  * Install gnome-session-flashback (metacity) and reproducer's dependencies 
`sudo apt install lightdm gnome-session-flashback pyside2-tools 
python3-pyside2.qtwidgets`
  * Start a graphical session with metacity
  * run python3 Untitled.py
  * Undock one of the application's child windows
  * Minimize main window
  * Result: Metacity will crash
  * Expectation: it should not crash and the application should be minimized.

  [Regression Potential]
  The fix is small in size and localized, it should not cause any regressions.

  -

  Bug Version: 1:3.36.1-1 / 1:3.44.0-1

  Metacity is running without the composite manager.

  Users cannot minimize an application with an undocked child window

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04 / Ubuntu 22.04
  Package: metacity 1:3.36.1-1 / 1:3.44.0-1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to :

[Desktop-packages] [Bug 1991777] Re: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older (than supported) kernels

** Summary changed:

- gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property 
(GAMMA_LUT) not found] on Alder Lake with older kernels
+ gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property 
(GAMMA_LUT) not found] on Alder Lake with older (than supported) kernels

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

** Changed in: mutter (Ubuntu)
   Status: New => 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/1991777

Title:
  gnome-shell deadlocked on startup [Failed to post KMS update: CRTC
  property (GAMMA_LUT) not found] on Alder Lake with older (than
  supported) kernels

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  My Ubuntu session is currently impossible to launch. Upon trying, I
  get a couple ~blank displays, sometimes along with a cursor at the
  position it was in GDM.

  Only way out is `chvt …`, or killing gnome-shell, over SSH.

  "Ubuntu on Xorg" works fine. The wayland session does work for a test
  user as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct  5 11:47:11 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (34 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  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/mutter/+bug/1991777/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Answer from email to comment #57:

It appears your CPU/GPU (i7-1280P) is too new for that old kernel
(5.14.0-1055-oem). And so you are hitting this bug:
https://launchpad.net/bugs/1991777

But the solution is simple: Just install 22.10 and don't downgrade the
kernel. It should be kernel version 5.19 when Ubuntu 22.10 is installed
properly.

-- 
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:
  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 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.

  [ 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 1991777] Re: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels

If atomic KMS is disabled then the same bug may present as:

Failed to post KMS update:
drmModeCrtcSetGamma on CRTC 80 failed: Function not implemented

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

Title:
  gnome-shell deadlocked on startup [Failed to post KMS update: CRTC
  property (GAMMA_LUT) not found] on Alder Lake with older kernels

Status in mutter package in Ubuntu:
  New

Bug description:
  My Ubuntu session is currently impossible to launch. Upon trying, I
  get a couple ~blank displays, sometimes along with a cursor at the
  position it was in GDM.

  Only way out is `chvt …`, or killing gnome-shell, over SSH.

  "Ubuntu on Xorg" works fine. The wayland session does work for a test
  user as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct  5 11:47:11 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-31 (34 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  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/mutter/+bug/1991777/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Please collect a log from the previous boot where it froze:

  journalctl -b-1 > prevboot.txt

and create a new bug with that file attached.

Also check for /var/crash files and create new bugs for each using
'ubuntu-bug'.

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

Title:
  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 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.

  [ 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 2003168] Re: SIdebar, files gets unresponsive after unlocking locked season.