date:20230103

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

** Summary changed:

- Xorg crash
+ Crash

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  It is the 10th time the Ubuntu just hang and restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec 17 12:38:26 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0]
  MachineType: ASUSTeK COMPUTER INC. UX310UAK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX310UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX310UAK
  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.:bvrUX310UAK.312:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX310UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://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 2000022] Re: app icon highlighting is glitched when a file is opened in the file explorer

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

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


** This bug has been marked a duplicate of bug 1965123
   Active launchers area pixels (corners) missing

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

Title:
  app icon highlighting is glitched when a file is opened in the file
  explorer

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

Bug description:
  When I open a text file in Files with an application that has not been
  added to favorites, the app highlighting (white rounded rectangle
  around the icon) is glitched.

  For example, I have attached a screenshot showing the app highlighting
  when I open a text file from files without having 'gedit' added to
  favorites. The gedit icon in the dock is glitched. Other app icons
  will also glitch in this way.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 18 17:49:46 2022
  InstallationDate: Installed on 2022-12-18 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 2001594] [NEW] Mutter crashes on xdg_activation.activate request

2023-01-03 Thread Andrei Cherniaev

Public bug reported:

Please allow users to upgrade Mutter because of bug. See
https://gitlab.gnome.org/GNOME/mutter/-/issues/2486

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

** Description changed:

- Please allow users to upgrade Mutter to because of bug. See
+ Please allow users to upgrade Mutter because of bug. See
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2486

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

Title:
  Mutter crashes on xdg_activation.activate request

Status in mutter package in Ubuntu:
  New

Bug description:
  Please allow users to upgrade Mutter because of bug. See
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2486

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


-- 
Mailing list: https://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 1999896] Re: cpu utilisation too high

Please open a terminal window and run 'top'. What process is using the
most CPU?

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

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

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

Title:
  cpu utilisation too high

Status in Ubuntu:
  Incomplete

Bug description:
  Im running Ubuntu 20.04(With KDE desktop environment) on a dell inspiron 5378.
   Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.8
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.15.0-56-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Pentium® CPU 4415U @ 2.30GHz
  Memory: 3.6 GiB of RAM

  The ram usage is fine, i have no issues on that end my main concern is
  how quickly the cpu goes up to 100% utilistation in system monitor
  after opening the file manager and a few firefox tabs.

  If anyone can advise on the matter i would be more than grateful.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Dec 16 16:07:45 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0740]
  InstallationDate: Installed on 2022-11-15 (30 days ago)
  InstallationMedia: Kubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 
(20220831)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2494 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 13-5378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=6580df22-8c81-4fb7-bbcf-f074c7b6efc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.36.0
  dmi.board.name: 0WFM43
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.36.0:bd12/15/2021:br1.36:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn0WFM43:rvrA00:cvnDellInc.:ct9:cvr:sku0740:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5378
  dmi.product.sku: 0740
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: https://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 1999939] Re: The conky display stopped working after recent update

** Package changed: xorg (Ubuntu) => conky (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/139

Title:
  The conky display stopped working after recent update

Status in conky package in Ubuntu:
  New

Bug description:
  The conky display stopped working after recent update, see error message:
  X Error of failed request:  BadWindow (invalid Window parameter)
Major opcode of failed request:  20 (X_GetProperty)
Resource id in failed request:  0x201
Serial number of failed request:  105
Current serial number in output stream:  105

  I attach the .conkyrc file

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec 16 15:32:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-10-28 (1145 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191026)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=9dfdf604-fe7f-4a57-b5c2-d1f354795add ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: https://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 1999578] Re: Bursts of high CPU usage after triggering overview

Actually really bursty CPU usage by gnome-shell might be garbage
collection, which will be improved in
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2377

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

Title:
  Bursts of high CPU usage after triggering overview

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

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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 2000024] Re: Font alignment/search bar size issue when using scaling factor > 1

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

** This bug has been marked a duplicate of bug 1999320
   Font alignment issue in search bar when using scaling factor > 1

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

Title:
  Font alignment/search bar size issue when using scaling factor > 1

Status in xorg package in Ubuntu:
  New

Bug description:
  When using 'gsettings set org.gnome.desktop.interface text-scaling-
  factor' command to set the scaling factor to something greater than 1,
  the text gets misaligned in the search bar, which seems to be too
  small (shown in an attachment here).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 18 18:07:13 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3090] [1043:87b3]
  InstallationDate: Installed on 2022-12-18 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=fc0c0197-bcc1-4eb2-abf4-af87b54ca0e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2022
  dmi.bios.release: 22.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z690-E GAMING WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2204:bd11/30/2022:br22.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-EGAMINGWIFI:rvrRev1.xx: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: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg/+bug/224/+subscriptions


-- 
Mailing list: https://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 1999833] Re: gnome-shell update should not request a reboot if it is not running

Logging out and in again should be enough. Although that wouldn't be
true where the login screen (also hosted by gnome-shell) was still
running during your desktop login but these days the login screen is
stopped and restarted on demand. So indeed logging out and in again
should be sufficient if you were running GNOME. Or do nothing at all if
you're logged into KDE (providing the login screen's gnome-shell
instance is not still running).

So you're right, but it can be complicated.


** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  gnome-shell update should not request a reboot if it is not running

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  The gnome-shell package requests a reboot even if no GNOME desktop is
  running.

  This reminds me too much of how Microsoft Windows only knows about
  itself. Windows assumes it is the only OS and overwrites GRUB, and now
  gnome-shell is assuming it's the only desktop environment (even
  ignoring the fact that Linux always has TTY too) and requests that
  everyone reboot even if just its users need to relog. It's also too
  much like how Windows will tell the user to restart their computer
  when just a single service needs to be restarted, while gnome-shell is
  now also telling the user to restart their computer if the just need
  to relog, possibly with a `killall5`.

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 43.1-0ubuntu1
Candidate: 43.1-0ubuntu1
Version table:
   *** 43.1-0ubuntu1 500 (phased 80%)
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu 
kinetic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   43.0-1ubuntu2 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main 
amd64 Packages

  # Expected Behavior

  There should not be a reboot notification in my KDE tray after running
  apt upgrade. No gnome desktop is logged in.

  # Actual Behavior

  There is a needless reboot notification in my KDE tray.
  `/var/run/reboot-required` exists.

  $ cat /var/run/reboot-required.pkgs 
  gnome-shell

  # Analysis

  In gnome-shell_43.1-0ubuntu1_amd64.deb there is control.tar.zst which has 
postinst. In that script there is not check for whether a gnome-session is 
running. Perhaps a `if ps -ef | grep -q gnome-shell; then` could be added. Even 
Firefox only tells you to restart only running instances.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DisplayManager:
   
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  PackageArchitecture: amd64
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  Tags: third-party-packages kinetic wayland-session
  Uname: Linux 6.0.12-surface x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (77 days ago)
  UserGroups: dialout docker kvm lpadmin lxd plugdev sudo systemd-journal video 
wireshark
  _MarkForUpload: True

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


-- 
Mailing list: https://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 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] ERROR

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

"drmModeAtomicCommit: Invalid argument" is also being tracked in bug
1968040 although it might have multiple causes.

"clutter_frame_clock_notify_presented: code should not be reached" is
being tracked in bug 1967707 and I think that's the main issue here.

** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: jammy nvidia nvidia-wayland wayland wayland-session

** This bug has been marked a duplicate of bug 1967707
   Nvidia Wayland sessions sometimes flood the log with 
"clutter_frame_clock_notify_presented: code should not be reached"

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

Title:
  external screen freeze during display setting in wayland session:
  kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*

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

Bug description:
  - ubuntu 22.04.1
  - 5.15.0-56-generic
  - mutter 42.5-0ubuntu1
  - using gdm3
  - nvidia Driver Version: 525.60.11 (nvidia-driver-525)
  - prime select to on-demand
  - 1 external display, 1 internal LCD

  ```
  Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting.
  Added device '/dev/dri/card0' (i915) using atomic mode setting.
  Dec 15 22:13:34  gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1'
  Dec 15 22:13:34  gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0'
  Dec 15 22:13:34  gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as 
primary
  Dec 15 22:13:35  gnome-shell[3203]: Secondary GPU initialization failed 
(Failed to create gbm_surface: No such file or directory). Falling back to 
GPU-less >
  Dec 15 22:13:35  gnome-shell[3203]: Using public X11 display :1, (using :2 
for managed services)
  Dec 15 22:13:35  gnome-shell[3203]: Using Wayland display name 'wayland-0'
  ```

  0. open a terminal `journalctl -f`
  1. Open the display setting, switch to join displays, choose external display 
as primary.
  2. try to change some settings like scale, position of the screen, refresh 
rate, etc, then applay
  3. repeat above step several times

  After 2 changes the external screen freeze forever. Internal screen is still 
responsible. On each `Apply` The journal recorded an kernel error about 
nvidia_drm and flooded with clutter-frame-clock error.
  ```
  Dec 15 22:18:52  gnome-shell[3203]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Dec 15 22:18:52  gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: 
Invalid argument
  Dec 15 22:19:25  gnome-shell[3203]: Failed to allocate onscreen framebuffer 
for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
  Dec 15 22:19:25  kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] 
*ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 
0x5>
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Dec 15 22:19:26  gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: 
Invalid argument
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  Dec 15 22:19:26  gnome-shell[3203]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  ```
  one may ignore the drmModeAtomicCommit warning, they are always flooding the 
