date:20240430

It looks like there are recurring errors "drmModeAtomicCommit: Invalid
argument".

Please try adding this to /etc/environment:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and reboot.


** Tags added: amdgpu hybrid multigpu multimonitor nvidia

** Summary changed:

- Blank screen after logging in Wayland using HP Thunderbolt G4 
+ Blank screen after logging in Wayland using HP Thunderbolt G4 
[drmModeAtomicCommit: Invalid argument]

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

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4
  [drmModeAtomicCommit: Invalid argument]

Status in mutter package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2063892] Re: How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?

2024-04-30 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Unknown => New

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

Title:
  How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Hi !

  For few months I'm getting used to « starred » items in Nautilus /
  Ubuntu 22.04.

  To my surprise I can't find how to do the same in 24.04,

  looks like the option for « starring » an element is missing in
  context menu.

  It's a default install of 24.04 hence « minimal » so maybe I'm missing
  a package ?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 27 00:45:55 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1040, 667)'
  InstallationDate: Installed on 2024-04-25 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

[Desktop-packages] [Bug 2064169] Re: Keyboard shortcuts

Those look fine. Next please run:

gsettings list-recursively org.gnome.settings-daemon.plugins.media-keys
| grep volume > volumekeys.txt

and attach the resulting text file here.

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

Title:
  Keyboard shortcuts

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I don't know if the section is correct, but when using the ubuntu
  keyboard shortcuts I added. Increase sound volume, when you put the
  super+up on, it ends up doing the behavior of another one that I had
  already removed to give way to this new one I made.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 17:28:25 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0781]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0781]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Dell Inc. Inspiron 7460
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=ddb1ca08-8d86-4cc1-a5ef-6f59217ebac6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0JXYRN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd07/23/2021:br1.15:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn0JXYRN:rvrA00:cvnDellInc.:ct10:cvr:sku0781:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7460
  dmi.product.sku: 0781
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/2064169/+subscriptions


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Incomplete => Triaged

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

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

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

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

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

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2056758] Autopkgtest regression report (apport/2.28.1-0ubuntu3)

2024-04-30 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted apport (2.28.1-0ubuntu3) for noble have 
finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:24.04.16 (arm64, armhf, ppc64el, s390x)


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

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

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

Thank you!

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

Title:
  ubuntu-bug doesn't let me file bugs for Snap thunderbird

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid
Status in apport source package in Noble:
  Fix Committed

Bug description:
  I'm trying to report a bug in the new Snap for Thunderbird.

  When I run "ubuntu-bug thunderbird", it:
  * Collects information correctly after I input the sudo password
  * Opens a page like 
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
 which does not seem to be valid.

  This is not the case for Firefox, which works fine with ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 
14:47:27.874792575 
+0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash
   640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 
17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash
  CurrentDesktop: KDE
  Date: Mon Mar 11 16:54:18 2024
  InstallationDate: Installed on 2022-08-29 (560 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago)

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


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

[Desktop-packages] [Bug 2061739] Re: crash in meta_wayland_transaction_commit

Fixed upstream:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3725

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

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

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

Title:
  crash in meta_wayland_transaction_commit

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  The system is Ubuntu Noble with a regular daily updates.
  This happens many times since few days ago but not clear
  at all how to reproduce it.

  Regards,
  Patrice

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Apr 16 09:26:16 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-05-24 (1789 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago)

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


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

[Desktop-packages] [Bug 2064320] Re: gnome-control-center : unable to import a wireguard configuration from file

omg I've tried to import a new wireguard config from my VPN provider, but with 
a short filename; the import seemed to fail because the dialog closed 
immediately after selecting the file and the new VPN connection would not add 
to the list. Tried a second time and had a crash; submitted the report as 
suggested but it would come back again as a new crash repeatedly. I decided to 
reboot to try again fresh but now I have no networking altogether. No Ethernet 
device in /dev 
But lspci still reports my two Ethernet adapters.
I look like I will have to wipe off this system again, start from scratch.
:(

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

Title:
  gnome-control-center : unable to import a wireguard configuration from
  file

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

Bug description:
  In Ubuntu 24.04 LTS fresh install.
  I am unable to import a Wireguard .conf configuration file from the 
gnome-control-center's Network panel.

  Parameters -> Network -> VPN -> + -> Import from file
  Select the .conf file that was sent by my VPN provider, then click Open

  Results in the following error (French) : Impossible d'importer la
  connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est
  illisible ou ne contient pas d'informations de connexion VPN
  reconnues. Erreur: le greffon ne prend pas en charge la fonction
  d'importation. Fermer

  Which roughly translates to : Unable to import VPN connection. The
  AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not
  contain recognized VPN connection information. Error: The plugin does
  not support the import function. Close

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 13:52:58 2024
  InstallationDate: Installed on 2024-04-25 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  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/2064320/+subscriptions


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

[Desktop-packages] [Bug 2064364] Re: gnome-control-center: wireguard pair closes when loosing focus

Further info from my system:

DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 20:15:58 2024
  InstallationDate: Installed on 2024-04-25 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=

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

Title:
  gnome-control-center: wireguard pair closes when loosing focus

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In gnome-control-center -> Network -> VPN -> + -> Wireguard -> Pairs
  -> +

  When adding a pair for the Wireguard connection, if the window looses
  focus (for example because we need do copy-paste from another window),
  the entire "pair" dialog closes and we loose as the info previously
  entered.

  As it is, it's almost not humanly possible to setup a wireguard
  connection manually because typing several long keys by hand is too
  error prone.

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


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

[Desktop-packages] [Bug 2064364] [NEW] gnome-control-center: wireguard pair closes when loosing focus

Public bug reported:

Just installed a fresh Ubuntu 24.04 LTS

In gnome-control-center -> Network -> VPN -> + -> Wireguard -> Pairs
-> +

When adding a pair for the Wireguard connection, if the window looses
focus (for example because we need do copy-paste from another window),
the entire "pair" dialog closes and we loose as the info previously
entered.

As it is, it's almost not humanly possible to setup a wireguard
connection manually because typing several long keys by hand is too
error prone.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: 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/2064364

Title:
  gnome-control-center: wireguard pair closes when loosing focus

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

Bug description:
  Just installed a fresh Ubuntu 24.04 LTS

  In gnome-control-center -> Network -> VPN -> + -> Wireguard -> Pairs
  -> +

  When adding a pair for the Wireguard connection, if the window looses
  focus (for example because we need do copy-paste from another window),
  the entire "pair" dialog closes and we loose as the info previously
  entered.

  As it is, it's almost not humanly possible to setup a wireguard
  connection manually because typing several long keys by hand is too
  error prone.

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


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

[Desktop-packages] [Bug 2064320] Re: gnome-control-center : unable to import a wireguard configuration from file

Whoa you nailed it.

The code fails if the filename + extension is > 20 characters long. It
handles the path name length correctly, it fails only if the filename +
extension is longer than 20 characters. It should be good up to 255 or
32k characters, but it isn't.

Will this be fixed?

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

Title:
  gnome-control-center : unable to import a wireguard configuration from
  file

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

Bug description:
  In Ubuntu 24.04 LTS fresh install.
  I am unable to import a Wireguard .conf configuration file from the 
gnome-control-center's Network panel.

  Parameters -> Network -> VPN -> + -> Import from file
  Select the .conf file that was sent by my VPN provider, then click Open

  Results in the following error (French) : Impossible d'importer la
  connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est
  illisible ou ne contient pas d'informations de connexion VPN
  reconnues. Erreur: le greffon ne prend pas en charge la fonction
  d'importation. Fermer

  Which roughly translates to : Unable to import VPN connection. The
  AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not
  contain recognized VPN connection information. Error: The plugin does
  not support the import function. Close

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 13:52:58 2024
  InstallationDate: Installed on 2024-04-25 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  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/2064320/+subscriptions


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-04-30 Thread John Johansen

For the thunderbird issue I have created
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064363

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 2019776] Re: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen

2024-04-30 Thread Treviño

This is handled via https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3293

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

Title:
  If gnome-shell is started directly (instead of through gnome-session),
  it might deadlock with no output to the screen

Status in GNOME Shell:
  New
Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  If gnome-shell is launched directly instead of launched through gnome-
  session, the process spawning `ibus-daemon` might cause deadlock and
  unable to start the graphics.

  Since `ibusManager.js` checks whether service
  `org.freedesktop.IBus.session.GNOME.service` exists. In our case with
  Ubuntu ubiquity, we've turned off `gnome-session.service` so that the
  check failed and gnome-shell spawns `ibus-daemon` after the check.

  I tried using gdb to gnome-shell and discovered it's hanging in a
  child process spawning `ibus-daemon`, but is still in child_setup of
  `Glib.spawn_async` function:

  ```
  root@dell-desktop:/home/oem# cat /tmp/log
  == Stack trace for context 0x5584da793180 ==
  #0   5584dbd2d478 i   resource:///org/gnome/shell/misc/ibusManager.js:119 
(2776aa47bfb0 @ 12)
  #1   5584dbd2d3a8 i   resource:///org/gnome/shell/misc/ibusManager.js:114 
(2776aa47bf60 @ 426)
  #2   5584dbd2d308 i   resource:///org/gnome/shell/misc/ibusManager.js:90 
(2776aa47bec0 @ 162)
  #3   5584dbd2d268 i   self-hosted:689 (34e3dc212650 @ 15)
  ```

  which is, in ibusManager.js:

  ```
  const [success_, pid] = GLib.spawn_async(
  null, cmdLine, env,
  GLib.SpawnFlags.SEARCH_PATH | 
GLib.SpawnFlags.DO_NOT_REAP_CHILD,
  () => {
  try {
  global.context.restore_rlimit_nofile(); # <- here
  } catch (err) {
  }
  }
  );
  ```

  Further code tracing found out that the deadlock is not during the
  execution of the function (`restore_rlimit_nofile`) but the access to
  the GObject (probably `global.context`).

  Currently my propose to work around this issue is to add a 5 second
  `setTimeout` to the caller of `_spawn` function in `ibusManager.js`.

  I've lost debugging information but I can try reproducing the issue
  and give the backtrace from gdb if needed.

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


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

@u-jjohansen:

```
$ sudo dmesg | grep DENIED
[   20.729222] audit: type=1400 audit(1714359674.872:42): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" 
name="/usr/local/share/" pid=2002 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
[   20.743227] audit: type=1400 audit(1714359674.886:43): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743368] audit: type=1400 audit(1714359674.886:44): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743817] audit: type=1400 audit(1714359674.886:45): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743821] audit: type=1400 audit(1714359674.886:46): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  496.181770] audit: type=1400 audit(1714360150.324:49): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=2609 comm="(python3)"
[  526.667987] audit: type=1400 audit(1714360181.273:50): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=2767 comm="(python3)"
[  554.736942] audit: type=1400 audit(1714360209.342:51): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=3216 comm="(python3)"
[ 2204.153512] audit: type=1400 audit(1714361858.768:60): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 
comm="snap-confine" capability=12  capname="net_admin"
[ 2204.153520] audit: type=1400 audit(1714361858.768:61): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 
comm="snap-confine" capability=38  capname="perfmon"
[ 2205.965365] audit: type=1107 audit(1714361860.578:62): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.2" pid=8056 label="snap.firefox.firefox" peer_pid=1382 
peer_label="unconfined"
[ 2206.032369] audit: type=1107 audit(1714361860.647:63): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 
peer_label="unconfined"
[ 2206.032740] audit: type=1107 audit(1714361860.647:64): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 
peer_label="unconfined"
[ 2206.331239] audit: type=1400 audit(1714361860.946:65): apparmor="DENIED" 
operation="open" class="file" profile="snap.firefox.firefox" 
name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=8056 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2990.682061] audit: type=1400 audit(1714362645.300:66): apparmor="DENIED" 
operation="open" class="file" profile="snap.firefox.firefox" 
name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=12989 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2991.168924] audit: type=1107 audit(1714362645.787:67): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.2" pid=12989 label="snap.firefox.firefox" peer_pid=1382 
peer_label="unconfined"
[ 2991.217994] audit: type=1107 audit(1714362645.836:68): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.107" pid=12989 label="snap.firefox.firefox" peer_pid=13639 
peer_label="unconfined"
[ 2991.218729] audit: type=1107 audit(1714362645.837:69): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1"

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-04-30 Thread John Johansen

@u-dal:

the problem with firefox (it has a snap profile and is allowed access to
user namespaces) is different than with chrome (no profile loaded), but
still might be apparmor related. Can you look in dmesg for apparmor
denials

```
  sudo dmesg | grep DENIED
```

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out

2024-04-30 Thread Benjamin Drung

I'll test this fix (since I am experience the bug).

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

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-session source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
  user-level gnome-session.service systemd unit not properly terminating
  gnome-session on logout. An attempt is made to send SIGTERM to the
  process, which gnome-session does not care about.

  Instead, gnome-session-quit should be invoked when the systemd unit
  shuts down, which acts effectively and immediately.

  [ Test Plan ]

  Actual behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that only the wallpaper is shown for 90 seconds prior to the 
login manager showing again.

  Expected behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

  [ Where problems could occur ]

  If the gnome-session or gnome-session-quit binaries change the
  arguments they accept by default, log in and log out functionality on
  Unity sessions are likely to break.

  Additionally, if lightdm or systemd changes in a non-reverse-
  compatible way, this increases the chance of a user-facing regression.

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


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

[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process

2024-04-30 Thread Alexander Carlsson

I'm having this issue on Raspberry Pi 4 Ubuntu server 24.04.

Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20
02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble

ubuntu@ubuntu:~$ sudo systemctl status gnome-remote-desktop
× gnome-remote-desktop.service - GNOME Remote Desktop
 Loaded: loaded (/usr/lib/systemd/system/gnome-remote-desktop.service; 
enabled; preset: enabled)
 Active: failed (Result: exit-code) since Tue 2024-04-30 21:58:11 UTC; 
11min ago
Process: 1741 ExecStart=/usr/libexec/gnome-remote-desktop-daemon --system 
(code=exited, status=217/USER)
   Main PID: 1741 (code=exited, status=217/USER)
CPU: 10ms

Apr 30 21:58:11 ubuntu systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 5.
Apr 30 21:58:11 ubuntu systemd[1]: gnome-remote-desktop.service: Start request 
repeated too quickly.
Apr 30 21:58:11 ubuntu systemd[1]: gnome-remote-desktop.service: Failed with 
result 'exit-code'.
Apr 30 21:58:11 ubuntu systemd[1]: Failed to start gnome-remote-desktop.service 
- GNOME Remote Desktop.

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

Title:
  gnome-remote-desktop.service: Failed to determine user credentials: No
  such process

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

Bug description:
  On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.

  The desktop does not show up though gdm3 is running.

  I see the following error messages which might indicate a dependency
  issue:

  pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 2.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 3.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 4.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

@u-jjohansen:

Also, I'm having this Thunderbird problem going on simultaneously --
https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
but-is-not-responding-message/39990 -- which might be related to the
issues from my Chrome comments?

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

@u-jjohansen:

Yes, live environment only. Sorry, I thought I'd included that in my
first comment but now I see that I neglected to do so. I added an EDIT:
to my first comment to make it clear.

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out

Hello Simon, or anyone else affected,

Accepted gnome-session into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
session/46.0-1ubuntu4.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-noble

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

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-session source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
  user-level gnome-session.service systemd unit not properly terminating
  gnome-session on logout. An attempt is made to send SIGTERM to the
  process, which gnome-session does not care about.

  Instead, gnome-session-quit should be invoked when the systemd unit
  shuts down, which acts effectively and immediately.

  [ Test Plan ]

  Actual behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that only the wallpaper is shown for 90 seconds prior to the 
login manager showing again.

  Expected behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

  [ Where problems could occur ]

  If the gnome-session or gnome-session-quit binaries change the
  arguments they accept by default, log in and log out functionality on
  Unity sessions are likely to break.

  Additionally, if lightdm or systemd changes in a non-reverse-
  compatible way, this increases the chance of a user-facing regression.

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


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

[Desktop-packages] [Bug 2064354] [NEW] File manager crashes on run

2024-04-30 Thread Elijah Reed

Public bug reported:

Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
$ nautilus
** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
libEGL warning: egl: failed to create dri2 screen
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 16:15:29 2024
GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
InstallationDate: Installed on 2024-04-24 (6 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   44.1-1
 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

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

Title:
  File manager crashes on run

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I 
obtained the following from the command prompt: 
  $ nautilus
  ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 16:15:29 2024
  GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
  InstallationDate: Installed on 2024-04-24 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

[Desktop-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird

Hello Helga, or anyone else affected,

Accepted apport into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apport/2.28.1-0ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  ubuntu-bug doesn't let me file bugs for Snap thunderbird

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid
Status in apport source package in Noble:
  Fix Committed

Bug description:
  I'm trying to report a bug in the new Snap for Thunderbird.

  When I run "ubuntu-bug thunderbird", it:
  * Collects information correctly after I input the sudo password
  * Opens a page like 
https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?,
 which does not seem to be valid.

  This is not the case for Firefox, which works fine with ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 
14:47:27.874792575 
+0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash
   640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 
17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash
  CurrentDesktop: KDE
  Date: Mon Mar 11 16:54:18 2024
  InstallationDate: Installed on 2022-08-29 (560 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago)

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


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

[Desktop-packages] [Bug 2019137] Proposed package upload rejected

An upload of gnome-software to noble-proposed has been rejected from the
upload queue for the following reason: "not an SRU, should be synced to
oracular".

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

Title:
  gnome-software should (?) be separated from the packagekit

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Given that the Snap Store is currently the default in Ubuntu instead
  of GNOME Software, the only reason GNOME Software (along with the Snap
  Store) can be installed is to support Flatpak applications.

  In the current instance, if you want to add flatpak support, GNOME
  Software is installed with both the apt packagekit add-on and the
  flatpak plugin, which is duplication of work (Software Updater already
  works on updates, and Snap Store works on showing deb apps).

  And since the future app store explicitly refuses [1], [2] to support
  flatpak applications, users who need this package format will be
  forced to put GNOME Software with everything I pointed out above.

  Therefore, it would be very nice if the developers removed the
  packagekit add-on from the "gnome-software part" and made it a "plug-
  in for gnome-software".

  I, unfortunately, have no such experience with packaging deb packages
  at the moment, and it turns out that it will obviously be necessary to
  work out both the code part (which, as far as I can see, won't be very
  difficult [3]), as well as the part where we will have to figure out
  where and how to insert the plugin as mandatory (for example, when the
  user completely gives up on snap packages) and as optional (because
  the Snap Store already stands).

  Also, let me know if this needs to be sent to upstream (Debian) instead of 
here.
  
---
  1. https://github.com/ubuntu-flutter-community/software/issues/126
  2. https://github.com/ubuntu-flutter-community/software/issues/30
  3. https://build.opensuse.org/request/show/1031279

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


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

[Desktop-packages] [Bug 2056767] Proposed package upload rejected

An upload of gnome-software to noble-proposed has been rejected from the
upload queue for the following reason: "not an SRU, should be synced to
oracular".

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

Title:
  FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main)
  with gnome-software packaging split

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Impact
  --
  I request permission to sync the gnome-software packaging from Debian. The 
biggest change is splitting gnome-software's .deb support into a separate 
package, gnome-software-plugin-deb, to match the existing -snap and -flatpak 
packages. This will allow users and flavors to specifically opt into the parts 
of the GNOME Software experience they want. For instance, someone may want to 
use only the Flatpak part because they use the Snap Store to manage .debs and 
Snaps. Or maybe they want a different combination.

  This has been requested by multiple users on Ubuntu Discourse and at
  least one Launchpad bug and one Debian bug.

  fwupd plugin
  
  I am dropping the fwupd plugin (now in a separate package too) to Suggests so 
upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs 
won't have it either unless a user explicitly installs it later.

  Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu
  desktop flavors also include it. For people who don't want snaps,
  there is also the gnome-firmware app packaged as a .deb.

  Because Ubuntu already has update-manager to handle apt update
  notifications, I am also dropping the autostart file to reduce
  background RAM use.

  A few Ubuntu desktop flavors do not provide any firmware updater app
  at all. Ubuntu Budgie developers thought a firmware updater app was
  too technical for inclusion in the default Ubuntu 24.04 LTS install.

  autostart
  -
  I have also dropped the autostart file since the fwupd plugin is no longer 
included by default and Ubuntu already has ways to notify users about available 
apt updates (update-manager and unattended upgrades) and snaps already 
automatically update.

  Potential Problems
  ---
  gnome-software has an explicit Recommend: gnome-software-plugin-deb so that 
people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That 
recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed 
then. (There is a Depends on the virtual packages that enable installing apps.)

  Full Changelog Entries
  --
  gnome-software (46.0-4) unstable; urgency=medium

    * Fix typo in gnome-software-plugin-deb package description
    * Add lintian overrides for desktop-command-not-in-package

   -- Jeremy Bícha  Fri, 29 Mar 2024 16:45:30 -0400

  gnome-software (46.0-3) unstable; urgency=medium

    * Update Homepage
    * Release to Unstable

   -- Jeremy Bícha  Thu, 28 Mar 2024 13:23:28 -0400

  gnome-software (46.0-2) experimental; urgency=medium

    * Split deb support into separate gnome-software-plugin-deb package
  (Closes: #1066030) (LP: #2019137, #2056767)
    * Have each plugin provide a virtual gnome-software-plugin package
    * Suggest all the gnome-software plugins
    * Recommend gnome-software-plugin-deb for upgrades
    * Split firmware update support into separate fwupd plugin & recommend it
  except on Ubuntu which provides a separate firmware-updater app
  Intentionally, do not have this provides the virtual gnome-software-plugin
  since it doesn't allow browsing apps.
    * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803)
    * Drop Depends: software-properties-gtk
    * Stop recommending gnome-software-plugin-snap on Ubuntu

   -- Jeremy Bícha  Wed, 27 Mar 2024 18:33:03 -0400

  Build Logs
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra

  Desktop Flavors Affected
  
  GNOME Software is currently included in the default install for only
  Ubuntu Cinnamon. See Joshua's comment below.

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


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

[Desktop-packages] [Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions

Hello theofficialgman, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Regression: Jammy to Noble, set_label no longer functions

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, set_label can be used to set the text 
to display instead of an appindicator icon. In ubuntu noble set_label no longer 
functions at all.
  
https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label

  [ Test Case ]

  - Download the test indicator and its dependencies:
* wget 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
* apt install gir1.2-appindicator3-0.1

  - Run the test indicator:
gjs -m testTool.js

  - Ensure the indicator icon shows up (it has an ubuntu icon)
  - Click on it and activate the "Set Label" item
  - A random numeric label should show next to the icon

  [ Regression potential ]

  The icon is not visible anymore

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


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

[Desktop-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

sorry, the template is there but I had loaded this page yesterday and
not refreshed!

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

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


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

[Desktop-packages] [Bug 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow

Hello iMac, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-noble

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

Title:
  JS ERROR: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in
  AboutToShow

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  With several indicator icons (Chrome, Slack, 1Password) a GDBus.Error
  systemd error message appears with each iteration of a left-click of
  any impacted indicator icon prior to the icon's menu appearing.

  Ubuntu Mantic 23.10, gnome-shell 45.0-1ubuntu2, gnome-shell-extension-
  appindicator 57-1

  Also reported upstream here: https://github.com/ubuntu/gnome-shell-
  extension-appindicator/issues/445

  Nov 06 08:32:20 ubuntu-mantic gnome-shell[3927]: JS ERROR: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow
  
_promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+subscriptions


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

[Desktop-packages] [Bug 2059819] Please test proposed package

Hello theofficialgman, or anyone else affected,

Accepted gnome-shell-extension-appindicator into noble-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/58-1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

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


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

[Desktop-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

An upload of gnome-shell-extension-appindicator has been uploaded to
noble for this issue, but this bug lacks an SRU test case.

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Fix Committed => Incomplete

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  Fix Committed
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

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


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

[Desktop-packages] [Bug 2064197] Re: Labels are invisible until i move mouse at them

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

Thanks, I'm marking it as duplicate

** This bug has been marked a duplicate of bug 2061079
   GTK-ngl (new default backend) rendering issues with the nvidia 470 driver

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

Title:
  Labels are invisible until i move mouse at them

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

Bug description:
  When I open gnome-control-center I can't see labels until I move/hover mouse 
over them.
  Then they are visible until I change to another tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:20:46 2024
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2064197/+subscriptions


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-04-30 Thread John Johansen

@u-dal:
are you running in a live cd environment? Something odd is happening on your 
system, with some profiles loaded and systemctl reporting 
ConditionPathExists=!/rofs/etc/apparmor.d

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Desktop-packages] [Bug 2064320] Re: gnome-control-center : unable to import a wireguard configuration from file

Thank you for your bug report. It seems a bit similar to
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2679
upstream, could you try if renaming the file with a shorter name makes a
difference maybe?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2679
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2679

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

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

Title:
  gnome-control-center : unable to import a wireguard configuration from
  file

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

Bug description:
  In Ubuntu 24.04 LTS fresh install.
  I am unable to import a Wireguard .conf configuration file from the 
gnome-control-center's Network panel.

  Parameters -> Network -> VPN -> + -> Import from file
  Select the .conf file that was sent by my VPN provider, then click Open

  Results in the following error (French) : Impossible d'importer la
  connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est
  illisible ou ne contient pas d'informations de connexion VPN
  reconnues. Erreur: le greffon ne prend pas en charge la fonction
  d'importation. Fermer

  Which roughly translates to : Unable to import VPN connection. The
  AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not
  contain recognized VPN connection information. Error: The plugin does
  not support the import function. Close

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 13:52:58 2024
  InstallationDate: Installed on 2024-04-25 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  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/2064320/+subscriptions


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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in Nautilus sidebar

2024-04-30 Thread vadim

Still broken in 24.04

They don't seem to understand that 
1)Ubuntu has desktop icons 
2)Attach icon will be at the very bottom, which is inconvenient 
3)Wayland is already the present, not the future

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

Title:
  wayland: desktop folder missing in Nautilus sidebar

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

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 2064348] [NEW] Apparmor rule of firefox does not include fcitx

2024-04-30 Thread csslayer

Public bug reported:

The bug is about the firefox in
http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/pool/main/f/firefox/

Snap version seems work fine after merge
https://github.com/snapcore/snapd/pull/12924

Briefly checking the /etc/apparmor.d/usr.bin.firefox, there's no
reference to fcitx dbus services, which prevents it from communicate
with fcitx.

Some other user that reports this issue on ubuntu-jp:
https://lists.ubuntu.com/archives/ubuntu-jp/2023-May/006616.html

Ideally, #include  should be enough, but for now
that only includes fcitx4's dbus service.

I created a MR to add the new service interface for fcitx5 at, but it
would require a apparmor release.

https://gitlab.com/apparmor/apparmor/-/merge_requests/1222/diffs

As a fcitx dev I would suggest add both

#include 

and the changes in
https://gitlab.com/apparmor/apparmor/-/merge_requests/1222/ to
/etc/apparmor.d/usr.bin.firefox so the issue won't be blocked by
apparmor release.

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

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

Title:
  Apparmor rule of firefox does not include fcitx

Status in firefox package in Ubuntu:
  New

Bug description:
  The bug is about the firefox in
  http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/pool/main/f/firefox/

  Snap version seems work fine after merge
  https://github.com/snapcore/snapd/pull/12924

  Briefly checking the /etc/apparmor.d/usr.bin.firefox, there's no
  reference to fcitx dbus services, which prevents it from communicate
  with fcitx.

  Some other user that reports this issue on ubuntu-jp:
  https://lists.ubuntu.com/archives/ubuntu-jp/2023-May/006616.html

  Ideally, #include  should be enough, but for now
  that only includes fcitx4's dbus service.

  I created a MR to add the new service interface for fcitx5 at, but it
  would require a apparmor release.

  https://gitlab.com/apparmor/apparmor/-/merge_requests/1222/diffs

  As a fcitx dev I would suggest add both

  #include 

  and the changes in
  https://gitlab.com/apparmor/apparmor/-/merge_requests/1222/ to
  /etc/apparmor.d/usr.bin.firefox so the issue won't be blocked by
  apparmor release.

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


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

[Desktop-packages] [Bug 2064197] Re: Labels are invisible until i move mouse at them

Seems to be the same issue. Workaround fixes problem.

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

Title:
  Labels are invisible until i move mouse at them

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

Bug description:
  When I open gnome-control-center I can't see labels until I move/hover mouse 
over them.
  Then they are visible until I change to another tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:20:46 2024
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2064197/+subscriptions


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

[Desktop-packages] [Bug 2064320] [NEW] gnome-control-center : unable to import a wireguard configuration from file

Public bug reported:

In Ubuntu 24.04 LTS fresh install.
I am unable to import a Wireguard .conf configuration file from the 
gnome-control-center's Network panel.

Parameters -> Network -> VPN -> + -> Import from file
Select the .conf file that was sent by my VPN provider, then click Open

Results in the following error (French) : Impossible d'importer la
connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est
illisible ou ne contient pas d'informations de connexion VPN reconnues.
Erreur: le greffon ne prend pas en charge la fonction d'importation.
Fermer

Which roughly translates to : Unable to import VPN connection. The
AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not
contain recognized VPN connection information. Error: The plugin does
not support the import function. Close

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-control-center 1:46.0.1-1ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 13:52:58 2024
InstallationDate: Installed on 2024-04-25 (5 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-control-center : unable to import a wireguard configuration from
  file

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

Bug description:
  In Ubuntu 24.04 LTS fresh install.
  I am unable to import a Wireguard .conf configuration file from the 
gnome-control-center's Network panel.

  Parameters -> Network -> VPN -> + -> Import from file
  Select the .conf file that was sent by my VPN provider, then click Open

  Results in the following error (French) : Impossible d'importer la
  connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est
  illisible ou ne contient pas d'informations de connexion VPN
  reconnues. Erreur: le greffon ne prend pas en charge la fonction
  d'importation. Fermer

  Which roughly translates to : Unable to import VPN connection. The
  AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not
  contain recognized VPN connection information. Error: The plugin does
  not support the import function. Close

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 13:52:58 2024
  InstallationDate: Installed on 2024-04-25 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  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/2064320/+subscriptions


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

[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions

2024-04-30 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Some shell elements don't respond to touchscreen in Xorg sessions

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

Bug description:
  Starting in GNOME 46 touchscreen input on the X11 session has become
  unusable

  the touchscreen is responsive on the desktop itself (moving the
  cursor) but does not interact with most things

  on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work 
with:
  - On screen keyboard (touch is registered but no keystrokes get input)
  - clicking options in gnome appindicators (indicators can be opened but 
clicking any option does nothing)
  - interacting with application overview (cannot press left and right buttons 
or search bar)
  - selecting textboxs
  - any of the touch gestures (eg: swipe up from bottom to bringup keyboard)

  All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and
  Ubuntu Noble from March and earlier before it was "upgraded" to GNOME
  46).

  Tested on a fresh image as well as an old image from February running GNOME 
45 upgraded to the latest packages with GNOME 46
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu
  DisplayManager: sddm
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2021-06-21 (1035 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Package: xorg-server
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 46.0-1ubuntu7
  Tags: noble
  Uname: Linux 6.8.0-28-generic x86_64
  UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  Package: xorg-server
  PackageArchitecture: arm64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu7
  Tags: noble third-party-packages
  Uname: Linux 4.9.140-l4t aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip gdm lpadmin plugdev sambashare sudo users 
video weston-launch
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

Ok, thanks for the update. From what you describe that seems either a
corruption in the mbox itself or a bug in thunderbird which failed to
process correct some emails. In any case not a downstream issue and if
you delete the email we don't have a way to debug now so closing the
report.

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions

2024-04-30 Thread theofficialgman

I have filed an upstream bug since this seems to be going nowhere
currently https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7626

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7626
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7626

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

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

Title:
  Some shell elements don't respond to touchscreen in Xorg sessions

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Starting in GNOME 46 touchscreen input on the X11 session has become
  unusable

  the touchscreen is responsive on the desktop itself (moving the
  cursor) but does not interact with most things

  on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work 
with:
  - On screen keyboard (touch is registered but no keystrokes get input)
  - clicking options in gnome appindicators (indicators can be opened but 
clicking any option does nothing)
  - interacting with application overview (cannot press left and right buttons 
or search bar)
  - selecting textboxs
  - any of the touch gestures (eg: swipe up from bottom to bringup keyboard)

  All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and
  Ubuntu Noble from March and earlier before it was "upgraded" to GNOME
  46).

  Tested on a fresh image as well as an old image from February running GNOME 
45 upgraded to the latest packages with GNOME 46
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu
  DisplayManager: sddm
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2021-06-21 (1035 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Package: xorg-server
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 46.0-1ubuntu7
  Tags: noble
  Uname: Linux 6.8.0-28-generic x86_64
  UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  Package: xorg-server
  PackageArchitecture: arm64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu7
  Tags: noble third-party-packages
  Uname: Linux 4.9.140-l4t aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip gdm lpadmin plugdev sambashare sudo users 
video weston-launch
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread Paul White

Thank your for the clarification.

I'll change the status back to 'New' and no doubt a member of Ubuntu's
Desktop Team will review your issue shortly.


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

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread Ge-org Brohammer

apport information

** Tags added: wayland-session

** Description changed:

  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.
  
  After logging in using wayland, both monitors goes blank and then enters
  power saving mode.  If I replug the dock then the monitors wake up but
  with display settings reset.
  
  When using x-server, both screen work as normal after login remembering
  my screen placement etc.
  
  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.
  
  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2024-04-26 (4 days ago)
+ InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 46.0-0ubuntu5
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
+ RelatedPackageVersions: mutter-common 46.0-1ubuntu9
+ Tags: noble wayland-session
+ Uname: Linux 6.8.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2064275/+attachment/5773292/+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/2064275

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble wayland-session
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

So fsck from a live-usb did not reveal errors on my partitions.

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread Ge-org Brohammer

Sorry about the wrong tag. This running x-server session but not sure if
you would like logs with wayland mode?  Just let me know what sequence
since the screens turn off, I might be able to replug the docking
station and collect them again?

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread Ge-org Brohammer

apport information

** Tags removed: 22.04
** Tags added: 24.04

** Tags added: apport-collected noble

** Description changed:

  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.
  
  After logging in using wayland, both monitors goes blank and then enters
  power saving mode.  If I replug the dock then the monitors wake up but
  with display settings reset.
  
  When using x-server, both screen work as normal after login remembering
  my screen placement etc.
  
  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.
  
  Ubuntu 24.04 with latest updtes installed.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2024-04-26 (4 days ago)
+ InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 46.0-0ubuntu5
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
+ RelatedPackageVersions: mutter-common 46.0-1ubuntu9
+ Tags: noble
+ Uname: Linux 6.8.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2064275/+attachment/5773286/+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/2064275

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-04-26 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 46.0-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  Tags: noble
  Uname: Linux 6.8.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread Paul White

>Ubuntu 24.04 with latest updtes installed.
but this report has been tagged '22.04'

Please clarify which release of Ubuntu you are using and run the command

  apport-collect 2064275

as requested in comment #1.


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

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.

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


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

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

@jjohansen:


```
$ sudo aa-status
apparmor module is loaded.
56 profiles are loaded.
54 profiles are in enforce mode.
   /snap/snapd/21465/usr/lib/snapd/snap-confine
   /snap/snapd/21465/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   libreoffice-senddocists=!/rofs/etc/apparmor.d).
   libreoffice-soffice//gpg
   libreoffice-xpdfimport
   rsyslogd
   snap-update-ns.chromium
   snap-update-ns.cups
   snap-update-ns.firefox
   snap-update-ns.firmware-updater
   snap-update-ns.thunderbird
   snap.chromium.chromedriver
   snap.chromium.chromium
   snap.chromium.hook.configure
   snap.cups.accept
   snap.cups.cancel
   snap.cups.cups-browsed
   snap.cups.cupsaccept
   snap.cups.cupsctl
   snap.cups.cupsd
   snap.cups.cupsdisable
   snap.cups.cupsenable
   snap.cups.cupsfilter
   snap.cups.cupsreject
   snap.cups.cupstestppd
   snap.cups.driverless
   snap.cups.gs
   snap.cups.ippeveprinter
   snap.cups.ippfind
   snap.cups.ipptool
   snap.cups.lp
   snap.cups.lpadmin
   snap.cups.lpc
   snap.cups.lpinfo
   snap.cups.lpoptions
   snap.cups.lpq
   snap.cups.lpr
   snap.cups.lprm
   snap.cups.lpstat
   snap.cups.reject
   snap.firefox.firefox
   snap.firefox.geckodriver
   snap.firefox.hook.configure
   snap.firefox.hook.connect-plug-host-hunspell
   snap.firefox.hook.disconnect-plug-host-hunspell
   snap.firefox.hook.post-refresh
   snap.firmware-updater.firmware-notifier
   snap.firmware-updater.firmware-updater
   snap.firmware-updater.firmware-updater-app
   snap.firmware-updater.hook.configure
   snap.thunderbird.hook.configure
   snap.thunderbird.thunderbird