log (though it may be related issue)

  The clutter warning then flood the log forever till reboot.

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


-- 
Mailing list:

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2023-01-03 Thread William Maddox

Inspired by BloodyIron's comments above, I investigated this issue and
was able to develop a patch that solves this problem for my use case:
browsing NAS devices running TrueNAS and OpenMediaVault.  It appears
that the gvfsd-smb-browse process is left in a bad state after
attempting to mount a workgroup, which occurs either when attempting to
open an URL like smb://WORKGROUP/ or during network discovery in gvfsd-
network.  My patch simply disables workgroup discovery/browsing
functionality, leaving *browsing* functionality intact for servers that
are *discovered* via DNS-SD (mDNS). This does not address the issue of
discovering Windows 10 servers that advertise themselves only via WS-
Discovery, but appears to work fine for devices that advertise
themselves using mDNS, allowing those devices to be successfully
browsed.

I note that workgroups are an obsolete concept in a post-NT1 (post-SMB1)
world, so the offending code should eventually just be yanked out, along
with the addition of support for WS-Discovery in Linux.  My patch does
not address the root cause, as whatever is going wrong while attempting
to mount a workgroup should result in a recoverable error.  I traced
gvfsbackendsmbbrowse.c:do_mount() up to the point at which
smbc_opendir() is called without any surprises, whereupon things went
south.  I did not investigate any further, but if I were to do so, I'd
be inclined to take a look for an unreleased lock.

** Patch added: "Disable broken workgroup discovery/browsing"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107/+attachment/5639041/+files/smb-browse-patch.diff

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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


-- 
Mailing list: https://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 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

2023-01-03 Thread Gunnar Hjalmarsson

A long shot: Install gnome-session:

sudo apt install gnome-session

log in to a "vanilla" GNOME session and see if you notice a difference
with respect to the endeavour behavior.

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

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


-- 
Mailing list: https://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 1995199] Re: Renaming home folders corrupts side panel behavior

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Renaming home folders corrupts side panel behavior

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Hi!

  Renamed home folder is not synchronized with side panel.
  So, side panel's link does not work after renaming home folders.

  Expected, opening renamed folder from side panel.
  Due to lack of customization of side panel, links can not
  be changed to the new renamed location.

  It is not only my opinion that the side panel must have more
  customization features, including resizing and disabling it. 

  Ubuntu 22.10
  5.19.0-23-generic

  nautilus-data/kinetic,kinetic,now 1:43.0-1ubuntu1 all [installed,automatic]
  nautilus-extension-gnome-terminal/kinetic,now 3.46.2-1ubuntu1 amd64 
[installed,automatic]
  nautilus/kinetic,now 1:43.0-1ubuntu1 amd64 [installed,automatic]

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


-- 
Mailing list: https://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 2001580] [NEW] Thunderbird 102.6.0-2 snap cant save files

2023-01-03 Thread Vladimir I

Public bug reported:

Can't save pdf file from attachment

Ubuntu 22.04.1 LTS

thunderbird102.6.0-2 281latest/stable 
snap-id:  k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460

with terminal output (no reaction in GUI)

(thunderbird:24618): Gtk-WARNING **: 09:35:43.338: Can't open portal
file chooser: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.portal.Desktop was not provided by any .service
files

installed xdg-desktop-portal-gtk and get:

(thunderbird:24618): Gtk-WARNING **: 09:38:40.128: Can't open portal
file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No
such interface “org.freedesktop.portal.FileChooser” on object at path
/org/freedesktop/portal/desktop

pretty similar to https://forum.snapcraft.io/t/firefox-snap-77-cannot-
download-anything/18167 bug

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

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

Title:
  Thunderbird 102.6.0-2 snap cant save files

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Can't save pdf file from attachment

  Ubuntu 22.04.1 LTS

  thunderbird102.6.0-2 281latest/stable 
  snap-id:  k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460

  with terminal output (no reaction in GUI)

  (thunderbird:24618): Gtk-WARNING **: 09:35:43.338: Can't open portal
  file chooser: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
  The name org.freedesktop.portal.Desktop was not provided by any
  .service files

  installed xdg-desktop-portal-gtk and get:

  (thunderbird:24618): Gtk-WARNING **: 09:38:40.128: Can't open portal
  file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No
  such interface “org.freedesktop.portal.FileChooser” on object at path
  /org/freedesktop/portal/desktop

  pretty similar to https://forum.snapcraft.io/t/firefox-snap-77-cannot-
  download-anything/18167 bug

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


-- 
Mailing list: https://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 1921398] Re: No dns resolution after closing a vpn/sstp connection

2023-01-03 Thread Eivind Naess

Not for Ubuntu, however the upstream pppd package from debian has the
following in the debian/extra/ip-up.d/usepeerdns

```
case "$6" in
  nm-*-service-*|/org/freedesktop/NetworkManager/PPP/*)
# NetworkManager handles it
exit 0
;;
esac
```

This is only a Ubuntu specific issue.

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

Title:
  No dns resolution after closing a vpn/sstp connection

Status in ppp package in Ubuntu:
  Confirmed

Bug description:

  The fix for the following issue closes it for nm-pptp-service-*
  connections, however; it is still a problem for users using network-
  manager-sstp.

  You use network-manager-sstp, connect to your VPN server. Then
  disconnect and you now can't lookup any hostnames.

  
  Original problem
  #1778946 No dns resolution after closing a vpn/pptp connection

  This is still a problem for sstp users.

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


-- 
Mailing list: https://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 2000240] Re: Unable to switch GDM User -

2023-01-03 Thread Kai-Heng Feng

** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Unable to switch GDM User -

Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  Hello

  since upgrading to 22.04.1 LTS it's no longer possible to switch users
  from graphical menu.

  The behaviour is as follows:
  - from user A session, click on System menu and then Change user
  - the user list is displayed
  - clicking on another user (B) then I'm prompted for the password
  - when I enter the password, there is a lag, and then the user list is 