2 profiles are in complain mode.
   libreoffice-oosplash
   libreoffice-soffice
0 profiles are in prompt mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
31 processes have profiles defined.
31 processes are in enforce mode.
   /usr/sbin/rsyslogd (1472) rsyslogd
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77339) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77395) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77397) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77401) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77402) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77404) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77433) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77441) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77443) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (78308) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (78968) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (79729) 
snap.chromium.chromium
   /usr/bin/dash (18605) snap.cups.cups-browsed
   /usr/bin/dash (18912) snap.cups.cups-browsed
   /usr/bin/sleep (92417) snap.cups.cups-browsed
   /usr/bin/dash (18607) snap.cups.cupsd
   /snap/cups/1044/sbin/cupsd (18745) snap.cups.cupsd
   /snap/firefox/4173/usr/lib/firefox/firefox (50912) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (51554) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (51573) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52145) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52713) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52829) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (57517) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (59890) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (84921) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (85070) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (87511) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (93200) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (93235) snap.firefox.firefox
0 processes are in complain mode.
0 processes are in prompt mode.
0 processes are in kill mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
```

```
$ sudo systemctl status apparmor
Warning: The unit file, source configuration file or drop-ins of 
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units.
○ apparmor.service - Load AppArmor profiles
 Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: 
enabled)
 Active: inactive (dead)
  Condition: start condition unmet at Sun 2024-04-28 20:01:04 PDT; 1 day 12h ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/

Apr 28 20:01:02 lubuntu

[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected

2024-04-30 Thread Marko Hrastovec

Thanks for identifying the cause. I had to use wayland, and now I can go
back to Xorg. For me it was impossible to find out why this was
happening, because I was using DMZ-black, and upgraded from 22.04 much
before if was stable. So I thought it will be resolved by the time of
24.04 launch. Unfortunately, that did not happen. Also had to find a
substitute for a program I use, and it only works in X.

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

Title:
  Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme
  is selected

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

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-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  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2062133] Re: Migration to the snap issues

2024-04-30 Thread Pablo Angulo

As mentioned in
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/comments/15
, if there is not enough free space for copying the .thunderbird folder
to its new snap location, then the migration will not be done,
thunderbird will open as new, and the user will not be notified at all.
Creating a soft link will not do. Moving the folder from ~/.thunberdird
to ~/snap/thunderbird/common/ did work.

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

Title:
  Migration to the snap issues

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  After migrating to the snap, I noticed the following:
  - the launcher icon disappeared (I guess it’s because the .desktop file is 
now "thunderbird_thunderbird.desktop"
  - the snap migration took a good 5 minutes on my machine (I guess it’s the 
copy of the email folder), without any feedbacks that something is happening if 
you don’t look at ps output. You don’t have any visual feedback about the 
migration and we should have a progress window (maybe zenity?) to reassure on 
this one time transition
  - all unread emails triggered notification (I guess it’s because the state is 
considered "New") on any folders.
  - I know have 2 15G folders now: ~/snap/thunderbird/common/ and 
~/.thunderbird. I think the latter was the old one which is unused right now 
and it should be cleaned up after the migration to the snap?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: thunderbird 2:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:28:35 2024
  InstallationDate: Installed on 2020-04-24 (1455 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SnapChanges:
   Identifiant  État  DescendancePrêt   
Résumé
   700  Done  2024-04-18T09:06:12+02:00  2024-04-18T09:07:34+02:00  
Installer le paquet Snap "thunderbird"
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

I think I solved the problem. When closing the flatpak-install, terminal
said something about a corrupt JPG. So I went in the flatpak-TB through
many of my e-mails and erased a lot of mails with jpg-attachments. Then
I copied the flatpak-mail-folder to the snap-mail-location, and now the
snap-TB opens everything as expected. So it must have been a corrupt
attachment - or I really have a disc-problem. I can check that later,
but I think now that there is no software bug...

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1

2024-04-30 Thread Jean-Baptiste Lallement

** Also affects: adsys (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: golang-1.22 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: golang-1.22 (Ubuntu Mantic)
   Status: New => Confirmed

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

Title:
  [SRU] adsys 0.14.1

Status in adsys package in Ubuntu:
  Fix Released
Status in golang-1.22 package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  Confirmed
Status in golang-1.22 source package in Jammy:
  Confirmed
Status in adsys source package in Mantic:
  Confirmed
Status in golang-1.22 source package in Mantic:
  Confirmed

Bug description:
  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.

  Given that ADSys directly interfaces with Active Directory and needs
  to align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.

  Now that ADSys has a complete set of features, the request is to
  proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note
  that any new features introduced in subsequent versions will be
  exclusively available in 24.04 and later releases.

  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.

  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-
  desktop/+archive/ubuntu/adsys) and already used in production by
  customers.

  At this time of writing the number of open issues is 1 in Launchpad
  and 16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.

  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.

   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs

   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common

   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version

  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)

  *

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

yes, that seems to be either a disk or kernel error. Could you try
checking the disk or maybe boot an older or newer kernel?

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2060976] Re: Create autopkgtest

2024-04-30 Thread Paride Legovini

There are issues with the proposed diff.