displayed again

  I tried alternatives
  - locking the A session before trying to open B session > no success
  - using the Wayland logging possiblity > no success

  Using journalctl wit support from experienced Ubunteros I tried to
  find issues and apparently there is an error related to the problem (I
  do not know if it's the cause or the consequence)

  sept. 04 17:55:12 pcmail gdm3[1002]: GLib-GObject:
  g_object_set_is_valid_property: object class 'GdmLocalDisplay' has no
  property named 'supported-session-tyes'

  there has also been a problem with apparmor (several messages logged)

  sept. 04 17:55:21 pcmail audit[746]: USER_AVC pid=746 uid=103 auid=4294967295 
ses=4294967295 subj=? msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/login1" interface=>
exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olmaillard  18811 F pulseaudio
   /dev/snd/controlC1:  olmaillard  18811 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-10-01 (445 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (125 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/11/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B360M-C
  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.:bvr2603:bd10/11/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olmaillard  18811 F pulseaudio
   /dev/snd/controlC1:  olmaillard  18811 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-10-01 (445 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet

[Desktop-packages] [Bug 2000240] [NEW] Unable to switch GDM User -

You have been subscribed to a public bug:

Hello

since upgrading to 22.04.1 LTS it's no longer possible to switch users
from graphical menu.

The behaviour is as follows:
- from user A session, click on System menu and then Change user
- the user list is displayed
- clicking on another user (B) then I'm prompted for the password
- when I enter the password, there is a lag, and then the user list is 
displayed again

I tried alternatives
- locking the A session before trying to open B session > no success
- using the Wayland logging possiblity > no success

Using journalctl wit support from experienced Ubunteros I tried to find
issues and apparently there is an error related to the problem (I do not
know if it's the cause or the consequence)

sept. 04 17:55:12 pcmail gdm3[1002]: GLib-GObject:
g_object_set_is_valid_property: object class 'GdmLocalDisplay' has no
property named 'supported-session-tyes'

there has also been a problem with apparmor (several messages logged)

sept. 04 17:55:21 pcmail audit[746]: USER_AVC pid=746 uid=103 auid=4294967295 
ses=4294967295 subj=? msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/login1" interface=>
  exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  olmaillard  18811 F pulseaudio
 /dev/snd/controlC1:  olmaillard  18811 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-10-01 (445 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-56-generic N/A
 linux-backports-modules-5.15.0-56-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.7
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags:  jammy
Uname: Linux 5.15.0-56-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-08-17 (125 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/11/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B360M-C
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.:bvr2603:bd10/11/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  olmaillard  18811 F pulseaudio
 /dev/snd/controlC1:  olmaillard  18811 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-10-01 (445 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-56-generic N/A
 linux-backports-modules-5.15.0-56-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.7
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags:  jammy
Uname: Linux 5.15.0-56-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-08-17 (125 days ago)
UserGroups: adm cdrom dip

[Desktop-packages] [Bug 2000098] Re: I am not sure if i am right

It looks like the NVIDIA-525 driver is correctly installed and working.
What makes you think otherwise?

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

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

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

Title:
  I am not sure if i am right

Status in Ubuntu:
  Incomplete

Bug description:
  I am not sure what i have done but the driver seems wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 
23:04:03 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] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 20 00:56:43 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.60.11, 5.19.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 
1660 SUPER] [1462:8d94]
  InstallationDate: Installed on 2022-12-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Gigabyte Technology Co., Ltd. B250M-Gaming 3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=847b2ef5-caec-47e0-a734-a25d0e008f1a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/10/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnB250M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B250M-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.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/ubuntu/+bug/298/+subscriptions


-- 
Mailing list: https://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 1999629] Re: xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older

** Tags added: kinetic

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

Title:
  xorg-core package does not provide xorg-video-abi version 24 ( it is
  version 25) under ubuntu 22 and later, makes it impossible to install
  cuda 10.2 or older

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  xserver-xorg-core:
    Installed: 2:21.1.4-2ubuntu1
    Candidate: 2:21.1.4-2ubuntu1
    Version table:
   *** 2:21.1.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't
  because the only compatible mix of CUDA and drivers results in a
  virtual dependency problem.

  apparently the problem is the lack the xorg-video-abi-24 in the
  xserver-xorg-core package

  as the grep command shows, only the video-abi-25 is provided in ubuntu
  22 , but in order to install cuda 10.2 (or older), the version 24 is
  needed.

  $ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
  Package: xserver-xorg-core
  Version: 2:21.1.3-2ubuntu2.5
  Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
  Package: xserver-xorg-core
  Version: 2:21.1.3-2ubuntu2
  Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting

  
  installing cuda 10.2 or older will give you this error:

   xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
    xorg-video-abi-23 but it is not 
installable or
    xorg-video-abi-20 but it is not 
installable or
    xorg-video-abi-19 but it is not 
installable or
    xorg-video-abi-18 but it is not 
installable or
    xorg-video-abi-15 but it is not 
installable or
    xorg-video-abi-14 but it is not 
installable or
    xorg-video-abi-13 but it is not 
installable or
    xorg-video-abi-12 but it is not 
installable or
    xorg-video-abi-11 but it is not 
installable or
    xorg-video-abi-10 but it is not 
installable or
    xorg-video-abi-8 but it is not 
installable or
    xorg-video-abi-6.0 but it is not 
installable

  According to my research this package is the provider in focal
  https://packages.ubuntu.com/focal/xorg-video-abi-24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1999629/+subscriptions


-- 
Mailing list: https://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 1999501] Re: Login Loop

It should be possible to log into a text console by pressing Ctrl+Alt+F4
for example. But per comment #2 if you're not using Ubuntu anymore then
we don't need to keep this bug open.


** Tags added: jammy

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  Login Loop

Status in Ubuntu:
  Won't Fix

Bug description:
  As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine
  using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the
  operating system gets stuck on the login page, even after inputing the
  correct  password.

  Some specs of the machine in question:

  --
  System Information
  --
   Machine name: ---
 Machine Id: ---
   Operating System: Windows 10 Home 64-bit (10.0, Build 19044) 
(19041.vb_release.191206-1406)
   Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
   System Model: ROG Zephyrus G15 GA503QR_GA503QR
   BIOS: GA503QR.413 (type: UEFI)
  Processor: AMD Ryzen 9 5900HS with Radeon Graphics 
(16 CPUs), ~3.3GHz
 Memory: 16384MB RAM
Available OS Memory: 15776MB RAM
  Page File: 12722MB used, 7405MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
   User DPI Setting: 96 DPI (100 percent)
 System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
   Miracast: Available, with HDCP
  Microsoft Graphics Hybrid: Supported

  ---
  Display Devices
  ---
 Card name: AMD Radeon(TM) Graphics
  Manufacturer: Advanced Micro Devices, Inc.
 Chip type: AMD Radeon Graphics Processor (0x1638)
Display Memory: 8384 MB
  Dedicated Memory: 496 MB
 Shared Memory: 7888 MB
  Current Mode: 2560 x 1440 (32 bit) (165Hz)

 Card name: NVIDIA GeForce RTX 3070 Laptop GPU
  Manufacturer: NVIDIA
 Chip type: NVIDIA GeForce RTX 3070 Laptop GPU
Display Memory: 15921 MB
  Dedicated Memory: 8033 MB
 Shared Memory: 7888 MB

  The problem seems to be with the usage of both integrated GPU and
  dedicated GPU, as the problem persists when the integrated GPU is the
  one in usage.

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


-- 
Mailing list: https://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 1989477] Re: Switching to dark mode in settings does not change shell theme.

Note that changing the Style>Color value in Settings, or using the quick
menu option 'Dark Mode' both seem to work around the problem.

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

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

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

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

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

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

** Tags added: lunar

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

Title:
Switching to dark mode in settings does not change shell theme.

Status in gnome-control-center package in Ubuntu:
Triaged
Status in gnome-shell package in Ubuntu:
Triaged

Bug description:
Changing the "Style" in the "Appearance" section of "Settings" (gnome-
control-center), does not update the shell theme. When I select dark
mode from settings, Libadwaita apps respond to the changes, but the
shell theme and GTK3 applications do not. This has been observed on
both Wayland and X11.

Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10

Package Version: 1:43~rc-1ubuntu2

What I Expected: Changing the style in settings will affect all the
apps that support changing light/dark mode. The shell theme will also
respond to the change.

What happened instead: Only libadwaita apps are affected by changing
the style in Settings. GTK3 apps and the shell theme do not change.
When changing to dark mode via the quick settings menu, all the apps
change their color scheme appropriately. However, there is not a
smooth transition when switching the style from quick settings.

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

--
Mailing list: https://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 1991494] Re: dark mode sometimes works

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

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  dark mode sometimes works

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  the dark mode sometimes works and sometimes doesn't work. If i open
  Ubuntu Software store dark mode doesn't work and i have to go back to
  turn it back on again then it work's, its like it doesn't went to be
  in dark mode when i open Ubuntu Software store. it doesn't matter that
  must to me i just want you guys to know about it.

  this problem in on Ubuntu 22.10 Kinetic Kudu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 20:18:36 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e]
  InstallationDate: Installed on 2022-10-02 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  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.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  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/gnome-shell/+bug/1991494/+subscriptions


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

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

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

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

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

** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  Settings and Quick Menu apply Dark style differently

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

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

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

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

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


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

[Desktop-packages] [Bug 1993878] Re: Dark mode from the drop down menu turning off on it's own

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

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  Dark mode from the drop down menu turning off on it's own

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  tldr; Dark mode from the drop down menu turning off on it's own,
  resulting in mismatched theme across the shell.

  Description:  Ubuntu 22.10
  Release:  22.10

  Gnome 43.

  Expected : Dark mode from the drop down menu matching the one from
  system settings.

  What happens : Dark mode from the drop down menu turning off on it's
  own.

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


-- 
Mailing list: https://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 1993883] Re: problems with dark mode

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

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  problems with dark mode

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

Bug description:
  when going to appearance settings my dark panels become white, though
  settings are not changed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 12:01:14 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-27 (267 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-02-07T09:04:41.555461

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


-- 
Mailing list: https://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 1997147] Re: App theme for legacy GTK3 apps inadvertently changes to light mode when Appearance pane in Settings is clicked/made active in Ubuntu 22.10

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

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  App theme for legacy GTK3 apps inadvertently changes to light mode
  when Appearance pane in Settings is clicked/made active in Ubuntu
  22.10

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

Bug description:
  This bug happens with dark mode enabled, whenever I open Settings with 
Appearance pane open, or I enter Appearance pane from other panes in Settings.
  Whenever I do so, the app theme for legacy GTK3 applications (those not 
supporting the new GTK dark mode API) inadvertently changes to light mode. To 
turn back dark mode on for legacy apps, 
  I have to use the toggle in Quick Settings, or click on any of the theme 
circles.

  Normally, the dark mode theme for legacy apps should not change whenever 
Settings is opened with Appearance pane open, or Appearance pane is selected 
from other panes in Settings, just like
  GTK3 applications using the new dark mode API, and  GTK4+libadwaita apps 
(which are not affected by this bug).

  A recording of the bug in action is attached along with this report.

  Ubuntu release details:
  Description:  Ubuntu 22.10
  Release:  22.10

  Package details: 
  gnome-control-center:
Installed: 1:43.0-1ubuntu2
Candidate: 1:43.0-1ubuntu2
Version table:
   *** 1:43.0-1ubuntu2 500
  500 http://ae.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 19 17:32:30 2022
  InstallationDate: Installed on 2022-09-24 (56 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/1997147/+subscriptions


-- 
Mailing list: https://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 1999472] Re: Dark mode not working correctly

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

It seems this is already covered by bug 1993874.

** This bug has been marked a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  Dark mode not working correctly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Version of Ubuntu: 22.10
  Package: X.org
  Expected to happen: Toolbox on the top right corner should stay in dark mode 
all the time.
  What happened instead: When accessing appearance options at config menu, the 
toolbox on the top right corner goes white, not corresponding with the dark 
mode selected on the config menu.

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


-- 
Mailing list: https://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 1997529] Re: Gnome Shell forgets settings

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

** This bug is no longer a duplicate of bug 1993874
   Settings and Quick Menu apply Dark style differently
** This bug has been marked a duplicate of bug 1989477
   Switching to dark mode in settings does not change shell theme.

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

Title:
  Gnome Shell forgets settings

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome Shell forgets that it has been told to be in dark mode. Often
  you log in and it has reverted to light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-24.25-generic 5.19.17
  Uname: Linux 5.19.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 23 07:10:39 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-11-17 (5 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1999472] Re: Dark mode not working correctly

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

Thanks for the bug report. It appears you need to toggle the color
selection to get it to apply to the "toolbox" (aggregate menu):

Settings > Appearance > Style > Color = change values

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

** Tags added: kinetic

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

Title:
  Dark mode not working correctly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Version of Ubuntu: 22.10
  Package: X.org
  Expected to happen: Toolbox on the top right corner should stay in dark mode 
all the time.
  What happened instead: When accessing appearance options at config menu, the 
toolbox on the top right corner goes white, not corresponding with the dark 
mode selected on the config menu.

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


-- 
Mailing list: https://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 1999320] Re: Font alignment issue when using scaling factor > 1

** Tags added: jammy

** Summary changed:

- Font alignment issue when using scaling factor > 1
+ Font alignment issue in search bar when using scaling factor > 1

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

Title:
  Font alignment issue in search bar when using scaling factor > 1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I use a desktop interface text scaling factor of 1.5, the
  alignment text in the applications menu search bar is not set properly

  I have attached a screenshot showing the issue.

  1)
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  3) text was centered
  4) it is not centered

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


-- 
Mailing list: https://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 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

2023-01-03 Thread DuckDuckWhale

Hi, I have it installed and the issue is still present on that version.
The upstream maintainer is unable to reproduce it on the newer Flatpak
version and suspects that it's related to Ubuntu instead:


Here's a snapshot of `top`:

```
top - 17:46:31 up 11 days,  3:23,  1 user,  load average: 2.76, 2.40, 3.11
Tasks: 520 total,   3 running, 515 sleeping,   0 stopped,   2 zombie
%Cpu(s): 24.4 us,  3.8 sy,  0.0 ni, 70.7 id,  1.1 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  15635.1 total,359.1 free,   8045.4 used,   7230.6 buff/cache
MiB Swap:   8192.0 total,   4474.0 free,   3718.0 used.   3539.6 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  

 976155 user  20   0  717112 201224   6820 R 180.1   1.3   4:13.66 
ibus-daemon  
   2423 user  20   0 6867760 675268 198844 S  77.7   4.2   6662:37 
gnome-shell  
...
 977417 user  20   0 2346300 460536 100516 S   2.3   2.9   0:17.48 
endeavour 
```

** Bug watch added: gitlab.gnome.org/World/Endeavour/-/issues #475
   https://gitlab.gnome.org/World/Endeavour/-/issues/475

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

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


-- 
Mailing list: https://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 1921398] Re: No dns resolution after closing a vpn/sstp connection

2023-01-03 Thread Neustradamus

It has been solved?

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

Title:
  No dns resolution after closing a vpn/sstp connection

Status in ppp package in Ubuntu:
  Confirmed

Bug description:

  The fix for the following issue closes it for nm-pptp-service-*
  connections, however; it is still a problem for users using network-
  manager-sstp.

  You use network-manager-sstp, connect to your VPN server. Then
  disconnect and you now can't lookup any hostnames.

  
  Original problem
  #1778946 No dns resolution after closing a vpn/pptp connection

  This is still a problem for sstp users.

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


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

Re: [Desktop-packages] [Bug 2000396] Re: installing snap chromium trashed my pre-snap files

2023-01-03 Thread Kathleen Caywood

I only keep one backup, so it has been rewritten several times since the 
incident.

The problem with conversion to snap is that nothing says ahead of time, 
"Oh by the way you need to take these steps to preserve your data 
because the snap mechanism may destroy it."

I cannot tell you which version of chromium was used in the old setup.


On 1/3/23 10:05, Nathan Teodosio wrote:
>> I restored my home directory from backup.
> Do you still have that backup available? If yes, and if
> ~/.config/chromium exists in it, you could try replacing
> ~/snap/chromium/common/chromium with it (better to do a backup of the
> latter though if you already have configuration worth keeping in your
> current set up).
>
>> I went looking for chromium installation.  I thought I found it on
>> chromium.org, but I may have gotten it from ubuntu.  It was called
>> chromium-snap
> The Ubuntu maintained snap has a hook[1] to do the process I suggested
> above so that one's data does not get lost when transitioning to the snap.
>
> One data point worth knowing if you can ascertain that: Which Chromium
> version was used in the old and current setups?
>
> [1]:
> https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=stable#n13
>

-- 
  Kathleen M. Caywood, emailkmcayw...@cox.net

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

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


-- 
Mailing list: https://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 1998966] Update Released

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

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

Title:
  Update gnome-remote-desktop to 42.7

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 42 series

  It fixes some crashes reported to errors.ubuntu.com

  Changes since the current Ubuntu 22.04 LTS release, 42.4:
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


-- 
Mailing list: https://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 1998966] Re: Update gnome-remote-desktop to 42.7

This bug was fixed in the package gnome-remote-desktop - 42.7-0ubuntu1

---
gnome-remote-desktop (42.7-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1998966)

 -- Jeremy Bicha   Tue, 06 Dec 2022 16:34:29 -0500

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

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

Title:
  Update gnome-remote-desktop to 42.7

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 42 series

  It fixes some crashes reported to errors.ubuntu.com

  Changes since the current Ubuntu 22.04 LTS release, 42.4:
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.4...42.7

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


-- 
Mailing list: https://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 1934579] Update Released

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

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Released
Status in nautilus source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  Nautilus crashes when a bookmarked place is opened from dock icon
  context menu

  [ Test case ]

  1. Open Nautilus (and ensure you've a location in the sidebar bookmarks)
  2. Right-click ubuntu dock nautilus icon
  3. Activate one of the bookmarks
  4. Nautilus should open that location without crashing.

  [ Regression potential ]

  A window may not be raised when opened under wayland.

  ---

  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


-- 
Mailing list: https://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 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]

This bug was fixed in the package nautilus - 1:43.0-1ubuntu2

---
nautilus (1:43.0-1ubuntu2) kinetic; urgency=medium

  * debian: Update references to ubuntu/kinetic branch
  * d/p/ubuntu/unity_launcher_support.patch: Only set window time under x11
(LP: #1934579)

 -- Marco Trevisan (Treviño)   Mon, 12 Dec 2022
14:52:09 +0100

** Changed in: nautilus (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Released
Status in nautilus source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  Nautilus crashes when a bookmarked place is opened from dock icon
  context menu

  [ Test case ]

  1. Open Nautilus (and ensure you've a location in the sidebar bookmarks)
  2. Right-click ubuntu dock nautilus icon
  3. Activate one of the bookmarks
  4. Nautilus should open that location without crashing.

  [ Regression potential ]

  A window may not be raised when opened under wayland.

  ---

  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


-- 
Mailing list: https://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 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]

This bug was fixed in the package nautilus - 1:42.2-0ubuntu2

---
nautilus (1:42.2-0ubuntu2) jammy; urgency=medium

  * d/p/ubuntu/unity_launcher_support.patch: Only set window time under x11
(LP: #1934579)

 -- Marco Trevisan (Treviño)   Mon, 12 Dec 2022
15:08:24 +0100

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

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Released
Status in nautilus source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  Nautilus crashes when a bookmarked place is opened from dock icon
  context menu

  [ Test case ]

  1. Open Nautilus (and ensure you've a location in the sidebar bookmarks)
  2. Right-click ubuntu dock nautilus icon
  3. Activate one of the bookmarks
  4. Nautilus should open that location without crashing.

  [ Regression potential ]

  A window may not be raised when opened under wayland.

  ---

  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


-- 
Mailing list: https://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 1995245] Update Released

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

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

Title:
  Update gnome-remote-desktop to 43.2

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 43 series

  It fixes some crashes reported to errors.ubuntu.com

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/compare/43.0...43.2

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case and the "Basic
  VNC Test Case (for Ubuntu 22.04 LTS only)

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


-- 
Mailing list: https://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 1995245] Re: Update gnome-remote-desktop to 43.2

This bug was fixed in the package gnome-remote-desktop - 43.2-0ubuntu1

---
gnome-remote-desktop (43.2-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1995245)
  * Drop all patches: applied in new release

 -- Jeremy Bicha   Tue, 06 Dec 2022 16:21:12 -0500

** Changed in: gnome-remote-desktop (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-remote-desktop to 43.2

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 43 series

  It fixes some crashes reported to errors.ubuntu.com

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/compare/43.0...43.2

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case and the "Basic
  VNC Test Case (for Ubuntu 22.04 LTS only)

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


-- 
Mailing list: https://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 654361] Re: GLX 1.3 programs (like clutter) fail with software rasteriser

2023-01-03 Thread Oibaf

Is this still an issue with a newer Ubuntu?

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  GLX 1.3 programs (like clutter) fail with software rasteriser

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Clutter-using apps will fail to start with the software rasteriser with the 
message:
  """
  failed to create drawable
  Failed to initialise clutter: Unable to select the newly created GLX context
  """

  swrast_dri.so is probably missing some GLX 1.3 stuff to make this work
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgl1-mesa-dri 7.9~git20100924-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  DRM.card0.DisplayPort.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DisplayPort.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DisplayPort.3:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI_Type_A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI_Type_A.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1440x900
   edid-base64: 
AP///wAwrhRAACoSAQOAGhB46uWVk1ZPkCgoUFQBAQEBAQEBAQEBAQEBAQEB8BygoFCEGjAYEDYABaMQAAAY8BygoFCEGjAYEDYABaMQAAAYDwCVCjKVCjIZAQAwZABV/gBMVEQxMjFFUTNCCiAgAJM=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Mon Oct  4 14:00:13 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100817)
  MachineType: LENOVO 7465CTO
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic 
root=UUID=e136bf5d-1b75-4152-9f1c-8f77220ef0f2 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_AU:en_GB:en_US:en
   PATH=(custom, user)
   LANG=en_AU.utf8
   SHELL=/usr/bin/zsh
  SourcePackage: mesa
  dmi.bios.date: 03/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET63WW (3.13 )
  dmi.board.name: 7465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET63WW(3.13):bd03/10/2010:svnLENOVO:pn7465CTO:pvrThinkPadX200s:rvnLENOVO:rn7465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7465CTO
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

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


-- 
Mailing list: https://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 1928536] Re: VNC Password cleared on reboot

2023-01-03 Thread Toby Broom

It same on 22.10, I assume since the upstream is the issue.  As NLin
there is plenty of comment on AskUbuntu

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

Title:
  VNC Password cleared on reboot

Status in gnome-remote-desktop package in Ubuntu:
  Triaged

Bug description:
  Password is set using the Screen Sharing settings... Screen sharing
  works till next machine reboot. After reboot the password entry is
  cleared in the settings and cannot connect anymore.

  The following line appears in syslog:
  May 15 09:53:37 alpha gnome-remote-de[1512]: Couldn't retrieve VNC password: 
Password not set

  Setting the password again in settings solves the problem... but this
  isn't very helpful on a machine which is meant to run headless.

  Thanks,
  J.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: vino 3.22.0-6ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 10:40:49 2021
  InstallationDate: Installed on 2019-01-03 (862 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: vino
  UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago)

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


-- 
Mailing list: https://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 1998639] Re: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

2023-01-03 Thread Oibaf

** Summary changed:

- MESA-INTEL: warning:
+ MESA-INTEL: warning: Performance support disabled, consider sysctl 
dev.i915.perf_stream_paranoid=0

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

Title:
  MESA-INTEL: warning: Performance support disabled, consider sysctl
  dev.i915.perf_stream_paranoid=0

Status in mesa package in Ubuntu:
  New

Bug description:
  MESA-INTEL: warning: Performance support disabled, consider sysctl
  dev.i915.perf_stream_paranoid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.39 [origin: unknown]
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  2 13:09:19 2022
  InstallationDate: Installed on 2021-06-05 (545 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2022-11-30 (2 days ago)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-11-29T19:37:54.229059

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


-- 
Mailing list: https://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 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below

2023-01-03 Thread ali pourjamal

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

** Summary changed:

- xorg-core package does not provide xorg-video-abi under kinetic(22.10), which 
breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and 
below
+ xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with 
graphics drivers version 510 and below

** Summary changed:

- xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with 
graphics drivers version 510 and below
+ xorg-core package does not provide xorg-video-abi version 24 ( it is version 
25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older

** Description changed:

  Description:  Ubuntu 22.10
  Release:  22.10
  
  xserver-xorg-core:
-   Installed: 2:21.1.4-2ubuntu1
-   Candidate: 2:21.1.4-2ubuntu1
-   Version table:
-  *** 2:21.1.4-2ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2:21.1.4-2ubuntu1
+   Candidate: 2:21.1.4-2ubuntu1
+   Version table:
+  *** 2:21.1.4-2ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ 
+ Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't
+ because the only compatible mix of CUDA and drivers results in a virtual
+ dependency problem.
+ 
+ apparently the problem is the lack the xorg-video-abi-24 in the xserver-
+ xorg-core package
+ 
+ as the grep command shows, only the video-abi-25 is provided in ubuntu
+ 22 , but in order to install cuda 10.2 (or older), the version 24 is
+ needed.
+ 
+ $ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)'
+ Package: xserver-xorg-core
+ Version: 2:21.1.3-2ubuntu2.5
+ Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
+ Package: xserver-xorg-core
+ Version: 2:21.1.3-2ubuntu2
+ Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting
  
  
- Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because 
the only compatible mix of CUDA and drivers results in a virtual dependency 
problem.
+ installing cuda 10.2 or older will give you this error:
  
- The latest version of the nividia-drivers on my system is 510,for all
- packages newer than this the persistence daemon fails.  No problem I
- suppose, I'll just install 510 and cuda-drivers-510.
+  xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
+   xorg-video-abi-23 but it is not 
installable or
+   xorg-video-abi-20 but it is not 
installable or
+   xorg-video-abi-19 but it is not 
installable or
+   xorg-video-abi-18 but it is not 
installable or
+   xorg-video-abi-15 but it is not 
installable or
+   xorg-video-abi-14 but it is not 
installable or
+   xorg-video-abi-13 but it is not 
installable or
+   xorg-video-abi-12 but it is not 
installable or
+   xorg-video-abi-11 but it is not 
installable or
+   xorg-video-abi-10 but it is not 
installable or
+   xorg-video-abi-8 but it is not 
installable or
+   xorg-video-abi-6.0 but it is not 
installable
  
- Only that doesn't work, because apparently though this package is
- installed it doesn't rprovide any of the xorg-video-abi virtual packages
- like it did in prior versions.
- 
- sudo apt-get install cuda-drivers-510 
- Reading package lists... Done
- Building dependency tree... Done
- Reading state information... Done
- Some packages could not be installed. This may mean that you have
- requested an impossible situation or if you are using the unstable
- distribution that some required packages have not yet been created
- or been moved out of Incoming.
- The following information may help resolve the situation:
- 
- The following packages have unmet dependencies:
-  xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not 
installable or
-   xorg-video-abi-23 but it is not 
installable or
-   xorg-video-abi-20 but it is not 
installable or
-   xorg-video-abi-19 but it is not 
installable or
-   xorg-video-abi-18 but it is not 
installable or
-   xorg-video-abi-15 but it

[Desktop-packages] [Bug 2000937] Re: DING settings values shown untranslated

2023-01-03 Thread Thierry Mass

Good joob !
Thanks very much.
Regards,
Roxfr

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

Title:
  DING settings values shown untranslated

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

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

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


-- 
Mailing list: https://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 1999924] Re: Unsupported buffer format 842094158

** Merge proposal linked:
   
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/435082

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

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

Title:
  Unsupported buffer format 842094158

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on
  Ubuntu 22.10 Wayland.

  When playing a h264 video, or a youtube video, I get:

  ```
  $ snap info chromium | grep installed
  installed:  107.0.5304.121-hwacc(2224) 171MB -
  $ chromium ~/sample.mp4
  Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.
  [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not 
supported, GL is egl, ANGLE is
  [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to 
initialize database.
  [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] 
libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: 
Unsupported buffer format 842094158

  Trace/breakpoint trap (core dumped)
  ```

  Test video: https://test-
  videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4

  I will try other hwacc versions and a non-hwacc version to see if they
  behave differently.

  OS: Ubuntu 22.10

  Desktop: Wayland

  GPU: Intel AlderLake-S GT1

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


-- 
Mailing list: https://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 1999924] Re: Unsupported buffer format 842094158

2023-01-03 Thread Bram Stolk

https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-
source/+merge/435082

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

Title:
  Unsupported buffer format 842094158

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on
  Ubuntu 22.10 Wayland.

  When playing a h264 video, or a youtube video, I get:

  ```
  $ snap info chromium | grep installed
  installed:  107.0.5304.121-hwacc(2224) 171MB -
  $ chromium ~/sample.mp4
  Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.
  [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not 
supported, GL is egl, ANGLE is
  [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to 
initialize database.
  [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] 
libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: 
Unsupported buffer format 842094158

  Trace/breakpoint trap (core dumped)
  ```

  Test video: https://test-
  videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4

  I will try other hwacc versions and a non-hwacc version to see if they
  behave differently.

  OS: Ubuntu 22.10

  Desktop: Wayland

  GPU: Intel AlderLake-S GT1

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


-- 
Mailing list: https://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 2000937] Re: Translation problem (missing?)

2023-01-03 Thread Gunnar Hjalmarsson

Thanks for your report! There are different reasons why those strings
are not shown translated.

* The "Color" string is a bug, and I have committed a fix for that:
  https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/1ce60c52

* The "Ubuntu Desktop" string simply needs to be translated:
  
https://translations.launchpad.net/ubuntu/lunar/+source/gnome-control-center/+pots/gnome-control-center-2.0/fr?search=ubuntu+desktop

But as regards the values in the Desktop Icons section, I don't know why
they are not shown translated. "Bottom Right", for instance, is indeed
translated into French:

$ echo $(LANGUAGE=fr gettext -d gnome-control-center-2.0 -c 'Alignment of new 
desktop icons' 'Bottom Right')
Bas à droite

** Summary changed:

- Translation problem (missing?)
+ DING settings values shown untranslated

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Changed in: ubuntu-translations
   Status: New => Confirmed

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu French Translators (ubuntu-l10n-fr)

** Changed in: ubuntu-translations
   Status: Confirmed => Triaged

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

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

** Tags added: kinetic lunar

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

Title:
  DING settings values shown untranslated

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

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

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


-- 
Mailing list: https://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 1831624] Re: [upstream] ibus-cangjie in libreoffice cannot type Chinese character at end of line

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [upstream] ibus-cangjie in libreoffice cannot type Chinese character
  at end of line

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

Bug description:
  I am using LibreOffice Version: 6.0.7.3, in particular I am using
  LibreOffice Writer.

  I am using ibus-cangjie to input Chinese.

  I cannot input any Chinese characters when I reach the end of a line
  on the screen.

  The expected behavior is that the typed Chinese character simply
  spills over to the next line and I can continue to type without a
  problem.

  If I reach the end of the line with half a space (of full-sized
  Chinese character) available, then I could insert a punctuation mark
  like 。 or 、 even if I use cangjie codes to input them (and then I can
  continue normally).

  if I reach the end of the line with no space available, then I cannot
  insert 。 or 、 when I use cangjie codes to input them (in the ibus-
  cangjie standard input table, 、 = XI)

  In neither case I can type a Chinese character like 日, all the typed
  characters simply disappears from the input queue and is not typed at
  all.  Note that as I type I can see that the candidate Chinese
  characters according to the cangjie codes I input, they just don't get
  sent to the application.

  when I am at the end of the line, I can type as many spaces as I want
  and the problem of being unable to type a Chinese character persists.

  Finally, the bug only triggers when I am at the end of text; if I am
  inserting in the middle of text, even if I am at the linebreak, I can
  type normally and naturally.

  the attached screenshot shows where I am getting my cursor stuck.

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


-- 
Mailing list: https://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 1831624]

2023-01-03 Thread Stephane-guillou-i

Cursor now follows the spaces in the margin and beyond the page with fix for 
bug 43100, so marking as a duplicate.
Formatting marks don't show beyond the page, but that could be a follow-up bug 
report if it is considered to be lacking.

*** This bug has been marked as a duplicate of bug 43100 ***

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

Title:
  [upstream] ibus-cangjie in libreoffice cannot type Chinese character
  at end of line

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

Bug description:
  I am using LibreOffice Version: 6.0.7.3, in particular I am using
  LibreOffice Writer.

  I am using ibus-cangjie to input Chinese.

  I cannot input any Chinese characters when I reach the end of a line
  on the screen.

  The expected behavior is that the typed Chinese character simply
  spills over to the next line and I can continue to type without a
  problem.

  If I reach the end of the line with half a space (of full-sized
  Chinese character) available, then I could insert a punctuation mark
  like 。 or 、 even if I use cangjie codes to input them (and then I can
  continue normally).

  if I reach the end of the line with no space available, then I cannot
  insert 。 or 、 when I use cangjie codes to input them (in the ibus-
  cangjie standard input table, 、 = XI)

  In neither case I can type a Chinese character like 日, all the typed
  characters simply disappears from the input queue and is not typed at
  all.  Note that as I type I can see that the candidate Chinese
  characters according to the cangjie codes I input, they just don't get
  sent to the application.

  when I am at the end of the line, I can type as many spaces as I want
  and the problem of being unable to type a Chinese character persists.

  Finally, the bug only triggers when I am at the end of text; if I am
  inserting in the middle of text, even if I am at the linebreak, I can
  type normally and naturally.

  the attached screenshot shows where I am getting my cursor stuck.

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


-- 
Mailing list: https://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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

2023-01-03 Thread Sharcoux

Thanks so much @brian-murray !

I didn't know how to find out the package responsible for that part!

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

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


-- 
Mailing list: https://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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

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


-- 
Mailing list: https://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 2000628] [NEW] The wifi password prompt disappear immediately after showing up on 22.04

You have been subscribed to a public bug:

Some other people reported this bug
[here](https://askubuntu.com/questions/1409433/22-04-cant-input-
password-for-wifi)

Basically, when you try to log into a network, there is no way to input
your password. The only way to reach a visible network seems to be by
one of the workarounds: use the "Connect to Hidden Network" option, or
directly edit the network config files.

It seems like a critical bug to me because it can demotivate new users
of Ubuntu and Linux.

I joined a screen record of the prompt blinking on screen.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
The wifi password prompt disappear immediately after showing up on 22.04
https://bugs.launchpad.net/bugs/2000628
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ubuntu-meta in Ubuntu.

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

[Desktop-packages] [Bug 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened

** Changed in: gnome-control-center
   Status: Fix Released => New

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

Title:
  High Xorg and gnome-shell CPU usage while Sound Settings opened

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

Bug description:
  Several days ago I found huge lags over all system on my Ubuntu
  20.04.1 LTS. Today I think found the problem, but not the reason. So
  when I open Settings -> Sound menu, the CPU usage comes to about 100%.
  If I close Settings window or go to other tab, it becomes OK. Nothing
  special in my sound configuration - monitor and notebook with built in
  audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04
  LTS.

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 29 18:27:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824]
  InstallationDate: Installed on 2020-09-12 (47 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. G5 5587
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 03PVDF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.product.sku: 0824
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

Re: [Desktop-packages] [Bug 2000396] Re: installing snap chromium trashed my pre-snap files

> I restored my home directory from backup.
Do you still have that backup available? If yes, and if 
~/.config/chromium exists in it, you could try replacing 
~/snap/chromium/common/chromium with it (better to do a backup of the 
latter though if you already have configuration worth keeping in your 
current set up).

> I went looking for chromium installation.  I thought I found it on
> chromium.org, but I may have gotten it from ubuntu.  It was called
> chromium-snap

The Ubuntu maintained snap has a hook[1] to do the process I suggested 
above so that one's data does not get lost when transitioning to the snap.

One data point worth knowing if you can ascertain that: Which Chromium 
version was used in the old and current setups?

[1]: 
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=stable#n13

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

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


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

Re: [Desktop-packages] [Bug 2000396] Re: installing snap chromium trashed my pre-snap files

2023-01-03 Thread Kathleen Caywood

On 1/3/23 08:45, Nathan Teodosio wrote:
> This was confusing to me.
>
>   > I replaced my boot drive, which also had /home on it.
>
> So you would no longer have user configuration files in your new set up.

I restored my home directory from backup.

>
>   > and installed chromium from your website
>
> What do you mean?

I went looking for chromium installation.  I thought I found it on 
chromium.org, but I may have gotten it from ubuntu.  It was called 
chromium-snap


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

-- 
  Kathleen M. Caywood, emailkmcayw...@cox.net

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

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


-- 
Mailing list: https://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 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults

Started happening again for 109.

https://launchpadlibrarian.net/643916878/buildlog_snap_ubuntu_focal_armhf_chromium-
snap-from-source-beta_BUILDING.txt.gz

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

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

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

Title:
  FTBFS on armhf since version 102: the final link step segfaults

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Example build log:

  [51110/51110] LINK ./chrome
  FAILED: chrome 
  python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- 
../../../../../usr/bin/clang++-10 
-Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC 
-Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf 
-no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs 
-Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o 
"./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group  
-ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 
-lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups 
-lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon 
-lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm 
-lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci 
-latspi -lxshmfence
  clang++-10: error: unable to execute command: Segmentation fault (core dumped)
  clang++-10: error: linker command failed due to signal (use -v to see 
invocation)
  ninja: build stopped: subcommand failed.

  This is observed for the deb package builds targeting bionic (built
  with clang 10), on armhf only (other architectures build fine).

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


-- 
Mailing list: https://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 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record

Glad to hear your issue is solved, since you confirmed it is Snap
related I'm marking it as resolved for Firefox and Chromium.

If you happen to locate the patch or post, please do let we know.

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

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

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

Title:
  [snap] chromium fails to start: unsupported version 0 of Verneed
  record

Status in chromium-browser package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  Just updated before trying to run the chromium.

  $ chromium-browser

  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  sed: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  cp: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  md5sum: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  xdg-user-dirs-update: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: 
/home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or 
directory
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  mkdir: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  ln: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: 
/home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file 
or directory
  rm: error while loading shared libraries: 
/snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: 
unsupported version 0 of Verneed record
  
/snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules:
 error while loading shared libraries:

[Desktop-packages] [Bug 2000396] Re: installing snap chromium trashed my pre-snap files

This was confusing to me.

 > I replaced my boot drive, which also had /home on it.

So you would no longer have user configuration files in your new set up.

 > and installed chromium from your website

What do you mean?


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

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

Title:
  installing snap chromium trashed my pre-snap files

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Most of my bookmarks, passwords, etc., from the pre-snap version of
  chromium are gone since I installed snap chromium.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  
  chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2
Candidate: 1:85.0.4183.83-0ubuntu2
Version table:
   *** 1:85.0.4183.83-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected my most recent bookmarks and files to be accessible after
  replacing the non-snap chromium with the snap chromium

  Instead, the only version of book marks, configuration, passwords,
  etc., are several years old

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


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

[Desktop-packages] [Bug 2000940] [NEW] Application "Startup Application Preferences" is not translated

2023-01-03 Thread Thierry Mass

Public bug reported:

Ubuntu 22.10 ; Gnome 43.0

Hello,
The application "Startup Application Preferences" is not translated.
See image below.
Regards,
Roxfr

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

** Attachment added: "Application "Startup Application Preferences" is not 
translated"
   https://bugs.launchpad.net/bugs/2000940/+attachment/5638954/+files/01.png

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

Title:
  Application "Startup Application Preferences" is not translated

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  The application "Startup Application Preferences" is not translated.
  See image below.
  Regards,
  Roxfr

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


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

[Desktop-packages] [Bug 1993356] Re: udisks doesn't make sense from cdrom

2023-01-03 Thread Lucas Kanashiro

We still have no progress in the upstream issue.

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

Title:
  udisks doesn't make sense from cdrom

Status in udisks:
  Unknown
Status in qemu package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  udisks doesn't make sense from cdrom

  there are journal errors from sending ATA command IDENTIFY, maybe
  incomplete kernel or qemu support?

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


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

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

2023-01-03 Thread Batwam

** Tags added: lunar

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

Title:
  Settings and Quick Menu apply Dark style differently

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

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

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

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

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


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

[Desktop-packages] [Bug 2000937] [NEW] Translation problem (missing?)

2023-01-03 Thread Thierry Mass

Public bug reported:

Ubuntu 22.10 ; Gnome 43.0

Hello,
There is a translation problem (missing?) in gnome-control-center.
See image attached.
Regards,
Roxfr

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

** Attachment added: "Image of non translation"
   https://bugs.launchpad.net/bugs/2000937/+attachment/5638945/+files/03.png

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

Title:
  Translation problem (missing?)

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

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

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


-- 
Mailing list: https://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 1995231] Re: image viewer is not showing some JPEG images

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

Most likely this was the same as bug 1998263.

** This bug has been marked a duplicate of bug 1998263
   JPEG ( backing store not supported ) : many pictures won't open.

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

Title:
  image viewer is not showing some JPEG images

Status in eog package in Ubuntu:
  New

Bug description:
  eog is not displaying some JPEG images which is fine with last 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 08:16:18 2022
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1786268] Re: EOG crashes when opening a large file

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

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

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

Title:
  EOG crashes when opening a large file

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  While opening a large file (eg, >8MB jpeg file), EOG segfaults with
  the following error:

  --
  (eog:16768): Gdk-ERROR **: 15:24:55.294: The program 'eog' received an X 
Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1790 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)
  --

  Increasing the kernel maximum shared memory value allows to go
  further:

  $ sudo sysctl -w kernel.shmmax=536870912

  Reopening the file with EOG will hang again, this time displaying this
  error:

  --
  $ eog '/media/data/Pictures/France2018/DSC_2333.JPG' 

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkDrawingArea': invalid value (typically too big) for the size of
  the input (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkOverlay': invalid value (typically too big) for the size of the
  input (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'EogScrollView': invalid value (typically too big) for the size of the
  input (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkOverlay': invalid value (typically too big) for the size of the
  input (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkPaned': invalid value (typically too big) for the size of the
  input (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkBox': invalid value (typically too big) for the size of the input
  (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkBox': invalid value (typically too big) for the size of the input
  (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget
  'GtkBox': invalid value (typically too big) for the size of the input
  (surface, pattern, etc.)

  (eog:17133): Gtk-WARNING **: 15:28:04.750: drawing failure for widget 
'EogWindow': invalid value (typically too big) for the size of the input 
(surface, pattern, etc.)
  --
  (etc.)

  I've uploaded the file used in this bug report here:
  
https://drive.google.com/file/d/1HW7QQNQ3nq19sgyRfyVbdsT_nit3Nj8l/view?usp=sharing

  
  Expected behavior:
  File should open, or at least a warning message should popup to explain that 
the file is too big to be displayed.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ uname -a
  Linux mars 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy eog
  eog:
Installed: 3.28.1-1
Candidate: 3.28.1-1
Version table:
   *** 3.28.1-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Aug  9 15:38:46 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-07-22 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1946821] Re: eog crashes on tall image

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

** This bug has been marked a duplicate of bug 1786268
   EOG crashes when opening a large file

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

Title:
  eog crashes on tall image

Status in eog package in Ubuntu:
  New

Bug description:
  eog crashes when I try to open it on this PNG file.

  $ eog crasher.png

  (eog:19783): Gdk-ERROR **: 01:44:05.714: The program 'eog' received an X 
Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 456 error_code 11 request_code 130 (MIT-SHM) 
minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() 
function.)
  Trace/breakpoint trap (core dumped)

  
  Probably because the image is unusually tall.

  $ file crasher.png 
  crasher.png: PNG image data, 1138 x 32768, 1-bit colormap, non-interlaced

  It is, however, a valid PNG file.

  $ pnginfo crasher.png
  crasher.png...
Image Width: 1138 Image Length: 32768
Bitdepth (Bits/Sample): 1
Channels (Samples/Pixel): 1
Pixel depth (Pixel Depth): 1
Colour Type (Photometric Interpretation): PALETTED COLOUR (1 colours, 0 
transparent) 
Image filter: Single row per byte filter 
Interlacing: No interlacing 
Compression Scheme: Deflate method 8, 32k window
Resolution: 0, 0 (unit unknown)
FillOrder: msb-to-lsb
Byte Order: Network (Big Endian)
Number of text strings: 0

  $ pngcheck -v crasher.png
  File: crasher.png (4680 bytes)
chunk IHDR at offset 0xc, length 13
  1138 x 32768 image, 1-bit palette, non-interlaced
chunk PLTE at offset 0x00025, length 3: 1 palette entry
chunk IDAT at offset 0x00034, length 4608
  zlib: deflated, 32K window, default compression
chunk IEND at offset 0x01240, length 0
  No errors detected in crasher.png (4 chunks, 99.9% compression).

  I don't have a convenient way to check a newer version of eog because
  of a bug in the snap package.

  https://gitlab.gnome.org/GNOME/eog/-/issues/211

  Maybe related:

  > bad alloc on large (but not too large) image

  https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1786268

  althought this file is quite small:

  $ du --bytes crasher.png 
  4680crasher.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
  Uname: Linux 5.4.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 12 21:30:44 2021
  InstallationDate: Installed on 2020-02-01 (619 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1959513] Re: image crashes image viewer

Please check to see if this is the same as bug 1786268 and otherwise follow 
these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  image crashes image viewer

Status in eog package in Ubuntu:
  Incomplete

Bug description:
  when viewing pixie02.jpg image crashes the image viewer

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: eog 3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 30 10:57:16 2022
  ExecutablePath: /usr/bin/eog
  InstallationDate: Installed on 2022-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1973481] Re: eog can't read a perfectly legitimate JPEG image ("Suspension not allowed here")

** Summary changed:

- eog can't read a perfectly legitimate JPEG image
+ eog can't read a perfectly legitimate JPEG image ("Suspension not allowed 
here")

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

Title:
  eog can't read a perfectly legitimate JPEG image ("Suspension not
  allowed here")

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  If you try to open the attached image with eog, it shows an error
  "Suspension not allowed here." Also, the file manager can't show a
  thumbnail. AND if you set this image as the desktop background you get
  a black background.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: eog 42.0-1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:57:58 2022
  InstallationDate: Installed on 2022-04-30 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 2000917] [NEW] Pipewire correctly detects laptop sound & speakers but no sound

2023-01-03 Thread Luis Alberto Pabón

Public bug reported:

Every now and then, after boot, I get no sounds at all coming from the
speakers. Everything seems normal - the control center reports the
output as active, and if I play anything with sound I can see the VU
meter going back and forth. I've attached a screenshot showing as much.

The internal microphone does not pick up any sounds either when this
happens.

If I connect my Bose NC700 bluetooth headset, I get sound out of it just
fine, and the mike on it also works.

Sometimes the internal sound will start working after a few times of
switching back and forth internal audio / bluetooth headset.

Restarting the systemd pipewire and pipewire-pulse user services doesn't
help. Nor does killing & respawning wireplumber.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pipewire-pulse 0.3.58-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Tue Jan  3 11:25:23 2023
InstallationDate: Installed on 2023-01-03 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: pipewire
UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


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

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

Title:
  Pipewire correctly detects laptop sound & speakers but no sound

Status in pipewire package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


-- 
Mailing list: https://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 2000868] Re: backport required for virtio_gpu_dri.so

2023-01-03 Thread Oibaf

For the record, the fix is already in upstream 22.3.0 and 22.2.5 (lunar
+ currently in "proposed" for kinetic), but not on 22.0.5 (jammy).

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

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


-- 
Mailing list: https://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 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

** Changed in: eog
   Status: Unknown => Fix Released

** Changed in: gdk-pixbuf
   Status: Unknown => Fix Released

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]

2023-01-03 Thread Sebastien Bacher

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

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Committed
Status in nautilus source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  Nautilus crashes when a bookmarked place is opened from dock icon
  context menu

  [ Test case ]

  1. Open Nautilus (and ensure you've a location in the sidebar bookmarks)
  2. Right-click ubuntu dock nautilus icon
  3. Activate one of the bookmarks
  4. Nautilus should open that location without crashing.

  [ Regression potential ]

  A window may not be raised when opened under wayland.

  ---

  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


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

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

2023-01-03 Thread Batwam

for info, I just tried the development build of 23.04 in a VM and the
issue remains.

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

Title:
  Settings and Quick Menu apply Dark style differently

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

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

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

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

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


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

[Desktop-packages] [Bug 1999578] Re: Bursts of high CPU usage after triggering overview

Indeed per the upstream discussion there *might* be things that can be
improved in mutter to reduce this problem. But at the same time it is
somewhat expected behaviour. Only unexpected above some unknowable
threshold of CPU usage that is system-dependent.

So this bug is not invalid, but also not definitely valid, currently
"Opinion".

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

Title:
  Bursts of high CPU usage after triggering overview

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

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

Sounds like the bug only exists in gdk-pixbuf 2.42.9 (Ubuntu 22.10) ...
https://gitlab.gnome.org/GNOME/eog/-/issues/255#note_1534033

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: gnome-control-center (Ubuntu)

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

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues #216
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216
   Importance: Unknown
   Status: Unknown

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Confirmed => Fix Released

** Tags added: fixed-in-gdk-pixbuf-2.42.10 fixed-upstream

** No longer affects: eog (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #255
   https://gitlab.gnome.org/GNOME/eog/-/issues/255

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

** Also affects: gdk-pixbuf (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gdk-pixbuf (Ubuntu Lunar)
   Importance: Undecided
   Status: Fix Released

** Changed in: gdk-pixbuf (Ubuntu Jammy)
   Status: New => Invalid

** Tags added: rls-kk-incoming

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Unknown
Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1999578] Re: Bursts of high CPU usage after triggering overview

2023-01-03 Thread Esokrates

Hi Daniel, thanks very much for having a look. What do you think then
about Jonas Adahl's observations from the syscap files, that "The frame
clocks together dispatches at 1000 Hz at times."? Is this expected to be
triggered by firefox as well, despite the window not being in focus?

Furthermore please note, that the high cpu usage holds for almost a
minute at times even after the overview animation is over!

Firefox was already using the Wayland in the config I used when
reporting the bug.

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

Title:
  Bursts of high CPU usage after triggering overview

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

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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 1999578] Re: Bursts of high CPU usage after triggering overview

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Bursts of high CPU usage after triggering overview

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

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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

francesco,

I think the reason you find Xorg is more fluid might be because you're
using two GPUs (Intel + AMD) and mutter's Wayland handling of secondary
GPUs is sometimes inefficient. To prove that is the issue, you can try
unplugging the external monitor(s) and just compare the laptop screen
performance in Wayland vs Xorg.


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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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 1982560] monitors.xml.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1995682] Re: gnome session freeze when open settings

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

I see...

12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:84db, in gnome-control-c [5686]
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] Resetting chip 
for stopped heartbeat on rcs0
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] *ERROR* rcs0 
reset request timed out: {request: 0001, RESET_CTL: 0001}
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] *ERROR* rcs0 
reset request timed out: {request: 0001, RESET_CTL: 0001}
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] gnome-shell[4227] 
context reset due to GPU hang
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] 
gnome-control-c[5686] context reset due to GPU hang
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] HuC authenticated
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC submission 
enabled
12æœˆ 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC SLPC enabled

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

** This bug has been marked a duplicate of bug 1998950
   GPU hang on Alder Lake laptop

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

Title:
  gnome session freeze when open settings

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  gnome session freeze when open settings and do some operation e.g
  scroll down by mouse wheel to the bottom of the pannel

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Nov  4 16:01:04 2022
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to kinetic on 2022-09-07 (58 days ago)

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


-- 
Mailing list: https://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] ShellJournal.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1982560] ProcEnviron.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1982560] ProcCpuinfoMinimal.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1982560] GsettingsChanges.txt

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions

apport information

** Tags added: apport-collected

** Description changed:

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/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 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

** No longer affects: bluez (Ubuntu)

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

  
  Seems

[Desktop-packages] [Bug 1994144] Re: External display monitor not recognized

Sounds like a kernel issue. Please run this command to see what ports
the kernel thinks are connected:

  grep . /sys/class/drm/*/status

** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

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

Title:
  External display monitor not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xrandr lists four disconnected DPs (though my laptop has zero Display
  Ports) but does not list an HDMI, which is what I use to connect
  external monitor. Cable is sound b/c I have a dual boot setup and
  Windows recognizes the display without issue.

  Using Ubuntu 22.04.1 LTS
  I expected OS to recognize that I have a an HDMI port or alternatively that 
something is plugged into it
  OS does not seem to acknowledge same

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 08:45:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:899b]
  InstallationDate: Installed on 2022-10-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 17-cn2xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 15.2
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 899B
  dmi.board.vendor: HP
  dmi.board.version: 06.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 6.26
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-cn2xxx
  dmi.product.sku: 641G6UA#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://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 1994485] Re: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT

In comment #6 it looks like gnome-shell is stuck on a bug in the amdgpu
kernel driver. But I should have been able to tell that from the
beginning...

дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring gfx_0.0.0 timeout, signaled seq=2186, emitted seq=2188
дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process gnome-shell pid 1818 thread gnome-shel:cs0 pid 1835
дек 23 17:09:14 d-3600xt-22 kernel: amdgpu :0c:00.0: amdgpu: GPU reset 
begin!

** Tags added: amdgpu

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

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

Title:
  Suspend screen bug Gnome  and Gnome  with video card AMD RX6500XT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:35:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-26 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux/+bug/1994485/+subscriptions


-- 
Mailing list: https://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 63245] Re: Cannot alt + tab out of fullscreen games

2023-01-03 Thread parshall jeffery

To download free gaming apps you have to visit roblox game
https://apksbrand.com/roblox-unlimited-robux-mod-apk/

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

Title:
  Cannot alt + tab out of fullscreen games

Status in Metacity:
  Confirmed
Status in metacity package in Ubuntu:
  Triaged

Bug description:
  This bug happens on Ubuntu Dapper 64-bit running the GNOME desktop
  environment.  I have not tested it on Edgy or KDE.

  When running some full screen games, the ALT+TAB shortcut will not
  minimize the window and you are forced to exit in order to return to
  the desktop.  Full screen games I have found this to be true in
  include Tremulous (www.tremulous.net), Nexuiz (www.nexuiz.com),
  Wolfenstein Enemy Territory, and Unreal Tournament 2004
  (http://www.unrealtournament.com/ut2004/).

  TO REPRODUCE THIS BUG:

  1.  Open up one of the above listed games.
  2.  Attempt to minimize the game with the ALT + TAB shortcut.

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


-- 
Mailing list: https://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

francesco,

Please provide some details about your system by running:

  apport-collect 1982560

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

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

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

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

Status in 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.

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 1972048] Re: gjs open a window and did't close using the UI

Please also check to see if your issue is caused by having certain
gnome-shell extensions enabled.

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

Title:
  gjs open a window and did't close using the UI

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gjs open a window and did't close using the UI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Sat May  7 08:30:34 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-18 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1972048] Re: gjs open a window and did't close using the UI

Can you provide a screenshot or photo of the problem?

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

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

Title:
  gjs open a window and did't close using the UI

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gjs open a window and did't close using the UI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Sat May  7 08:30:34 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-18 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://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 1999578] Re: Bursts of high CPU usage after triggering overview

Thanks for the bug report. In your video I can see two causes that are
not really bugs:

* Firefox using CPU at the same time as gnome-shell means it is Firefox
causing the persistent CPU usage in gnome-shell. Make sure Firefox isn't
displaying animations like web ads. Even if that doesn't look like the
problem, it's still Firefox's fault if the problem is correlated with
that app running.

* Triggering the window spread animation causes even higher gnome-shell
CPU usage. This is normal and not a bug. Although we welcome patches to
make it more efficient.

Suggested workaround: Make Firefox render more efficiently by adding
MOZ_ENABLE_WAYLAND=1 to /etc/environment and then reboot. Also don't
leave any browser tabs open that you don't need.

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

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

Title:
  Bursts of high CPU usage after triggering overview

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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 1999578] Re: Bursts of high CPU usage after triggering overview

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6137
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137

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

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

Title:
  Bursts of high CPU usage after triggering overview

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

Bug description:
  As requested in the upstream bug report
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6137, I hereby
  file the downstream issue:

  I am experiencing high cpu usage of gnome-shell in situations where I
  would not expect it, leading to my fans running more often and wasting
  my battery on my Dell XPS 13 9310 2-in1.

  The problem can be seen in action here: 
https://www.youtube.com/watch?v=Y9o7a7BGPE4
  See also the upstream report for syscap recordings of such situations.

  I think there might be a correlation with firefox being opened on
  another workspace (but no video or any other playback happening). At
  least everytime I notice that my an comes on for no reason and I fire
  up top to see gnome shell consuming too much cpu, when I kill all my
  firefox windows gnome shell cpu usage goes down as well, but that
  could be pure coincidence.

  At least I can safely rule out the triple buffering downstream ubuntu
  mutter patch, since I recompiled mutter without the patch and it does
  not really change the problem much.

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


-- 
Mailing list: https://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 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"

The upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2489
also shows there are other ways to trigger this warning.

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

Title:
  Nvidia Wayland sessions sometimes flood the log with
  "clutter_frame_clock_notify_presented: code should not be reached"

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

Bug description:
  Nvidia Wayland sessions sometimes flood the log with:

  [   13.105877] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.106163] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.112490] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.125302] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached
  [   13.142242] computer gnome-shell[1264]: 
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
 code should not be reached

  I've been seeing the issue for months although it only seems to happen
  *after* something has gone wrong in mutter. Not by default.

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


-- 
Mailing list: https://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 1998529] Re: Uninstalling extensions dereferences symlinks, risking data loss