1. the d/changelog entry is not descriptive of what the added test does.
Please add something like (you'll know better):

 * d/tests: add basic connection test (LP: #)

2. the debdiff adds d/t/a.sh which is unused.

3. d/t/connect: better not specify shell options in the shebang, as that
get lost if the script is invoked with `sh /path/to/script`. Use `set`.

4. d/t/connect: isNaturalNumber() returns 0 on the empty string, but we
don't want that.

5. d/t/connect: this logic:

if isNaturalNumber "$port"; then
exit 1
fi

seems backwards to me: don't we want $port to be a natural number? FWIW
I think it's enough to check that it's a nonempty string ([ -n "$port"
]).

6. xrdp.service has WantedBy=multi-user.target. Why do we need to
manually `sudo systemctl start xrdp`?

7. Can we make the `timeout 4s` longer? In general, can you add a
comment on what we are testing more precisely?

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

Title:
  Create autopkgtest

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  Ran successfully with autopkgtest -B . -- schroot noble-amd64.

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


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

[Desktop-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format

** Changed in: policykit-1 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

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


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

[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1

2024-04-30 Thread Gabriel Nagy

Attached debdiff for adsys 0.14.1 backport to Mantic


** Patch added: "adsys_0.14.1~23.10.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+attachment/5773212/+files/adsys_0.14.1~23.10.debdiff

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

Title:
  [SRU] adsys 0.14.1

Status in adsys package in Ubuntu:
  Fix Released
Status in golang-1.22 package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  Confirmed
Status in golang-1.22 source package in Jammy:
  Confirmed

Bug description:
  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.

  Given that ADSys directly interfaces with Active Directory and needs
  to align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.

  Now that ADSys has a complete set of features, the request is to
  proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note
  that any new features introduced in subsequent versions will be
  exclusively available in 24.04 and later releases.

  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.

  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-
  desktop/+archive/ubuntu/adsys) and already used in production by
  customers.

  At this time of writing the number of open issues is 1 in Launchpad
  and 16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.

  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.

   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs

   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common

   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version

  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)

  * Dependencies to backport to 22.04:
    * golang-go >= 2:1.22
    * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will 
be disabled otherwise)
    * python3-cepces (suggest. Required for

[Desktop-packages] [Bug 2063221] Autopkgtest regression report (glib2.0/2.80.0-6ubuntu3)

2024-04-30 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted glib2.0 (2.80.0-6ubuntu3) for noble 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.28.1-0ubuntu2 (ppc64el)
cluster-glue/1.0.12-22.1ubuntu3 (ppc64el)
cpdb-backend-cups/2.0~b5-0ubuntu6 (armhf)
cpdb-libs/2.0~b5-1.2build1 (armhf)
dbus-test-runner/19.04.0-1build2 (arm64)
lasi/unknown (arm64)
libsoup2.4/2.74.3-6ubuntu1 (arm64, ppc64el)
mender-client/3.4.0+ds1-5build3 (armhf)
snapd-glib/1.64-0ubuntu5 (ppc64el, s390x)
software-properties/unknown (amd64, arm64, armhf, i386, ppc64el, s390x)
surf/2.1+git20221016-6build2 (armhf)
ymuse/0.22-1build2 (s390x)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#glib2.0

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

Thank you!

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  Fix Committed

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Technically, Steve Langasek already removed libglib2.0-0 from noble
  release just before release. This upload is necessary to ensure that
  we don't accidentally bring it back.

  Test Case
  -
  1. Is libglib2.0-0 built?

  2. Run rmadison libglib2.0-0
  There should be 0 results for noble, noble-proposed, or noble-updates

  3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu
  22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is
  currently set to disallow upgrades to 24.04 LTS. If this is still the
  case when it is time to verify this SRU, you can manually substitute
  jammy → noble in /etc/apt/sources.list for purposes of testing this
  upgrade, probably in a VM since that's not the supported way to
  upgrade.

  Where Problems Could Occur
  --
  Doing an upload to not build a package that already does not exist in Ubuntu 
24.04 LTS should have no regression potential. The only other change in this 
SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 
is also removed for people who were using Ubuntu 24.04 LTS early. That also 
should not cause problems since the package was an empty transitional package 
for early Ubuntu 24.04 LTS users.

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  removing the transitional package and some other workarounds in other
  packages, like in the transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

  We have landed the removal in Debian Unstable and it successfully
  migrated to Debian Testing on April 27 as one of the first t64
  packages to migrate there.

  The removal was recommended by Julian Klode, the apt maintainer for
  Debian and Ubuntu.

  The original transitional package was added by Simon McVittie in hopes
  that it would help apt be able to calculate the upgrade easier. At
  least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like
  it was the opposite. (Although that particular detail was fixed by the
  removal that already happened.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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

[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1

2024-04-30 Thread Gabriel Nagy

Attached debdiff for Go 1.22 backport to Mantic

** Patch added: "golang-1.22_1.22.2-2~23.10.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+attachment/5773187/+files/golang-1.22_1.22.2-2~23.10.debdiff

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

Title:
  [SRU] adsys 0.14.1

Status in adsys package in Ubuntu:
  Fix Released
Status in golang-1.22 package in Ubuntu:
  Fix Released
Status in adsys source package in Jammy:
  Confirmed
Status in golang-1.22 source package in Jammy:
  Confirmed

Bug description:
  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.

  Given that ADSys directly interfaces with Active Directory and needs
  to align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.

  Now that ADSys has a complete set of features, the request is to
  proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note
  that any new features introduced in subsequent versions will be
  exclusively available in 24.04 and later releases.

  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.

  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-
  desktop/+archive/ubuntu/adsys) and already used in production by
  customers.

  At this time of writing the number of open issues is 1 in Launchpad
  and 16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.

  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.

   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs

   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common

   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version

  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)

  * Dependencies to backport to 22.04:
    * golang-go >= 2:1.22
    * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will 
be disabled otherwise)
    * python3-cepces (suggest. Required for

[Desktop-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4

2024-04-30 Thread lotuspsychje

Thank you for filing this bug and make Ubuntu better!

In order to pull your logs and system info into this bug

please execute: apport-collect 2064275 from your terminal

so the developers can start debugging your bug a better way.

In the future please use ubuntu-bug yourpackage from a terminal.

Thank you!

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

Title:
  Blank screen after logging in Wayland using HP Thunderbolt G4

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

  After logging in using wayland, both monitors goes blank and then
  enters power saving mode.  If I replug the dock then the monitors wake
  up but with display settings reset.

  When using x-server, both screen work as normal after login
  remembering my screen placement etc.

  Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

  Ubuntu 24.04 with latest updtes installed.

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


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

[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

2024-04-30 Thread Heitor Alves de Siqueira

Marking as verified according to comment #21

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

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: software-properties (Ubuntu Mantic)
   Status: Confirmed => Invalid

** Changed in: software-properties (Ubuntu Noble)
   Status: Confirmed => Invalid

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

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Invalid
Status in ppa-purge source package in Mantic:
  Fix Committed
Status in software-properties source package in Mantic:
  Invalid
Status in ppa-purge source package in Noble:
  Fix Released
Status in software-properties source package in Noble:
  Invalid

Bug description:
  Thank you @jbicha for the original bug report!

  [ Impact ]

  Currently ppa-purge fails to purge packages on distribution using the deb822 
source format. Currently mantic and noble make use of this format and are 
affected by this issue.
  When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the 
custom PPA since it cannot disable deb822 sources and leads to apt still 
querying the ppa when running:

  $ apt update

  In older versions of ubuntu, PPAs used the ".list" format which could be 
disabled by simply commenting out the "deb" line with a "#". This was the 
method that ppa-purge used to disable PPAs.
  This new patch allows ppa-purge to detect and disable deb822 source files by 
adding an "Enabled: no" field in each component section of the deb822 file. It 
also removes any line that starts with "Enabled:"
  to make sure the resulting file is clean.

  [ Test Plan ]

  The changes were tested on both mantic and noble in a lxc container using the 
oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) 
as the test PPA.
  The following steps were recorded in a noble lxc container.

   - First make sure that mesa-utils is installed in your environment:
  $ sudo apt update && sudo apt install mesa-utils

   - Add the oibaf PPA to your system using the following command:
  $ sudo add-apt-repository ppa:oibaf/graphics-drivers

   - Make sure that the mesa-utils packages were upgraded after adding the PPA:
  $ sudo apt update && sudo apt upgrade
  $ dpkg - l | grep mesa

   - output should be similar to the following:

  ii  libegl-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the EGL API -- Mesa vendor library
  ii  libgl1-mesa-dri:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- DRI modules
  ii  libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the GL API -- shared library
  ii  libglx-mesa0:amd64  24.1~git2402280600.41722c~oibaf~n 
  amd64free implementation of the OpenGL API -- GLX vendor library
  ii  mesa-utils  9.0.0-2   
  amd64Miscellaneous Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd649.0.0-2   
  amd64Miscellaneous Mesa utilities -- native applications
  ii  mesa-vulkan-drivers:amd64   24.1~git2402280600.41722c~oibaf~n 
  amd64Mesa Vulkan graphics drivers


   - Install and run ppa-purge:
  $ sudo apt install ppa-purge
  $ sudo ppa-purge ppa:oibaf/graphics-drivers

   - ppa-purge will report at the end that none of the oibaf packages
  need to be downgraded/removed:

  
  libglapi-mesa is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglapi-mesa set to manually installed.
  libglx-mesa0 is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  libglx-mesa0 set to manually installed.
  mesa-vulkan-drivers is already the newest version 
(24.1~git2402280600.41722c~oibaf~n).
  mesa-vulkan-drivers set to manually installed.
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1'
  Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open 
Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2'
  Selected version

[Desktop-packages] [Bug 2064169] Re: Keyboard shortcuts

2024-04-30 Thread Tomaz Henrique

I turned on the computer this morning, and the shortcut I made using the
"super+down" key to reduce the computer's sound volume did not work
correctly. "super+up" worked as expected, it increases my sound volume,
but "super+down" didn't work. It seems that when restarting the
computer, there is a misconfiguration of the shortcut keys I created.

org.gnome.TextEditor keybindings 'default'
org.gnome.desktop.wm.keybindings activate-window-menu ['space']
org.gnome.desktop.wm.keybindings always-on-top @as []
org.gnome.desktop.wm.keybindings begin-move ['F7']
org.gnome.desktop.wm.keybindings begin-resize ['F8']
org.gnome.desktop.wm.keybindings close ['F4']
org.gnome.desktop.wm.keybindings cycle-group ['F6']
org.gnome.desktop.wm.keybindings cycle-group-backward ['F6']
org.gnome.desktop.wm.keybindings cycle-panels ['Escape']
org.gnome.desktop.wm.keybindings cycle-panels-backward 
['Escape']
org.gnome.desktop.wm.keybindings cycle-windows ['Escape']
org.gnome.desktop.wm.keybindings cycle-windows-backward ['Escape']
org.gnome.desktop.wm.keybindings lower @as []
org.gnome.desktop.wm.keybindings maximize ['Up']
org.gnome.desktop.wm.keybindings maximize-horizontally @as []
org.gnome.desktop.wm.keybindings maximize-vertically @as []
org.gnome.desktop.wm.keybindings minimize ['h']
org.gnome.desktop.wm.keybindings move-to-center @as []
org.gnome.desktop.wm.keybindings move-to-corner-ne @as []
org.gnome.desktop.wm.keybindings move-to-corner-nw @as []
org.gnome.desktop.wm.keybindings move-to-corner-se @as []
org.gnome.desktop.wm.keybindings move-to-corner-sw @as []
org.gnome.desktop.wm.keybindings move-to-monitor-down ['Down']
org.gnome.desktop.wm.keybindings move-to-monitor-left ['Left']
org.gnome.desktop.wm.keybindings move-to-monitor-right ['Right']
org.gnome.desktop.wm.keybindings move-to-monitor-up ['Up']
org.gnome.desktop.wm.keybindings move-to-side-e @as []
org.gnome.desktop.wm.keybindings move-to-side-n @as []
org.gnome.desktop.wm.keybindings move-to-side-s @as []
org.gnome.desktop.wm.keybindings move-to-side-w @as []
org.gnome.desktop.wm.keybindings move-to-workspace-1 ['Home']
org.gnome.desktop.wm.keybindings move-to-workspace-10 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-11 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-12 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-2 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-3 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-4 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-5 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-6 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-7 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-8 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-9 @as []
org.gnome.desktop.wm.keybindings move-to-workspace-down 
['Down']
org.gnome.desktop.wm.keybindings move-to-workspace-last ['End']
org.gnome.desktop.wm.keybindings move-to-workspace-left 
['Page_Up', 'Left', 
'Left']
org.gnome.desktop.wm.keybindings move-to-workspace-right 
['Page_Down', 'Right', 
'Right']
org.gnome.desktop.wm.keybindings move-to-workspace-up 
['Up']
org.gnome.desktop.wm.keybindings panel-main-menu ['F1']
org.gnome.desktop.wm.keybindings panel-run-dialog ['F2']
org.gnome.desktop.wm.keybindings raise @as []
org.gnome.desktop.wm.keybindings raise-or-lower @as []
org.gnome.desktop.wm.keybindings set-spew-mark @as []
org.gnome.desktop.wm.keybindings show-desktop ['d', 
'd', 'd']
org.gnome.desktop.wm.keybindings switch-applications ['Tab']
org.gnome.desktop.wm.keybindings switch-applications-backward 
['Tab']
org.gnome.desktop.wm.keybindings switch-group ['Above_Tab', 
'Above_Tab']
org.gnome.desktop.wm.keybindings switch-group-backward 
['Above_Tab', 'Above_Tab']
org.gnome.desktop.wm.keybindings switch-input-source ['space', 
'XF86Keyboard']
org.gnome.desktop.wm.keybindings switch-input-source-backward 
['space', 'XF86Keyboard']
org.gnome.desktop.wm.keybindings switch-panels ['Tab']
org.gnome.desktop.wm.keybindings switch-panels-backward 
['Tab']
org.gnome.desktop.wm.keybindings switch-to-workspace-1 ['Home']
org.gnome.desktop.wm.keybindings switch-to-workspace-10 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-11 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-12 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-2 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-3 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-4 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-5 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-6 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-7 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-8 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-9 @as []
org.gnome.desktop.wm.keybindings switch-to-workspace-down ['Down']
org.gnome.desktop.wm.keybindings switch-to-workspace-last ['End']
org.gnome.desktop.wm.keybindings switch-to-workspace-left ['Page_Up',

[Desktop-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

2024-04-30 Thread Treviño

** Description changed:

+ [ Impact ]
+ 
  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of the
  screen without proper theming.
  
  See attached image.
+ 
+ [ Test case ]
+ 
+ Note: this only tests the appindicator-side that may have lead to
+ "activating" the application, it's not something that will fix the
+ applications issues that is a QT bug.
+ 
+ 1. Start a QT application with indicator
+(after gnome-shell has started; e.g. clementine, barrier...)
+ 2. The applindicator menu with shell theme should appear
+ 3. No activation happens on the application (e.g. the window is not opened)
+ 
+ [ Regression potential ]
+ 
+ Mouse events aren't properly exposed to the indicators

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Fix Committed

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

** Also affects: qtbase-opensource-src (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Committed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell-extension-appindicator source package in Noble:
  New
Status in qtbase-opensource-src source package in Noble:
  New

Bug description:
  [ Impact ]

  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

  [ Test case ]

  Note: this only tests the appindicator-side that may have lead to
  "activating" the application, it's not something that will fix the
  applications issues that is a QT bug.

  1. Start a QT application with indicator
 (after gnome-shell has started; e.g. clementine, barrier...)
  2. The applindicator menu with shell theme should appear
  3. No activation happens on the application (e.g. the window is not opened)

  [ Regression potential ]

  Mouse events aren't properly exposed to the indicators

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

So I tried it in a flatpak-installation of TB, too: At startup, all
mboxes are displayed just fine. But when I try to import the large mbox-
file by hand, it's also imported just partly and journalctl -f logs the
errors I just posted above.

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

When trying to import the large mbox-file (2,4Gb) using
ImportExportTools, journalctl -f logs:

Apr 30 13:55:44 knut kernel: nvme0n1: I/O Cmd(0x2) @ LBA 106160824, 8 blocks, 
I/O Error (sct 0x2 / sc 0x81) 
Apr 30 13:55:44 knut kernel: critical medium error, dev nvme0n1, sector 
106160824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 30 13:55:44 knut kernel: nvme0n1: I/O Cmd(0x2) @ LBA 106160824, 8 blocks, 
I/O Error (sct 0x2 / sc 0x81) 
Apr 30 13:55:44 knut kernel: critical medium error, dev nvme0n1, sector 
106160824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 30 13:55:44 knut kernel: nvme0n1: I/O Cmd(0x2) @ LBA 106160824, 8 blocks, 
I/O Error (sct 0x2 / sc 0x81) 
Apr 30 13:55:44 knut kernel: critical medium error, dev nvme0n1, sector 
106160824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 30 13:55:44 knut kernel: nvme0n1: I/O Cmd(0x2) @ LBA 106160824, 8 blocks, 
I/O Error (sct 0x2 / sc 0x81) 
Apr 30 13:55:44 knut kernel: critical medium error, dev nvme0n1, sector 
106160824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 30 13:55:44 knut kernel: nvme0n1: I/O Cmd(0x2) @ LBA 106160824, 8 blocks, 
I/O Error (sct 0x2 / sc 0x81) 
Apr 30 13:55:44 knut kernel: critical medium error, dev nvme0n1, sector 
106160824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
  

This does not appear when opening thunderbird via terminal, yet it
sounds like a hardware problem, right?

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

here we go:

knut@knut:~$ thunderbird
[ImapModuleLoader] Using nsImapService.cpp

(thunderbird:1240551): Gtk-WARNING **: 13:48:05.619: Failed to parse 
/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini: Permission denied
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 
unprotected)"
console.log: "IETNG: mboxImportModule.js -v4"
console.log: "IETNG: mboximportExport.js -v4"
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: 
NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: 
NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: 
NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: chrome://mboximport/content/mboximport/messengerOL.js, line 
178: TypeError: console is not a function
JavaScript error: resource://services-settings/Utils.sys.mjs, line 245: 
TypeError: Headers.set: cf_use_ob=443; path=/; expires=tue, 30-apr-24 11:48:47 
gmt is an invalid header name.
[Parent 1240551, Main Thread] WARNING: atk-bridge: get_device_events_reply: 
unknown signature: 'glib warning', file 
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167

** (thunderbird:1240551): WARNING **: 13:48:32.105: atk-bridge: 
get_device_events_reply: unknown signature
^CExiting due to channel error.


I started journalctl -f before thunderbird and then started thunderbird from 
command line: 

knut@knut:~$ journalctl -f
Apr 30 13:44:12 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:44:12 knut rtkit-daemon[4435]: Successfully made thread 1231631 of 
process 1230985 owned by '1000' RT at priority 10.
Apr 30 13:44:12 knut rtkit-daemon[4435]: Supervising 9 threads of 6 processes 
of 1 users.
Apr 30 13:44:12 knut kernel: audit: type=1400 audit(1714477452.284:378): 
apparmor="DENIED" operation="mknod" class="file" 
profile="snap.thunderbird.thunderbird" 
name="/home/knut/.local/share/fonts/.uuid.TMP-HqDZsr" pid=1231621 
comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c" fsuid=1000 
ouid=1000
Apr 30 13:45:01 knut CRON[1233526]: pam_unix(cron:session): session opened for 
user root(uid=0) by root(uid=0)
Apr 30 13:45:01 knut CRON[1233535]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Apr 30 13:45:01 knut CRON[1233526]: pam_unix(cron:session): session closed for 
user root
Apr 30 13:47:26 knut kernel: lxterminal[1229240]: segfault at 78 ip 
55cc72cc4ed8 sp 7ffd962ac920 error 4 in lxterminal[55cc72cc+9000] 
likely on CPU 2 (core 2, socket 0)
Apr 30 13:47:26 knut kernel: Code: 66 90 f3 0f 1e fa 55 48 89 f7 48 89 e5 53 48 
89 f3 48 83 ec 08 e8 e8 fc ff ff 85 c0 75 15 eb 1e 66 90 48 8b 00 31 f6 48 8b 
10 <48> 8b 7a 38 e8 3f fe ff ff 48 8b 43 40 8b 50 08 85 d2 75 e4 48 8b
Apr 30 13:47:26 knut systemd[4396]: 
snap.thunderbird.thunderbird-7fc8e35c-83fa-4eac-90db-93ce75bd6442.scope: 
Consumed 29.737s CPU time.
Apr 30 13:48:05 knut systemd[4396]: Started 
snap.thunderbird.thunderbird-3b35f818-0478-4153-9163-1d2dfd77d062.scope.
Apr 30 13:48:05 knut kernel: audit: type=1400 audit(1714477685.613:379): 
apparmor="DENIED" operation="open" class="file" 
profile="snap.thunderbird.thunderbird" 
name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=1240551 
comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 30 13:48:05 knut kernel: audit: type=1400 audit(1714477685.761:380): 
apparmor="DENIED" operation="mknod" class="file" 
profile="snap.thunderbird.thunderbird" 
name="/home/knut/.local/share/fonts/.uuid.TMP-NFd59b" pid=1240551 
comm=5B70616E676F5D204663496E6974 requested_mask="c" denied_mask="c" fsuid=1000 
ouid=1000
Apr 30 13:48:06 knut dbus-daemon[4421]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/a11y/bus" 
interface="org.freedesktop.DBus.Properties" member="Get" mask="send" 
name="org.a11y.Bus" pid=1240551 label="snap.thunderbird.thunderbird" 
peer_pid=4523 peer_label="unconfined"
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 8 threads of 5 processes 
of 1 users.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Successfully made thread 1241201 of 
process 1240551 owned by '1000' RT at priority 10.
Apr 30 13:48:07 knut rtkit-daemon[4435]: Supervising 9 threads of 6 processes 
of 1 users.
Apr 30 13:48:07 knut

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

2024-04-30 Thread Tobias Heider

> Was it it more than a red line in systemctl status output? Does it
have annoying logging behaviour or break some other service if it isn't
running?

Red lines and an avoidable boot delay while trying to restart and
failing a bunch of times.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS

2024-04-30 Thread Miroslav Zaťko

Triggering if-up.d scripts changed completely without mention in documentation.
For 23.10 scripts was triggered for each network interface separately. On boot 
it was with

* PHASE=post-up, IFACE=lo;
* PHASE=post-up, IFACE=virbr0;
* PHASE=post-up, IFACE=enx047bcb671ca9;
* PHASE=post-up, IFACE=docker0;
* PHASE=post-up, IFACE=wlp0s20f3

Later on connecting to openconnect/anyconnect it was triggered with
* PHASE=post-up, IFACE=vpn0


After upgrade to 24.04 it is triggered on boot only with:
* PHASE=post-up, IFACE=lo;
* PHASE=post-up, IFACE=-all

Nothing triggered after connecting to openconnect/anyconnect

https://bugs.launchpad.net/openconnect/+bug/2064028

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

Title:
  if-up.d files do not have effect on ubuntu 24.04 LTS

Status in ifupdown package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Some time ago I wrote a detailed answer to fix an error for lowering
  MTU size for a cisco-compatible VPN
  (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
  into-remote-machine-but-able-to-ping-vpnc/768758#768758)

  After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to
  lower the MTU size.

  In particular, if I run the following command from the terminal

  sudo ifconfig your_tunnel_name mtu 1370 up

  it seems to lower the MTU size.

  However, the script under /etc/network/if-up.d is not automatically
  triggered.

  Does something change with the newer Ubuntu version?

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


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

[Desktop-packages] [Bug 2064277] [NEW] NetworkManager, default IPv4 route always through wifi, even if wired available

2024-04-30 Thread Lionel Jeanson

Public bug reported:

If wifi is connected, the default IPv4 route is always through wifi, no
route through wired connection is set up, even if wired faster, and
connected to the same gw. The default IPv6 route is ok. Tested on a
fresh install, same behavior.

lionel@lionelux:~$ ip addr 
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute 
   valid_lft forever preferred_lft forever
2: wlo1:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 70:a8:d3:dc:fa:05 brd ff:ff:ff:ff:ff:ff
altname wlp0s20f3
inet 10.0.0.66/24 brd 10.0.0.255 scope global dynamic noprefixroute wlo1
   valid_lft 7153sec preferred_lft 7153sec
inet6 2a01:e0a:51a:50d1:c4f5:20d5:51a:3666/64 scope global temporary 
dynamic 
   valid_lft 604755sec preferred_lft 86110sec
inet6 2a01:e0a:51a:50d1:3c79:4f2b:d7f1:a0d/64 scope global mngtmpaddr 
noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::e2e1:a4d7:bb8c:961a/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
3: virbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether 52:54:00:4d:6c:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
   valid_lft forever preferred_lft forever
9: enx908d6e354c47:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000
link/ether 90:8d:6e:35:4c:47 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.65/24 brd 10.0.0.255 scope global dynamic noprefixroute 
enx908d6e354c47
   valid_lft 7174sec preferred_lft 7174sec
inet6 2a01:e0a:51a:50d1:7c69:4bd8:2924:9ff8/64 scope global temporary 
dynamic 
   valid_lft 604775sec preferred_lft 86178sec
inet6 2a01:e0a:51a:50d1:c87c:7002:3ad2:496e/64 scope global mngtmpaddr 
noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::ba1:bdae:e9c3:f29f/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
10: enx186571a0c6a4:  mtu 1500 qdisc 
pfifo_fast state DOWN group default qlen 1000
link/ether 18:65:71:a0:c6:a4 brd ff:ff:ff:ff:ff:ff

lionel@lionelux:~$ ip route
default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.66 metric 600 
10.0.0.0/24 dev wlo1 proto kernel scope link src 10.0.0.66 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 

lionel@lionelux:~$ ip -6 route
2a01:e0a:51a:50d1::/64 dev enx908d6e354c47 proto ra metric 100 pref medium
2a01:e0a:51a:50d1::/64 dev wlo1 proto ra metric 600 pref medium
fe80::/64 dev wlo1 proto kernel metric 1024 pref medium
fe80::/64 dev enx908d6e354c47 proto kernel metric 1024 pref medium
default via fe80::8b6b:4e44:c003:cca6 dev wlo1 proto ra metric 600 pref medium
default via fe80::8b6b:4e44:c003:cca6 dev enx908d6e354c47 proto ra metric 20100 
pref medium

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 13:09:23 2024
InstallationDate: Installed on 2024-02-09 (81 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
IpRoute:
 default via 10.0.0.1 dev enx908d6e354c47 proto dhcp src 10.0.0.65 metric 100 
 default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.66 metric 600 
 10.0.0.0/24 dev enx908d6e354c47 proto kernel scope link src 10.0.0.65 metric 
100 
 10.0.0.0/24 dev wlo1 proto kernel scope link src 10.0.0.66 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
SourcePackage: network-manager
UpgradeStatus: Upgraded to noble on 2024-04-25 (5 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2024-02-14T13:52:12.489815
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.46.0   connected  started  full  enabled enabled  
enabled  missing  enabled

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


** Tags: amd64 apport-bug noble

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

Title:
  NetworkManager, default IPv4 route always through wifi, even if wired
  available

Status in network-manager package in Ubuntu:
  New

Bug description:
  If wifi is connected, the default IPv4 route is always through wifi,
  no route through

[Desktop-packages] [Bug 2064276] [NEW] 24.04 : Alsa : Missing 5.1 outputs

2024-04-30 Thread Lionel Jeanson

Public bug reported:

alsa-driver or alsa-topology, 5.1 digital surround IEC958 are not
available, they were on 23.10.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 13:03:05 2024
InstallationDate: Installed on 2024-02-09 (81 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: Micro-Star International Co., Ltd. Summit E13FlipEvo A13MT
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to noble on 2024-04-25 (5 days ago)
dmi.bios.date: 03/29/2023
dmi.bios.release: 5.7
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E13P3IMS.507
dmi.board.asset.tag: Default string
dmi.board.name: MS-13P3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE13P3IMS.507:bd03/29/2023:br5.7:svnMicro-StarInternationalCo.,Ltd.:pnSummitE13FlipEvoA13MT:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-13P3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku13P3.5:
dmi.product.family: Summit
dmi.product.name: Summit E13FlipEvo A13MT
dmi.product.sku: 13P3.5
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2024-02-14T13:52:12.489815

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  24.04 : Alsa : Missing 5.1 outputs

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  alsa-driver or alsa-topology, 5.1 digital surround IEC958 are not
  available, they were on 23.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 13:03:05 2024
  InstallationDate: Installed on 2024-02-09 (81 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: Micro-Star International Co., Ltd. Summit E13FlipEvo A13MT
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to noble on 2024-04-25 (5 days ago)
  dmi.bios.date: 03/29/2023
  dmi.bios.release: 5.7
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E13P3IMS.507
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-13P3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE13P3IMS.507:bd03/29/2023:br5.7:svnMicro-StarInternationalCo.,Ltd.:pnSummitE13FlipEvoA13MT:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-13P3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku13P3.5:
  dmi.product.family: Summit
  dmi.product.name: Summit E13FlipEvo A13MT
  dmi.product.sku: 13P3.5
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2024-02-14T13:52:12.489815

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


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

[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap

@Pablo, thanks. then it's another issue than the one reported here,
let's move to bug #2062133 instead.

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

Title:
  Thunderbird profile not migrated to snap

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Today's update installed the thunderbird snap and removed the
  thunderbird binary but it did not migrate my thunderbird profile.

  Now I don't have access to any old mails anymore.

  Looking at ~/.thunderbird:

  $ cat profiles.ini 
  [Profile1]
  Name=default
  IsRelative=1
  Path=ao6t0qef.default
  Default=1

  [InstallFDC34C9F024745EB]
  Default=ji04wv64.default-release
  Locked=1

  [Profile0]
  Name=default-release
  IsRelative=1
  Path=ji04wv64.default-release

  [General]
  StartWithLastProfile=1
  Version=2

  
  ji04wv64.default-release is the folder that should have been migrated.

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


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

[Desktop-packages] [Bug 2064039] Re: TB Snap fails to import/display large mbox-file completely

Thank you for your bug report. It would be weird if the issue was
specific to the snap, perhaps a problem from the new upstream version.
Do you get any warning/error on stdout/stderr if you start thunderbird
from a command line?

Could you also do 
$ journalctl -f

and try to import the mbox and see if there is anything relevant logged?

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

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

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

Title:
  TB Snap fails to import/display large mbox-file completely

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I use TB 115.10.1 (snap) since today, after a system upgrade of
  Lubuntu 23.10 to 24.04 via terminal. All was fine before the update. I
  use Pop, no Imap. Transition to TB snap seemed fine but one the
  various mbox-files was not properly imported/displayed. All attempts
  to properly import it by hand failed. The mbox-file is ~2.4 GB
  containing a large archive of e-mails from 2013 on, yet just ~1.4GB
  are displayed. When I try to import the file, it seems to start but
  then no e-mails are actually imported. So I see not all e-mails in my
  inbox (the last 3 years are missing). All my other mbox-files are much
  smaller - and they're all fine.

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


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

[Desktop-packages] [Bug 2056772] Re: Properties of Audio Files Causes Lock Ups

The issue has been fixed upstream now,

https://gitlab.gnome.org/GNOME/nautilus/-/commit/ced65980

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

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

Title:
  Properties of Audio Files Causes Lock Ups

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  On SMB mounted file systems, right click properties on audio files
  causes the Nautilus to freeze. Force/Wait appears.

  The file system has read/write permission. Happens every time for
  large .flac files.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46~beta-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 11 10:33:22 2024
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'recursive-search' b"'always'"
   b'org.gnome.nautilus.preferences' b'show-directory-item-counts' b"'always'"
   b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1241, 1039)'
  InstallationDate: Installed on 2022-04-07 (704 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00
  usr_lib_nautilus:
   file-roller   43.1-1
   nautilus-extension-gnome-terminal 3.51.90-1ubuntu1
   nautilus-share0.7.5-0.3

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


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

[Desktop-packages] [Bug 2063892] Re: How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nautilus (Ubuntu)
   Status: New => Triaged

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

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

Title:
  How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Hi !

  For few months I'm getting used to « starred » items in Nautilus /
  Ubuntu 22.04.

  To my surprise I can't find how to do the same in 24.04,

  looks like the option for « starring » an element is missing in
  context menu.

  It's a default install of 24.04 hence « minimal » so maybe I'm missing
  a package ?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 27 00:45:55 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1040, 667)'
  InstallationDate: Installed on 2024-04-25 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

[Desktop-packages] [Bug 2063992] Re: thumbnails are not shown

Thank you for your bug report. Is that specific to some format or
directory? Where are thumbnails not showing, in the viewer itself or in
the filemanager?

Concerning the version, 45 is the current upstream eog version
https://gitlab.gnome.org/GNOME/eog/-/tags

GNOME switched to use 'loupe' which is a different software (new project
written in rust) which we didn't switch to this cycle in Ubuntu because
it has a more limited feature set that eog at this point. The fact that
thumbnails aren't working hasn't to do with that though

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

Title:
  thumbnails are not shown

Status in eog package in Ubuntu:
  Incomplete

Bug description:
  I firstly reported to gnome directly to
  https://gitlab.gnome.org/GNOME/loupe/-/issues/359
  All details there.
  But now i see that real issue that someone decides to leave 45's version of 
eog on gnome's 46 one. 
  On fedora on the same machine everything works fine. 
  Personally i don't understand how version control of packages is done in 
release version of os!

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: eog 45.3-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 28 11:06:49 2024
  SourcePackage: eog
  UpgradeStatus: Upgraded to noble on 2024-04-26 (2 days ago)

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


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

[Desktop-packages] [Bug 2063986] Re: no "send to..." in the nautilus context menu

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

Thanks, in fact the item is there but named 'Email...' but it doesn't
work as expected which you already saw since you commented on the
existing report bug #1996927. I'm going to mark that one as duplicate.
We added back nautilus-sendto with the intend to change nautilus back to
use it instead of the xd-desktop-portal but just didn't get to do the
nautilus side of the changes in time for release.


** Changed in: nautilus-sendto (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus-sendto (Ubuntu)
   Status: New => Confirmed

** This bug has been marked a duplicate of bug 1996927
   Nautilus send mail not working

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

Title:
  no "send to..." in the nautilus context menu

Status in nautilus-sendto package in Ubuntu:
  Confirmed

Bug description:
  hi,
  In ubuntu 24.04, nautilus-sendto is included in the installation. But it has 
no effect on nautilus.

  In nautilus, click on a file, then right click on it and there is no
  "send to..." in the context menu so there is no way to send a file to
  thunderbird from nautilus as expected

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


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

Removing /dev/dri/card0 and re-login makes it work. So its the
https://bugs.launchpad.net/bugs/2060268

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

2024-04-30 Thread Leo Didier

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

Same for me, the upgrade went horribly also wrong...

But i could get everything on track again from the terminal with a complete 
update and upgrade the missing packages.
Did not have to do install systemd-resolved as i already had the latest 
installed.

Then in Ubuntu 24 desktop i had troubles with long minutes hanging on a grey 
screen, firefox freeze at start up and other desktop freezes..
A snap store refresh did the job with 'sudo snap refresh snap-store' and 
everything is working fine now !

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

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


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

[Desktop-packages] [Bug 2064213] [NEW] Release BlueZ 5.75 to Oracular

Public bug reported:

Release BlueZ 5.75 to Oracular:
https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz

** Affects: bluez (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: Triaged


** Tags: oracular

** Changed in: bluez (Ubuntu)
Milestone: None => ubuntu-24.10

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

Title:
  Release BlueZ 5.75 to Oracular

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Release BlueZ 5.75 to Oracular:
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz

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


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

[Desktop-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install

Here's the fix for Oracular.

** Changed in: mesa (Ubuntu)
Status: Confirmed => Won't Fix

** Patch added: "webkit2gtk_2.44.0-2ubuntu1.debdiff"

https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2037015/+attachment/5772919/+files/webkit2gtk_2.44.0-2ubuntu1.debdiff

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

Title:
Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
during install

Status in Webkit:
Confirmed
Status in mesa package in Ubuntu:
Won't Fix
Status in webkit2gtk package in Ubuntu:
In Progress

Bug description:
[ Impact ]

Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
during install.

[ Test Plan ]

1. Log into a Xorg session on a Raspberry Pi 4/400.

2. Open the default Help app by clicking the question mark icon in the
dock or by running 'yelp'.

3. Verify it didn't crash and the window contents are not corrupt.

[ Where problems could occur ]

The fix is limited to webkit2gtk so can only affect apps such as yelp
or the Raspberry Pi installer.

[ Other Info ]

During the initial configuration of the Ubuntu Desktop for Raspberry
Pi (the oem-config process, derived from ubiquity), on the Mantic beta
images, after the various pages of information have been filled out
and the process moves onto configuration, the "slide deck" that is
usually displayed during the process appeared corrupted as if a
horizontal stride were incorrectly set somewhere.

I'm attached a photo of the screen (as, while I could take a
screenshot during the process, it evidently wasn't saved somewhere
persistent).

I originally thought this might be a regression of LP: #1924251 as the
corruption in the window looks very similar (incorrect horizontal
stride causing "banding"), but I tested the embedded browser (via the
help system) after completing setup and it worked perfectly so that's
*probably* unrelated.

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

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

[Desktop-packages] [Bug 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

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

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

Title:
  Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Won't Fix
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  MiniBrowser crashed immediately on Raspberry Pi 400.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1
  Uname: Linux 6.8.0-1002-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:32:12 2024
  ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser
  JournalErrors: -- No entries --
  ProcCmdline: ./MiniBrowser
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: webkit2gtk
  StacktraceTop:
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /lib/aarch64-linux-gnu/libgbm.so.1
   ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
  Title: MiniBrowser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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

[Desktop-packages] [Bug 2064099] Re: Quickly switching right and left clicks freezes Nautilus

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

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

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

Title:
  Quickly switching right and left clicks freezes Nautilus

Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  1. Open Nautilus.
  2. Try to right click and left click randomly and quickly.

  This behavior will freeze Nautilus until you must kill it and it
  happens every time you do this, and you cannot even move it's window.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 12:42:46 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
  InstallationDate: Installed on 2024-03-22 (38 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

[Desktop-packages] [Bug 2064099] Re: Quickly switching right and left clicks freezes Nautilus

2024-04-30 Thread Islam

Disabling the extension didn't solve the issue.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064099/+attachment/5772876/+files/journal.txt

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

Title:
  Quickly switching right and left clicks freezes Nautilus

Status in mutter package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  1. Open Nautilus.
  2. Try to right click and left click randomly and quickly.

  This behavior will freeze Nautilus until you must kill it and it
  happens every time you do this, and you cannot even move it's window.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:46.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 12:42:46 2024
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
  InstallationDate: Installed on 2024-03-22 (38 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago)
  usr_lib_nautilus:
   file-roller   44.1-1
   nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

[Desktop-packages] [Bug 2064205] [NEW] Optimize cross-GPU multi-monitor syncs

Public bug reported:

Optimize cross-GPU multi-monitor syncs still slowing down Nvidia
secondary GPUs on Wayland per:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304#note_1860864

** Affects: mutter (Ubuntu)
 Importance: Wishlist
 Assignee: Daniel van Vugt (vanvugt)
 Status: Triaged


** Tags: hybrid multigpu multimonitor nvidia nvidia-wayland performance wayland 
wayland-session

** Tags added: nvidia-wayland

** Changed in: mutter (Ubuntu)
Milestone: None => ubuntu-24.10

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

Title:
  Optimize cross-GPU multi-monitor syncs

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Optimize cross-GPU multi-monitor syncs still slowing down Nvidia
  secondary GPUs on Wayland per:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304#note_1860864

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


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

The xrandr output looks correct but the attached MonitorsUser.xml.txt
looks suspicious in that it confirms the monitors don't have any
separate positional information. If deleting monitors.xml didn't work
then next please try:

1. sudo rm /dev/dri/card0 # (should be the "Unknown Display")
2. rm ~/.config/monitors.xml
3. Log in again.

If that works then the issue is just bug 2060268. And unfortunately
deleting /dev/dri/card0 will only last until the next reboot.

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  [Xorg] Large performance regression in fullscreen windows

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

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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

[Desktop-packages] [Bug 2061739] Re: crash in meta_wayland_transaction_commit

2024-04-30 Thread Bug Watch Updater

** Changed in: mutter
   Status: Unknown => New

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

Title:
  crash in meta_wayland_transaction_commit

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

Bug description:
  Hi,

  The system is Ubuntu Noble with a regular daily updates.
  This happens many times since few days ago but not clear
  at all how to reproduce it.

  Regards,
  Patrice

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Apr 16 09:26:16 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-05-24 (1789 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago)

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


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

I have restarted system after removing monitors.xml.

The third one on the list is "Unknown Display".

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

Actually xrandr show 3 displays:

Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 
477mm x 268mm panning 3840x1080+0+0 tracking 5760x1080+0+0 border 0/0/0/0
   1920x1080 60.00*+  59.9450.0060.0050.04  
   1680x1050 59.95  
   1440x900  74.9859.89  
   1440x576  50.00  
   1280x1024 75.0260.02  
   1280x960  60.00  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0370.0760.00  
   800x600   75.0060.3256.25  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0072.8159.9459.93  
DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
510mm x 287mm panning 3840x1080+1920+0 tracking 5760x1080+0+0 border 0/0/0/0
   1920x1080 60.00*+
   1680x1050 59.95  
   1440x900  74.9859.89  
   1280x1024 75.0260.02  
   1280x720  60.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   640x480   75.0072.8159.94  
DP-1 disconnected (normal left inverted right x axis y axis)
None-1-1 connected (normal left inverted right x axis y axis)
   1920x1080 60.00 +

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers:

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

Did you log in again after deleting the file?

Is one of the two different names "Unknown Display"?

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

Removing ~/.config/monitors.xml doesn't help.

In the "Settings -> Display" I see two different names. Both monitors
are recognized.

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2038801] Re: Secondary GPU frame rates are held back by dynamic-max-render-time

** Description changed:

+ [ Impact ]
+ 
  Secondary GPU frame rates are held back by dynamic-max-render-time as
  shown on this amdgpu setup connected to a 60 Hz monitor:
  
  main: 30 FPS
  main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS
  
  https://gitlab.gnome.org/GNOME/mutter/-/issues/3070
+ 
+ [ Test Plan ]
+ 
+ This is imprecise because many machines won't exhibit a measurable
+ difference...
+ 
+ 1. Set up a dual GPU machine with dual monitors using an open source
+ driver such as amdgpu or nouveau. If you are using Mutter 46 or later
+ then the closed source Nvidia driver may also be used in theory.
+ 
+ 2. In a Wayland session, check that the frame rate being achieved on the
+ monitor connected to the secondary GPU is at least that of the refresh
+ rate.
+ 
+ 3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to /etc/environment
+ and reboot.
+ 
+ 4. In a Wayland session, check that the frame rate on the monitor
+ connected to the secondary GPU has not changed (didn't get better) after
+ the environment change.
+ 
+ 5. Remove the change from /etc/environment.
+ 
+ [ Where problems could occur ]
+ 
+ Anywhere in frame scheduling and frame rate performance, since that is
+ what changed.
+ 
+ [ Other Info ]

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

Title:
  Secondary GPU frame rates are held back by dynamic-max-render-time

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

  Secondary GPU frame rates are held back by dynamic-max-render-time as
  shown on this amdgpu setup connected to a 60 Hz monitor:

  main: 30 FPS
  main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS

  https://gitlab.gnome.org/GNOME/mutter/-/issues/3070

  [ Test Plan ]

  This is imprecise because many machines won't exhibit a measurable
  difference...

  1. Set up a dual GPU machine with dual monitors using an open source
  driver such as amdgpu or nouveau. If you are using Mutter 46 or later
  then the closed source Nvidia driver may also be used in theory.

  2. In a Wayland session, check that the frame rate being achieved on
  the monitor connected to the secondary GPU is at least that of the
  refresh rate.

  3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to
  /etc/environment and reboot.

  4. In a Wayland session, check that the frame rate on the monitor
  connected to the secondary GPU has not changed (didn't get better)
  after the environment change.

  5. Remove the change from /etc/environment.

  [ Where problems could occur ]

  Anywhere in frame scheduling and frame rate performance, since that is
  what changed.

  [ Other Info ]

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


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

[Desktop-packages] [Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

** Description changed:

+ [ Impact ]
+
+ GNOME Wayland session crashes with
+
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
+ assertion failed: (logical_monitor)
+
+ [ Test Plan ]
+
+ This needs more detail and community help...
+
+ 1. On a machine that was previously affected by the crash, disconnect
+ the HDMI cable.
+
+ Expect: The shell has not crashed and continues to function.
+
+ [ Where problems could occur ]
+
+ Potentially anywhere in Gnome Shell. Judging by the fix it relates to
+ automatic window placement when monitors are added and removed.
+
+ [ Original description ]
+
I am observing multiple issues with external monitor in a hybrid system
(laptop) with Intel GPU and NVIDIA GPU in a Gnome session:

- Disconnecting HDMI cable crashes the desktop to login screen

The HDMI port is connected to NVIDIA. I use the latest updates and
drivers of 22.04 LTS.

I am not sure how to auto-report this with ubuntu-bug. The system is
similar to this report:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291

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

Title:
GNOME Wayland session crashes with

libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
assertion failed: (logical_monitor)

Status in Gnome Shell Extension Tiling Assistant:
New
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Committed

Bug description:
[ Impact ]

GNOME Wayland session crashes with

libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
assertion failed: (logical_monitor)

[ Test Plan ]

This needs more detail and community help...

1. On a machine that was previously affected by the crash, disconnect
the HDMI cable.

Expect: The shell has not crashed and continues to function.

[ Where problems could occur ]

Potentially anywhere in Gnome Shell. Judging by the fix it relates to
automatic window placement when monitors are added and removed.

[ Original description ]

I am observing multiple issues with external monitor in a hybrid
system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session:

- Disconnecting HDMI cable crashes the desktop to login screen

The HDMI port is connected to NVIDIA. I use the latest updates and
drivers of 22.04 LTS.

I am not sure how to auto-report this with ubuntu-bug. The system is
similar to this report:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291

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

[Desktop-packages] [Bug 2039543] Re: Miss placed Hexchat icon when switching workspaces

Fixed in https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3285


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

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

Title:
  Miss placed Hexchat icon when switching workspaces

Status in Ubuntu AppIndicators:
  New
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Won't Fix

Bug description:
  While switching workspaces, Hexchat icon in the app indicator appears
  bigger than the normal and in a wrong position then disappears.

  Please check the attached screen cast for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-appindicator 57-1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 11:17:05 2023
  InstallationDate: Installed on 2023-10-12 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061739] Re: crash in meta_wayland_transaction_commit

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

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

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

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

Title:
  crash in meta_wayland_transaction_commit

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

Bug description:
  Hi,

  The system is Ubuntu Noble with a regular daily updates.
  This happens many times since few days ago but not clear
  at all how to reproduce it.

  Regards,
  Patrice

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Apr 16 09:26:16 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-05-24 (1789 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu6
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago)

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


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

If you delete ~/.config/monitors.xml and log in again, can you configure
the monitors correctly after that?


** Tags added: multimonitor nvidia

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

Are you sure Settings is showing both Iiyama and Philips or is it
perhaps showing one of them twice? (bug 2060268)

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

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2064196] Re: Can't change display position to "right of"

I wonder if this is due to bug 2060268...

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

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: 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/2064196

Title:
  Can't change display position to "right of"

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors (Iiyama and Philips).
  In 22.04 I had two separate pulpits on each monitors.

  Currently in "Settings -> Displays" I can set it to "duplicate" or "joined".
  joined option is inconvenient because, every window I open is by default in 
the center of the gap between two monitors.

  I'am able to change it manually via nvidia-settings but it isn't
  persistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-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  470.239.06  Sat Feb  3 
06:03:07 UTC 2024
   GCC version:
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:05:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e]
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: MSI MS-7758
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-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.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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-control-center/+bug/2064196/+subscriptions


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

[Desktop-packages] [Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs

** Summary changed:

- Window borders and shadows missing from GTK dialogs
+ Window borders and shadows missing from GTK3 dialogs

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Window borders and shadows missing from GTK3 dialogs

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  I have a fresh Ubuntu 24.04 instalation and some of the windows have a
  few problems. Some are probably caused by theming, as the windows'
  borders (or their color) makes them impossible to discern from the
  background windows.

  
  Just earlier I discovered another bug, related to detecting the click and 
window I clicked. I am trying to see the sub-content of a software update but 
the system reacts as I clicked the window below. In the recording you can see 
this happening both with the Terminal and with Firefox.

  
  I have plenty of screenshots and also a screen recording that show the bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 00:37:47 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-04-26 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  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/2064177/+subscriptions


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

[Desktop-packages] [Bug 2064197] [NEW] Labels are invisible until i move mouse at them

Public bug reported:

When I open gnome-control-center I can't see labels until I move/hover mouse 
over them.
Then they are visible until I change to another tab.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-control-center 1:46.0.1-1ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 08:20:46 2024
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2024-04-28 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=pl_PL.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Attachment added: "screen shoot"
   
https://bugs.launchpad.net/bugs/2064197/+attachment/5772856/+files/Zrzut%20ekranu%20z%202024-04-30%2008-22-55.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/2064197

Title:
  Labels are invisible until i move mouse at them

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

Bug description:
  When I open gnome-control-center I can't see labels until I move/hover mouse 
over them.
  Then they are visible until I change to another tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46.0.1-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 08:20:46 2024
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2024-04-28 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2064197/+subscriptions


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

[Desktop-packages] [Bug 2064196] [NEW] Can't change display position to "right of"