from:"Alessandro Astone"

** Changed in: linux (Ubuntu Oracular)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076428

Title:
  Enable CONFIG_EXFAT_FS in s390x too

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

Right, as Daniel said in comment #2 the issue about apps failing to
launch on NVIDIA+Wayland is tracked in  bug 1965563 and already resolved
in noble (but not in jammy).

So this thread is now only tracking the bug which causes apps to be
launched on the NVIDIA GPU by default in hybrid systems, rather than
defaulting to the integrated GPU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

** Changed in: egl-wayland (Ubuntu Jammy)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

With bug 2062082 fixed, applications are now allowed to use the NVIDIA GPU on 
hybrid systems on Wayland.
Together with bug 2080282, all hybrid systems running Jammy will hit this bug 
making this a high priority for a Jammy SRU

** Changed in: egl-wayland (Ubuntu Jammy)
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

@azorin, could you please verify if this build solves your issue?
https://launchpad.net/~aleasto/+archive/ubuntu/tests/+build/29088125

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

Yea the libnvidia-egl-wayland1 "fix" upstream was to basically disable
it for hybrid systems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

** Patch added: "egl-wayland_1.1.9-1.1ubuntu1.debdiff"
   
https://bugs.launchpad.net/gtk/+bug/1965563/+attachment/5816995/+files/egl-wayland_1.1.9-1.1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

egl-wayland >= 1.1.10 basically just disables itself on hybrid systems: the 
driver refuses to use a GPU that is not the compositor's primary GPU; so this 
bug does not happen when bug 1965563 is fixed.
-- Note that this means that "Launch using Discrete GPU" wouldn't work even if 
switcheroo-control was changed to configure EGL like it does GLX.

NVIDIA does intend to eventually allow egl-wayland to work on hybrid
systems, but I don't see any time commitment.

MESA instead should already default to using the compositor's primary
GPU when DRI_PRIME is unset; so this bug should not be present on hybrid
systems with non-NVIDIA discrete GPUs either.

For now, lowering the priority.

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

** Changed in: switcheroo-control (Ubuntu)
   Importance: Medium => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

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

> NVIDIA does intend to eventually allow egl-wayland to work on hybrid
systems, but I don't see any time commitment.

Scratch that, it seems supported by setting __NV_PRIME_RENDER_OFFLOAD.
Which switcheroo-control already does correctly.

So I guess there isn't much to fix here. It barely works, but it still
works.

Finally, this bug was indeed a duplicate of bug 1965563

** This bug has been marked a duplicate of bug 1965563
   GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

** Description changed:

+ [ Impact ]
+ 
+  * GTK applications fail to start on a hybrid graphics machine with an
+ NVIDIA discrete GPU.
+ 
+  * The NVIDIA egl-wayland extension 1.1.9 only supports rendering to the
+ NVIDIA GPU if it is the primary GPU. On a hybrid system the primary GPU
+ would be the integrated graphics, while the NVIDIA GPU should only be
+ used for offloading of specific applications. On such a setup, the egl-
+ wayland extension still incorrectly advertised the driver as compatible
+ and attempted to use the NVIDIA GPU for all EGL applications.
+ 
+  * To fix the issue, backport a commit from a newer version of the
+ NVIDIA egl-wayland extension that reports the driver as incompatible
+ when the NVIDIA GPU is not the primary GPU. This effectively ensures
+ that all EGL applications run on integrated graphics by default.
+ 
+ [ Test Plan ]
+ 
+  * Set up a hybrid graphics machine with Jammy 22.04 LTS and the
+ proprietary NVIDIA drivers 535 or 550.
+ 
+  * Install `libnvidia-egl-wayland1` from the update.
+ 
+  * Log-in to a Wayland desktop session.
+ 
+  * Verify that you can start `gnome-text-editor`.
+ 
+ [ Where problems could occur ]
+ 
+  * The scope of the change is limited to the NVIDIA proprietary drivers.
+ 
+  * A possible regression would be that the driver starts reporting as
+ incompatible on NVIDIA single-GPU systems too. One would notice by all
+ wayland-native applications suddenly being very slow. Note that such
+ systems would not default to Wayland in Jammy.
+ 
+ [ Original Report ]
+ 
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error
  
  Caveat: I currently have a mix of packages from jammy-release and jammy-
  proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080838] [NEW] No option to change session type to Wayland in KVM since kernel 6.8

Public bug reported:

My Jammy install in KVM does not offer the option to log-in to the GNOME
Wayland session when booting kernel 6.8.0-44-generic. Kernel 6.5.0
instead gives the option.

I've tried to use both QXL and Virtio as video drivers, both of which
offer KMS capabilities, and neither works. `/dev/dri/card1` exists.

`/run/udev/gdm-machine-has-hardware-gpu`
`/run/udev/gdm-machine-has-hybrid-graphics`
`/run/udev/gdm-machine-has-virtual-gpu`
all exist, which is not right.

This is likely due to the new SimpleDRM driver included in kernel 6.8.0,
which causes the primary GPU device to show up as `card1` rather than
`card0`.

https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/198 looks like it
should fix the issue of misdetecting this system as a hybrid graphics
system.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.4
ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 16 12:11:26 2024
InstallationDate: Installed on 2024-08-08 (39 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: gdm3 (Ubuntu Noble)
 Importance: Undecided
 Status: Fix Released

** Affects: gdm3 (Ubuntu Oracular)
 Importance: Undecided
 Status: Fix Released


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080838

Title:
  No option to change session type to Wayland in KVM since kernel 6.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080838] Re: No option to change session type to Wayland in KVM since kernel 6.8

** Attachment added: "drm_info"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2080838/+attachment/5817864/+files/drm.info

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

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

** Also affects: gdm3 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** No longer affects: gdm3 (Ubuntu Focal)

** Changed in: gdm3 (Ubuntu Noble)
   Status: New => Fix Released

** Changed in: gdm3 (Ubuntu Oracular)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080838

Title:
  No option to change session type to Wayland in KVM since kernel 6.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080838] Re: No option to change session type to Wayland in KVM since kernel 6.8

** Attachment added: "journalctl -b0"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2080838/+attachment/5817863/+files/journal.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080838

Title:
  No option to change session type to Wayland in KVM since kernel 6.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080838] Re: No option to change session type to Wayland in KVM since kernel 6.8

** Tags added: udeng-1202

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080838

Title:
  No option to change session type to Wayland in KVM since kernel 6.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078721] Re: nautilus crashed with SIGSEGV

2024-09-17 Thread Alessandro Astone

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078721

Title:
  nautilus crashed with SIGSEGV

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-07-01 Thread Alessandro Astone

== History ==
Prior to nvidia 545 the driver did not provide a framebuffer and instead relied
on framebuffers from CONFIG_EFI_FB and CONFIG_VESA_FB alike.

SimpleDRM (required on a modern Wayland-only system) can also provide a
framebuffer (simplefb), and indeed Ubuntu does not use EFI_FB and
VESA_FB anymore, relying purely on SimpleDRM to provide a fallback
framebuffer. However SimpleDRM also provides a DRM device which creates
this phantom display.

Since nvidia 545, the driver has gained the capability to provide a
framebuffer device, currently opt-in with the option `nvidia-
drm.fbdev=1`. Enabling this makes SimpleDRM go away like it would with
amdgpu or i915 (*currently racy, see [1]).

== Solutions ==
1. The first option is to enable fbdev=1 by default, like we do for
nvidia-drm.modeset=1.
This is still considered to be in test-stage by nvidia, and unfortunately on my
Ubuntu machine it breaks any graphical session with bug [2]. NB: somehow this
bug does not happen on my Fedora install, where fbdev=1 is already the default.

2. Prior to having the nvidia-drm.fbdev option in Fedora we would
instead disable SimpleDRM if-and-only-if the nvidia driver is installed.
You may achieve this either by appending
`initcall_blacklist=simpledrm_platform_driver_init` to the kernel
commandline through a package install-time script, or through a patch
like [3]. But we are now left with no framebuffer device, so switching
VT leaves you with a black screen (imho unacceptable). The solution to
that issue is to enable CONFIG_EFI_FB/CONFIG_VESA_FB again so that
nvidia systems will keep access to VTs, albeit low-res ones compared to
simplefb.

[1]: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2063143
[2]:
https://forums.developer.nvidia.com/t/545-29-06-18-1-flip-event-timeout-error-on-startup-shutdown-and-sometimes-suspend-wayland-unusable/274788
[3]: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1788/diffs

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] [NEW] Confine wdsd with apparmor

Public bug reported:

Limit resource access to increase security.

The apparmor profile needs to allow network access (ipv4 and ipv6), and
r/w access to at least $XDG_RUNTIME_DIR

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

** Patch added: "wsdd-apparmor.patch"
   
https://bugs.launchpad.net/bugs/2071692/+attachment/5794110/+files/wsdd-apparmor.patch

** Description changed:

  Limit resource access to increase security.
+ 
+ The apparmor profile needs to allow network access (ipv4 and ipv6), and
+ r/w access to at least $XDG_RUNTIME_DIR

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wdsd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

Sorry, rebased patch on ubuntu/devel

** Patch added: "wsdd-apparmor2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071692/+attachment/5794143/+files/wsdd-apparmor2.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

Apparently I can use fbdev=1 without hitting the bug at
https://forums.developer.nvidia.com/t/545-29-06-18-1-flip-event-timeout-
error-on-startup-shutdown-and-sometimes-suspend-wayland-unusable/274788
if I delay the startup of gdm with:

Wants=systemd-udev-settle.service
After=systemd-udev-settle.service

That is still different than 2063143 because the bug occurs even if I
disable simpledrm.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

Yes, I am upstreaming all changes to debian as well, but using ubuntu
for a first review since these changes interest us the most:
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2070025

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071453] Re: Create autopkgtests that test the daemon functionality

Indeed (assuming upstream wants it)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071453

Title:
  Create autopkgtests that test the daemon functionality

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

Debian change: https://salsa.debian.org/grantma/wsdd/-/merge_requests/6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071453] Re: Create autopkgtests that test the daemon functionality

Actually, this test currently relies on launching an `ubuntu-
daily:$(lsb_release -cs)` lxc container, so wouldn't work on debian :/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071453

Title:
  Create autopkgtests that test the daemon functionality

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2016368] Re: WSDD Package missing UFW application profile

Merge request in debian:
https://salsa.debian.org/grantma/wsdd/-/merge_requests/4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016368

Title:
  WSDD Package missing UFW application profile

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061744] Re: Evolution crashes on launch: libevolution-rss-common.so: cannot open shared object file

2024-07-04 Thread Alessandro Astone

The crash and the "Could not load /usr/lib/evolution-data-server/camel-
providers/libcamelrss.so: libevolution-rss-common.so: cannot open shared
object file: No such file or directory" message look like two different
issues.

I'm changing this bug description to track the missing library issue,
which only causes evolution to not support adding or showing RSS feeds,
since that's what was fixed in 3.52.1-4, and SRU the fix to noble.

If you still see the crash after this has been fixed, please file a
different bug report.

** Summary changed:

- Evolution crashes on launch: libevolution-rss-common.so: cannot open shared 
object file
+ Evolution does not handle RSS feeds anymore: libevolution-rss-common.so: 
cannot open shared object file

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061744

Title:
  Evolution does not handle RSS feeds anymore: libevolution-rss-
  common.so: cannot open shared object file

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061744] Re: Evolution does not handle RSS feeds anymore: libevolution-rss-common.so: cannot open shared object file

2024-07-04 Thread Alessandro Astone

** Description changed:

+ [ Impact ]
+ 
+ Evolution does not support adding or showing RSS feeds anymore.
+ `Menu > Edit > Preferences` shows no tab to manage RSS feeds, and the home 
page does not show any of the previously added ones.
+ 
+ Upon starting evolution the terminal output is as follows:
+ 
  ubuntu@ubuntu:~$ evolution
  
- (process:23406): e-data-server-WARNING **: 08:04:00.506: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
+ (process:265491): e-data-server-WARNING **: 09:24:47.124: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
  Failed to load module: /usr/lib/evolution/modules/module-rss.so
  
- (evolution:23406): camel-CRITICAL **: 08:04:00.597: camel_provider_list:
- Could not load /usr/lib/evolution-data-server/camel-
- providers/libcamelrss.so: libevolution-rss-common.so: cannot open shared
- object file: No such file or directory
+ (evolution:265491): camel-CRITICAL **: 09:24:47.330:
+ camel_provider_list: Could not load /usr/lib/evolution-data-
+ server/camel-providers/libcamelrss.so: libevolution-rss-common.so:
+ cannot open shared object file: No such file or directory
  
- (evolution-alarm-notify:23421): camel-CRITICAL **: 08:04:00.962: 
camel_provider_list: Could not load 
/usr/lib/evolution-data-server/camel-providers/libcamelrss.so: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
- bwrap: Creating new namespace failed: Permission denied
+ (evolution:265491): e-mail-engine-WARNING **: 09:24:47.457: Failed to
+ add service 'News and Blogs' (rss): No provider available for protocol
+ “rss”
  
- ** (evolution:23406): ERROR **: 08:04:01.075: Failed to fully launch 
dbus-proxy: Child process exited with code 1
- Trace/breakpoint trap (core dumped)
+ (evolution:265491): e-mail-engine-CRITICAL **: 09:24:47.511:
+ mail_session_refresh_cb: assertion 'service != NULL' failed
+ 
+ (evolution-alarm-notify:265513): camel-CRITICAL **: 09:24:47.690:
+ camel_provider_list: Could not load /usr/lib/evolution-data-
+ server/camel-providers/libcamelrss.so: libevolution-rss-common.so:
+ cannot open shared object file: No such file or directory
+ 
+ [ Test Plan ]
+ 
+  * Open Evolution
+> You may discard the Welcome wizard by clicking Cancel at the top left.
+ 
+  * Click on the hamburger menu and navigate to Edit > Preferences
+ 
+  * Verify that you see a "News and Blogs" tab in the sidebar.
+ 
+  * Click "News and Blogs"
+ 
+  * Click "Add"
+ 
+  * Insert an Feed URL, for example:
+https://distrowatch.com/news/distro/ubuntu.xml
+ 
+  * Click "Fetch" and verify that the "Name" field is automatically
+ populated.
+ 
+  * Click "Save"
+ 
+  * Close the Preferences window.
+ 
+  * Verify that in the main window's sidebar you see a "News and Blogs" 
section,
+with your newly added RSS feed.
+ 
+ [ Where problems could occur ]
+ 
+ Evolution is not pre-installed in Ubuntu Desktop.
+ If the update is malfunctional, the Evolution app (mail/contacts/calendar 
suite) may stop working.
+ 
+ Evolution is part of the GNOME micro release exceptions:
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: evolution 3.52.0-1build2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 08:09:58 2024
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
-  LANG=C.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061744

Title:
  Evolution does not handle RSS feeds anymore: libevolution-rss-
  common.so: cannot open shared object file

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061744] Re: Evolution does not handle RSS feeds anymore: libevolution-rss-common.so: cannot open shared object file

2024-07-08 Thread Alessandro Astone

** Description changed:

  [ Impact ]
  
  Evolution does not support adding or showing RSS feeds anymore.
  `Menu > Edit > Preferences` shows no tab to manage RSS feeds, and the home 
page does not show any of the previously added ones.
  
  Upon starting evolution the terminal output is as follows:
  
  ubuntu@ubuntu:~$ evolution
  
  (process:265491): e-data-server-WARNING **: 09:24:47.124: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
  Failed to load module: /usr/lib/evolution/modules/module-rss.so
  
  (evolution:265491): camel-CRITICAL **: 09:24:47.330:
  camel_provider_list: Could not load /usr/lib/evolution-data-
  server/camel-providers/libcamelrss.so: libevolution-rss-common.so:
  cannot open shared object file: No such file or directory
  
  (evolution:265491): e-mail-engine-WARNING **: 09:24:47.457: Failed to
  add service 'News and Blogs' (rss): No provider available for protocol
  “rss”
  
  (evolution:265491): e-mail-engine-CRITICAL **: 09:24:47.511:
  mail_session_refresh_cb: assertion 'service != NULL' failed
  
  (evolution-alarm-notify:265513): camel-CRITICAL **: 09:24:47.690:
  camel_provider_list: Could not load /usr/lib/evolution-data-
  server/camel-providers/libcamelrss.so: libevolution-rss-common.so:
  cannot open shared object file: No such file or directory
  
  [ Test Plan ]
  
-  * Open Evolution
-> You may discard the Welcome wizard by clicking Cancel at the top left.
+  * Open Evolution
+    > You may discard the Welcome wizard by clicking Cancel at the top left.
  
-  * Click on the hamburger menu and navigate to Edit > Preferences
+  * Click on the hamburger menu and navigate to Edit > Preferences
  
-  * Verify that you see a "News and Blogs" tab in the sidebar.
+  * Verify that you see a "News and Blogs" tab in the sidebar.
  
-  * Click "News and Blogs"
+  * Click "News and Blogs"
  
-  * Click "Add"
+  * Click "Add"
  
-  * Insert an Feed URL, for example:
-https://distrowatch.com/news/distro/ubuntu.xml
+  * Insert an Feed URL, for example:
+    https://distrowatch.com/news/distro/ubuntu.xml
  
-  * Click "Fetch" and verify that the "Name" field is automatically
+  * Click "Fetch" and verify that the "Name" field is automatically
  populated.
  
-  * Click "Save"
+  * Click "Save"
  
-  * Close the Preferences window.
+  * Close the Preferences window.
  
-  * Verify that in the main window's sidebar you see a "News and Blogs" 
section,
-with your newly added RSS feed.
+  * Verify that in the main window's sidebar you see a "News and Blogs" 
section,
+    with your newly added RSS feed.
+ 
+  * Also follow the generic test plan for Evolution updates
+> https://wiki.ubuntu.com/DesktopTeam/TestPlans/Evolution
  
  [ Where problems could occur ]
  
- Evolution is not pre-installed in Ubuntu Desktop.
- If the update is malfunctional, the Evolution app (mail/contacts/calendar 
suite) may stop working.
+ Evolution is included by default in Ubuntu MATE.
+ 
+ If the update is malfunctioning, the Evolution app
+ (mail/contacts/calendar suite) may stop working. The Thunderbird app may
+ be used alternatively.
  
  Evolution is part of the GNOME micro release exceptions:
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: evolution 3.52.0-1build2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 08:09:58 2024
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [ Impact ]
  
  Evolution does not support adding or showing RSS feeds anymore.
  `Menu > Edit > Preferences` shows no tab to manage RSS feeds, and the home 
page does not show any of the previously added ones.
  
  Upon starting evolution the terminal output is as follows:
  
  ubuntu@ubuntu:~$ evolution
  
  (process:265491): e-data-server-WARNING **: 09:24:47.124: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
  Failed to load module: /usr/lib/evolution/modules/module-rss.so
  
  (evolution:265491): camel-CRITICAL **: 09:24:47.330:
  camel_provider_list: Could not load /usr/lib/evolution-data-
  server/camel-providers/libcamelrss.so: libevolution-rss-common.so:
  cannot open shared object file: No such file or directory
  
  (evolution:265491): e-mail-engine-WARNING **: 09:24:47.457: Failed to
  add

[Bug 2072547] [NEW] [SRU] Update evolution to 3.52.3

2024-07-09 Thread Alessandro Astone

Public bug reported:

[ Impact ]
This is a new stable release in the 3.52 series.
https://gitlab.gnome.org/GNOME/evolution/-/blob/3.52.3/NEWS

[ Test Plan ]
You may follow the generic test plan at:
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Evolution

[ Where problems could occur ]
Evolution is included by default in Ubuntu MATE.

If the update is malfunctioning, the Evolution app
(mail/contacts/calendar suite) may stop working. The Thunderbird app may
be used alternatively.

Evolution is part of the GNOME micro release exceptions:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

[ Other Info ]
This depends on evolution-data-server 3.52.3 so that version ought to reach 
noble-updates before we let evolution 3.44.4 in to noble-updates

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072547

Title:
  [SRU] Update evolution to 3.52.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067420] Re: [SRU] Update gnome-calculator to 46.1

2024-07-11 Thread Alessandro Astone

Verified the version 1:46.1-1ubuntu1~24.04.1 against the test plan on
Ubuntu 24.04 LTS

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067420

Title:
  [SRU] Update gnome-calculator to 46.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-07-15 Thread Alessandro Astone

Status update from me.

The hang with nvidia-drm.fbdev=1 is caused by gpu-manager.service which is:
WantedBy=display-manager.service
Before=display-manager.service

In my previous testing delaying gdm.service with udev-settle really just
caused to delay gpu-manager.service which fixes this issue.

I'm now thinking that gpu-manager.service is also the cause of bug
2063143.

It also explains why I don't hit any of these bugs in Fedora, as gpu-
manager.service is only shipped in ubuntu:
https://github.com/canonical/ubuntu-drivers-
common/blob/master/share/hybrid/gpu-manager.c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-07-15 Thread Alessandro Astone

With this workaround https://github.com/canonical/ubuntu-drivers-
common/pull/100 we can enable nvidia-drm.fbdev=1 and solve this bug for
nvidia >=550

How do you want to handle 470 and 535?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

I like it.
And +1 for 71-u-d-c-gpu-detection.rules over 71-nvidia.rules

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071453] Re: Create autopkgtests that test the daemon functionality

The current progress is that I got verbose output and can reproduce the
failure in a local qemu by setting up an http proxy as described in the
"I'm seeing a squid proxy? My tests behave differently there!" section
of https://wiki.ubuntu.com/ProposedMigration#autopkgtests

Attaching the current debdiff for this test failure:
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-aleasto-
tests/oracular/amd64/w/wsdd/20240703_151256_a54f9@/log.gz

** Patch added: "wsdd-discovery-autopkgtest.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071453/+attachment/5797607/+files/wsdd-discovery-autopkgtest.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071453

Title:
  Create autopkgtests that test the daemon functionality

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069416] Re: ThinkPad Z13 + AMDGPU Bootloops on wake from suspend

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

Indeed `6.8.0-40-generic` is working fine for me!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069416

Title:
  ThinkPad Z13 + AMDGPU Bootloops on wake from suspend

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064595] Re: AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system

Indeed `6.8.0-40-generic` is working fine for me!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595

Title:
  AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070386] Re: [SRU] Update evolution-data-server to 3.52.3

Verified the following builds on Ubuntu 24.04 LTS:
evolution-data-server:amd64 (3.52.3-0ubuntu1)
evolution-data-server-common:amd64 (3.52.3-0ubuntu1)
libcamel-1.2-64t64:amd64 (3.52.3-0ubuntu1)
libecal-2.0-3:amd64 (3.52.3-0ubuntu1)
libedataserverui4-1.0-0t64:amd64 (3.52.3-0ubuntu1)
libebook-1.2-21t64:amd64 (3.52.3-0ubuntu1)
libedata-book-1.2-27t64:amd64 (3.52.3-0ubuntu1)
libedataserverui-1.2-4t64:amd64 (3.52.3-0ubuntu1)
libedataserver-1.2-27t64:amd64 (3.52.3-0ubuntu1)
libebook-contacts-1.2-4t64:amd64 (3.52.3-0ubuntu1)
libedata-cal-2.0-2t64:amd64 (3.52.3-0ubuntu1)
libebackend-1.2-11t64:amd64 (3.52.3-0ubuntu1)


Both Calendar and Evolution behave correctly according to the test plans.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070386

Title:
  [SRU] Update evolution-data-server to 3.52.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070283] Re: [SRU] Update gnome-text-editor to 46.3

Verified gnome-text-editor_46.3-0ubuntu1_amd64 on Ubuntu 24.04 LTS
against the test plan.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070283

Title:
  [SRU] Update gnome-text-editor to 46.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072547] Re: [SRU] Update evolution to 3.52.3

2024-07-17 Thread Alessandro Astone

I've added test plans for the  suite using a
Google account, and a test plan for RSS Feed (the same test plan
specified in the bug-report that this upload fixes)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072547

Title:
  [SRU] Update evolution to 3.52.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071453] Re: Create autopkgtests that test the daemon functionality

2024-07-17 Thread Alessandro Astone

Success!
The autopkgtest now passes in ppa too: 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-aleasto-tests/oracular/amd64/w/wsdd/20240717_160225_dd052@/log.gz

** Patch added: "wsdd-discovery-autopkgtest.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071453/+attachment/5798095/+files/wsdd-discovery-autopkgtest.2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071453

Title:
  Create autopkgtests that test the daemon functionality

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072547] Re: [SRU] Update evolution to 3.52.3

2024-07-17 Thread Alessandro Astone

** Changed in: evolution (Ubuntu Noble)
   Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072547

Title:
  [SRU] Update evolution to 3.52.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-08-30 Thread Alessandro Astone

** Description changed:

[ Impact ]

After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.

It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dri/card1.

This also seems to be triggering bug 2062426 and bug 2066126.

[ Temporary Workaround ]

1. sudo rm /dev/dri/card0
2. Log in again.

[ Permanent Workaround ]

Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init
Beware that this has side-effects: see comment #37

[ Test Plan - Nvidia case ]

1. Set up a single monitor desktop where the only GPU enabled is an Nvidia
one.
2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
3. Reboot and verify the Nvidia driver is now active (lspci -k should mention
'nvidia' and not 'nouveau').
4. Open Settings and verify the only monitors shown are your real monitors.

[ Test Plan - Non-Nvidia case ]

- 1. Set up a single monitor desktop with one or more GPUs, all non-nvidia.
-(a KVM virtual machine with VirtIO is an easy candidate for this)
+ 1. Set up a machine with one or more GPUs, all non-nvidia.
+ (a KVM virtual machine with VirtIO is an easy candidate for this)
2. Run `apt install nvidia-driver-535`.
3. Reboot.
4. Verify that you are able to log into the Ubuntu Desktop Wayland session.

[ Test Plan - No-GPU case ]

- 1. Set up a single monitor desktop without any GPU.
-(a virtual machine without any graphics acceleration (vmware, virtio...)
is an easy candidate for this.
+ 1. Set up a machine without any GPU.
+ (a virtual machine without any graphics acceleration (vmware, virtio...)
is an easy candidate for this.
2. Run `sudo apt install nvidia-driver-535`.
3. Reboot.
4. Verify that you are able to log into the Ubuntu Desktop Wayland session.
5. Go back to point 2, and try with another driver version:
-[nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open,
nvidia-driver-550, nvidia-driver-550-open]
-
+ [nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open,
nvidia-driver-550, nvidia-driver-550-open]

[ Where problems could occur ]

Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.

One case where this could happen is if the Nvidia driver would allow
being loaded even without any nvidia hardware present: if that is the
case, "Test Plan - No-GPU case" would fail.

[ Other Info ]

ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:dan4631 F pipewire
/dev/snd/controlC1: dan4636 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-01-04 (92 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
MachineType: Intel(R) Client Systems NUC12DCMi7
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash
vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
RelatedPackageVersions:
linux-restricted-modules-6.8.0-11-generic N/A
linux-backports-modules-6.8.0-11-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu1
Tags: noble
Uname: Linux 6.8.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 12/20/2021
dmi.bios.release: 5.24
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EDADL579.0046.2021.1220.2351
dmi.board.name: NUC12EDBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M27908-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.7
dmi.modalias:
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
dmi.product.family: DC
dmi.product.name: NUC12DCMi7
dmi.product.sku: RNUC12DCMi7
dmi.product.version: M30143-302
dmi.sys.vendor: Intel(R) Client Systems

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
Phantom "Unknown Display" shown in Settings after installin

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-08-30 Thread Alessandro Astone

Very early in the boot process SimpleDRM will claim card0 as a DRM device 
backed by the BIOS framebuffer, mostly useful to offer Wayland-friendly 
graphics on systems without a GPU.
When the system loads a GPU driver that brings its own framebuffer, it will 
automatically unload SimpleDRM. The nvidia driver doesn't yet expose a 
framebuffer (it's changing soon), so SimpleDRM will stick around on nvidia-only 
systems.

On single-GPU systems without nvidia, the GPU display will be at /dev/dri/card1 
and card0 won't be present because SimpleDRM was unloaded.
On single-GPU systems with nvidia, the GPU display will also be at 
/dev/dri/card1 but card0 will stick around, causing this bug.
On multi-GPU systems, the presence of any non-nvidia GPUs should trigger the 
automatic removal of SimpleDRM. I'm not sure about this but I think it is 
possible that one of the real GPUs would end up as /dev/dri/card0.


To address the bug, we cannot simply unload SimpleDRM on nvidia because it also 
provides the system's only framebuffer at /dev/fb0, which we need for VTs and 
comment #37 for example. But we can remove the SimpleDRM DRM node at 
/dev/dri/card0 which we don't need because an actual GPU card is available at 
/dev/dri/card1.


 > don't systems with multiple video cards exist, and couldn't one be using 
 > /dev/dri/card0?

There are two conditions that need to be satisfied in order for the `rm
/dev/dri/card0` action to run:

1. The nvidia proprietary driver must be loaded. Note that the nvidia
driver will refuse to probe unless a nvidia GPU is present, so this
implies that the nvidia hardware is available.

2. The /dev/dri/card0 device must be owned by SimpleDRM. If
/dev/dri/card0 is created by another driver, the action will not be run.


 > During boot, when does exactly "/bin/rm /dev/dri/card0" run

Whenever the nvidia driver is loaded. I'm not sure when that normally
is, but it shouldn't be relevant: when any other GPU DRM driver is
present, we don't need a SimpleDRM DRM node.

 > Also, the test plan still does not cover non-nvidia platforms, and it
sounds to me like that would be crucial.

The two pre-conditions that i've illustrated above will cover the non-
nvidia case. The crucial point there is that the nvidia driver must
refuse to load without the underlying hardware. Since that is the case,
the `rm` action is not triggered. The regression potential here is that
on a system with the nvidia driver installed but no GPU hardware we
would remove the only DRM driver, breaking Wayland compositors. I'll add
a test-plan to ensure that the driver behaves as expected. I guess this
would be where testing multiple nvidia driver versions is useful.

 > could /dev/dri/card0 be used for non-graphical things, like servers
doing GPU calculations? And in that case, removing it could break that
workload?

No, SimpleDRM only allows drawing one buffer to the screen.



** Description changed:

  [ Impact ]
  
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.
  
  It looks like the phantom monitor is /dev/dri/card0 which is still
  controlled by simpledrm, while Nvidia uses /dev/dri/card1.
  
  This also seems to be triggering bug 2062426 and bug 2066126.
  
  [ Temporary Workaround ]
  
  1. sudo rm /dev/dri/card0
  2. Log in again.
  
  [ Permanent Workaround ]
  
  Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init
+ Beware that this has side-effects: see comment #37
  
- [ Test Plan ]
+ [ Test Plan - Nvidia case ]
  
  1. Set up a single monitor desktop where the only GPU enabled is an Nvidia 
one.
  2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
  3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 
'nvidia' and not 'nouveau').
  4. Open Settings and verify the only monitors shown are your real monitors.
  
+ [ Test Plan - Non-Nvidia case ]
+ 
+ 1. Set up a single monitor desktop with one or more GPUs, all non-nvidia.
+(a KVM virtual machine with VirtIO is an easy candidate for this)
+ 2. Run `apt install nvidia-driver-535`.
+ 3. Reboot.
+ 4. Verify that you are able to log into the Ubuntu Desktop Wayland session.
+ 
+ [ Test Plan - No-GPU case ]
+ 
+ 1. Set up a single monitor desktop without any GPU.
+(a virtual machine without any graphics acceleration (vmware, virtio...) 
is an easy candidate for this.
+ 2. Run `sudo apt install nvidia-driver-535`.
+ 3. Reboot.
+ 4. Verify that you are able to log into the Ubuntu Desktop Wayland session.
+ 5. Go back to point 2, and try with another driver version:
+[nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open, 
nvidia-driver-550, nvidia-driver-550-open]
+ 
+ 
  [ Where problems could occur ]
  
  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.
+ 
+

[Bug 2078674] [NEW] Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main)

Public bug reported:

08/06/17 version 5.5.2.6 (temp release)
- Modified generating MPS file with some new options:
  - MPSLINDO: Write semi-continious variables in different order as required by 
LINDO
  - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format
xli_MPS is modified to handle these new options.
- Reading an lp file with a semi-cont variable failed if the minimum is larger 
than the maximum.
  This is allowed because if the semi-cont attribute on the variables in which 
case a 0 is also a valid solution.
- Some models with degeneraracy returned a "Unacceptable accuracy found" error.

30/07/17 version 5.5.2.7 (temp release)
- Lower/Upper objective sensitivity was sometimes not given for some variables. 
Was ok when scaling was disabled.

xx/xx/xx version 5.5.2.8
- Modified PHP driver for PHP 5.4
- In some cases an accuracy error was given by check_solution which was not 
always true

13/03/20 version 5.5.2.9
- When a model is infeasible it can happen that the returned solution is not 
initialised and returning NAN values

15/11/20 version 5.5.2.10
- write_MPS doesn't generate an SC BOUND on a variable that is semi-continious 
and the upper bound is equal to the lower bound.
- The VB.NET demo application wasn't adapted yet for 64-bit

29/12/20 version 5.5.2.11
- version 5.5.2.9 introduced a problem for some models. They give infeasible or 
let even lpsolve crash.

** Affects: lp-solve (Ubuntu)
 Importance: Undecided
 Assignee: Alessandro Astone (aleasto)
 Status: In Progress

** Merge proposal linked:
   
https://code.launchpad.net/~aleasto/ubuntu/+source/lp-solve/+git/lp-solve/+merge/471906

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078674

Title:
  Please merge lp-solve 5.5.2.11-2 (main) from Debian unstable (main)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

** Description changed:

[ Impact ]

After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.

It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dri/card1.

This also seems to be triggering bug 2062426 and bug 2066126.

[ Temporary Workaround ]

1. sudo rm /dev/dri/card0
2. Log in again.

[ Permanent Workaround ]

Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init
Beware that this has side-effects: see comment #37

[ Test Plan - Nvidia case ]

[ Test Plan - Non-Nvidia case ]

1. Set up a machine with one or more GPUs, all non-nvidia.
(a KVM virtual machine with VirtIO is an easy candidate for this)
2. Run `apt install nvidia-driver-535`.
3. Reboot.
4. Verify that you are able to log into the Ubuntu Desktop Wayland session.

[ Test Plan - No-GPU case ]

1. Set up a machine without any GPU.
(a virtual machine without any graphics acceleration (vmware, virtio...)
is an easy candidate for this.
2. Run `sudo apt install nvidia-driver-535`.
3. Reboot.
4. Verify that you are able to log into the Ubuntu Desktop Wayland session.
5. Go back to point 2, and try with another driver version:
[nvidia-driver-470, nvidia-driver-535, nvidia-driver-535-open,
nvidia-driver-550, nvidia-driver-550-open]
+
+ [ Test Plan - Nvidia+LUKS ]
+
+ 1. Set up a machine with an Nvidia GPU and encrypted disk.
+ 2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
+ 3. Reboot
+ 4. Verify that you see the password prompt for decrypting the disk.

[ Where problems could occur ]

Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.

One case where this could happen is if the Nvidia driver would allow
being loaded even without any nvidia hardware present: if that is the
case, "Test Plan - No-GPU case" would fail.

[ Other Info ]

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver

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

--
ubuntu-bugs mailing list
ub

[Bug 2078715] [NEW] [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

Public bug reported:

[ Why ]

The current version of lp-solve in Ubuntu fails to build with gcc 14 due to new 
warnings.
The version in debian has already resolved this issue, but was not imported 
into Ubuntu automatically because it had deviated from debian.

We can merge back with debian to achieve the following:
* Many bugfixes from upstream
* Fix the FTBFS with gcc 14
* Re-align with debian

Attaching the upstream changelog diff.

This is a new minor version, but a Freeze Exception might be necessary
because two new options were added:

+- Modified generating MPS file with some new options:
+  - MPSLINDO: Write semi-continious variables in different order as required 
by LINDO
+  - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS format
+xli_MPS is modified to handle these new options.

Because the new options wouldn't be used by any existing projects, i
believe it is safe to upgrade to the new version.

However if this is rejected I will just propose backporting the FTBFS
fix to the Ubuntu package, and we can backport more fixes as requested.

[ Test ]

$ cat

[Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

sbuild targeting noble

** Attachment added: "lp-solve.sbuild.log"
   
https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812374/+files/lp-solve.sbuild.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078715

Title:
  [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

** Attachment added: "lp-solve.install.log"
   
https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812375/+files/lp-solve.install.log

** Description changed:

  [ Why ]
  
  The current version of lp-solve in Ubuntu fails to build with gcc 14 due to 
new warnings.
  The version in debian has already resolved this issue, but was not imported 
into Ubuntu automatically because it had deviated from debian.
  
  We can merge back with debian to achieve the following:
  * Many bugfixes from upstream
  * Fix the FTBFS with gcc 14
  * Re-align with debian
  
  Attaching the upstream changelog diff.
  
  This is a new minor version, but a Freeze Exception might be necessary
  because two new options were added:
  
  +- Modified generating MPS file with some new options:
  +  - MPSLINDO: Write semi-continious variables in different order as required 
by LINDO
  +  - MPSFREEFULLPRECISION: Write numbers with more precision in free MPS 
format
  +xli_MPS is modified to handle these new options.
  
  Because the new options wouldn't be used by any existing projects, i
  believe it is safe to upgrade to the new version.
  
  However if this is rejected I will just propose backporting the FTBFS
  fix to the Ubuntu package, and we can backport more fixes as requested.
  
  [ Test ]
+ 
  $ cat

[Bug 2078715] Re: [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

** Attachment added: "lp-solve.sbuild.log"
   
https://bugs.launchpad.net/ubuntu/+source/lp-solve/+bug/2078715/+attachment/5812376/+files/lp-solve.sbuild.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078715

Title:
  [FFE] Upgrade lp-solve to 5.5.2.11-2 in oracular

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

** Description changed:

[ Impact ]

After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.

It looks like the phantom monitor is /dev/dri/card0 which is still
controlled by simpledrm, while Nvidia uses /dev/dri/card1.

This also seems to be triggering bug 2062426 and bug 2066126.

[ Temporary Workaround ]

1. sudo rm /dev/dri/card0
2. Log in again.

[ Permanent Workaround ]

Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init
Beware that this has side-effects: see comment #37

[ Test Plan - Nvidia case ]

1. Set up a DESKTOP where the only GPU enabled is an Nvidia one.
2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
3. Reboot and verify the Nvidia driver is now active (lspci -k should mention
'nvidia' and not 'nouveau').
4. Open Settings and verify the only monitors shown are your real monitors.

[ Regression Test Plan - Intel/AMD graphics ]

1. Set up a machine with integrated graphics only.
2. Reboot.
3. Verify that you are able to log into the Ubuntu Desktop Wayland session.
4. Run `apt install nvidia-driver-535`.
5. Reboot.
6. Verify that you are able to log into the Ubuntu Desktop Wayland session.

[ Regression Test Plan - Virtual machines ]

1. Set up a virtual machine without any graphics acceleration (vmware,
virtio...)
2. Reboot.
3. Verify that you are able to log into the Ubuntu Desktop Wayland session.
4. Run `sudo apt install nvidia-driver-535`.
5. Reboot.
6. Verify that you are able to log into the Ubuntu Desktop Wayland session.
7. Optionally go back to point 4, and try with nvidia-driver-550.

[ Regression Test Plan - Nvidia+LUKS ]

1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted
disk.
2. Open the 'Additional Drivers' app to install a supported Nvidia driver.
3. Reboot
4. Verify that you see the password prompt for decrypting the disk.

[ Where problems could occur ]

Removing the simpledrm card is only safe when it's not being used. If
somehow a machine wasn't using the installed Nvidia driver then there
could be a risk of deleting the only working display.

One case where this could happen is if the Nvidia driver would allow
being loaded even without any nvidia hardware present: if that is the
- case, "Test Plan - No-GPU case" would fail.
+ case, "Regression Test Plan - Virtual machines" would fail.

[ Other Info ]

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver

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

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

Verified [ Regression Test Plan - Virtual Machines ] with ubuntu-drivers-common 
1:0.9.7.6ubuntu3.1 on Ubuntu 24.04 LTS by using KVM:
```

  

```

Even with nvidia-driver-535 or nvidia-driver-550 installed, the system
has kept access to SimpleDRM and can still boot a Wayland session.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

Verified [ Regression Test Plan - Intel/AMD graphics ] with ubuntu-
drivers-common 1:0.9.7.6ubuntu3.1 on Ubuntu 24.04.1 LTS on an AMD
thinkpad.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078812] [NEW] lerc: FTBFS with gcc-14

Public bug reported:

From the test rebuild, lerc failed to rebuild on ppc64el:
https://launchpadlibrarian.net/745205771/buildlog_ubuntu-oracular-
ppc64el.lerc_4.0.0+ds-4ubuntu2_BUILDING.txt.gz

gcc-14 has introduced a regression which causes it to crash when
compiling valid code:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460

** Affects: gcc
 Importance: Unknown
 Status: Unknown

** Affects: gcc-14 (Ubuntu)
 Importance: Undecided
 Assignee: Alessandro Astone (aleasto)
 Status: New

** Affects: lerc (Ubuntu)
 Importance: Undecided
 Assignee: Alessandro Astone (aleasto)
 Status: New

** Also affects: gcc-14 (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: GCC Bugzilla #116460
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460

** Also affects: gcc via
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116460
   Importance: Unknown
   Status: Unknown

** Changed in: lerc (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: gcc-14 (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078812

Title:
  lerc: FTBFS with gcc-14

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078812] Re: lerc: FTBFS with gcc-14

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

** Changed in: gcc-14 (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078812

Title:
  lerc: FTBFS with gcc-14

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078812] Re: lerc: FTBFS with gcc-14

Matthias, I've backported the upstream fix here if you want to include it:
https://salsa.debian.org/aleasto/gcc/-/commit/3416b33ed98e749068f57d5fe805f2e1e85be1f3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078812

Title:
  lerc: FTBFS with gcc-14

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

Verified [ Regression Test Plan - Virtual Machines ] with ubuntu-
drivers-common 1:0.9.6.2~0.22.04.7 on Ubuntu 22.04.4 LTS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080073] Re: 47rc: unable to resize mattermost, discord windows

2024-09-10 Thread Alessandro Astone

Can you try https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3997
?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080073

Title:
  47rc: unable to resize mattermost,  discord windows

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078721] Re: nautilus crashed with SIGSEGV

2024-09-10 Thread Alessandro Astone

** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078721

Title:
  nautilus crashed with SIGSEGV

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

2024-09-12 Thread Alessandro Astone

> So the only real issue now is; why would GNOME default to launching
apps on the discrete GPU instead of the integrated GPU?

That's expected for EGL apps, because
`/usr/share/glvnd/egl_vendor.d/10_nvidia.json` comes before
`/usr/share/glvnd/egl_vendor.d/50_nvidia.json`.

switcherooctl also does not support switching EGL vendor at the moment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

> This needs verifying in Oracular to see if it's still the case.

It is behaving as designed. Because NVIDIA has priority in EGL, it will
always be tried first. Without libnvidia-egl-wayland1 it fails so the
second driver is probed, MESA.

> If the maintainer of the nvidia-graphics-drivers-550 source package
could remove "libnvidia-egl-wayland1" as a dependency for the
"libnvidia-gl-550" package in jammy (as was the case before), this issue
should probably be resolved.

> I believe that's the fix.

Breaking the NVIDIA driver cannot be the fix ;)

What we probably want is to fix switcheroo, and make gnome-shell always
use switcheroo rather than only for "Launch Using Discrete GPU"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

From the GLVND documentation:

> EGL can't rely on asking an X server for a vendor name like GLX can,
so instead, it enumerates and loads every available vendor library.
Loading every vendor is also needed to support extensions such as
EGL_EXT_device_enumeration.

> When the application calls eglGetPlatformDisplay, EGL will simply call
into each vendor library until it finds one that succeeds. After that,
whichever vendor succeeded owns that display.


** Also affects: switcheroo-control (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

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

** Changed in: switcheroo-control (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: switcheroo-control (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080282] Re: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU

** Tags added: udeng-1202

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080282

Title:
  Apps run on the discrete Nvidia GPU by default instead of the Intel
  integrated GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064732] Re: Update xdg-desktop-portal-gnome to 46.2

2024-07-18 Thread Alessandro Astone

Verified `xdg-desktop-portal-gnome/noble-proposed,now 46.2-0ubuntu1 amd64` on 
Ubuntu 24.04 LTS by running the test plan.
Also no issues found while daily driving it for 2 days.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064732

Title:
  Update xdg-desktop-portal-gnome to 46.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071453] Re: Create autopkgtests that test the daemon functionality

2024-07-18 Thread Alessandro Astone

seb already sponsored the upload, it's currently in oracular-proposed.

The wsdd version installed in the container should already be the one
being tested, because we share the apt configuration with the host. But
yea specifying the version wouldn't hurt :)

I'll take a look at shellcheck!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071453

Title:
  Create autopkgtests that test the daemon functionality

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() ["bwrap: setting up uid map: Permission denied" ; "Failed to fully launch

My two cents:

The apparmor profile looks good.
It also wouldn't hurt to properly confine the process since it involves a 
webview and untrusted remote content

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051574

Title:
  gnome-shell-portal-helper crashed with SIGTRAP in
  waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() ["bwrap:
  setting up uid map: Permission denied" ; "Failed to fully launch dbus-
  proxy: Child process exited with code 1"]

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073589] [NEW] Confined executable script needs 'mrix' rule on its shebang only when running inside LXD

Public bug reported:

I'm writing the AppArmor policy for a python script installed as
executable at `/usr/bin/wsdd`

The script has the following shebang: `#!/usr/bin/env python3`

With the aid of aa-logprof I came up with the following rules for
enabling the execution of this script:

  /usr/bin/env ix,
  /{,usr/}bin/python3.{1,}[0-9] mrix,
  /usr/bin/wsdd r,

It works correctly on my machine. However when running the same program
with the same profile inside an LXD container, executing /usr/bin/wsdd
fails with "Segmentation fault".

Running it in `strace` shows:

  execve("/usr/bin/wsdd", ["/usr/bin/wsdd"], 0x7ffc5329f110 /* 12 vars */) = -1 
EACCES (Permission denied)
  +++ killed by SIGSEGV +++

And the host journal shows:

  Jul 19 12:32:00 thinkpad kernel: audit: type=1400
audit(1721385120.086:2685): apparmor="DENIED" operation="file_mmap"
class="file" namespace="root//lxd-noble_"
profile="/usr/bin/wsdd" name="/usr/bin/env" pid=74694 comm="wsdd"
requested_mask="r" denied_mask="r" fsuid=100 ouid=100

The audit indicates that AppArmor is preventing mmap of /usr/bin/env, the 
program specified in the shebang.
Indeed changing the rule from `/usr/bin/env ix` to `/usr/bin/env mrix` solves 
the issue.
But why is `mrix` only required inside LXD?

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor 4.0.1really4.0.0-beta3-0ubuntu0.1
ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 19 12:17:54 2024
InstallationDate: Installed on 2024-06-16 (33 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-40-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: wsdd (Ubuntu)
 Importance: Medium
 Assignee: Alessandro Astone (aleasto)
 Status: In Progress


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

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

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

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

** Changed in: wsdd (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Description changed:

  I'm writing the AppArmor policy for a python script installed as
  executable at `/usr/bin/wsdd`
  
  The script has the following shebang: `#!/usr/bin/env python3`
  
  With the aid of aa-logprof I came up with the following rules for
  enabling the execution of this script:
  
-   /usr/bin/env ix,
-   /{,usr/}bin/python3.{1,}[0-9] mrix,
-   /usr/bin/wsdd r,
+   /usr/bin/env ix,
+   /{,usr/}bin/python3.{1,}[0-9] mrix,
+   /usr/bin/wsdd r,
  
- It works correctly on my machine. However when installing the same
- profile inside an LXD container, running /usr/bin/wsdd fails with
- "Segmentation fault".
+ It works correctly on my machine. However when running the same program
+ with the same profile inside an LXD container, executing /usr/bin/wsdd
+ fails with "Segmentation fault".
  
  Running it in `strace` shows:
  
-   execve("/usr/bin/wsdd", ["/usr/bin/wsdd"], 0x7ffc5329f110 /* 12 vars */) = 
-1 EACCES (Permission denied)
-   +++ killed by SIGSEGV +++
+   execve("/usr/bin/wsdd", ["/usr/bin/wsdd"], 0x7ffc5329f110 /* 12 vars */) = 
-1 EACCES (Permission denied)
+   +++ killed by SIGSEGV +++
  
  And the host journal shows:
  
-   Jul 19 12:32:00 thinkpad kernel: audit: type=1400
+   Jul 19 12:32:00 thinkpad kernel: audit: type=1400
  audit(1721385120.086:2685): apparmor="DENIED" operation="file_mmap"
  class="file" namespace="root//lxd-noble_"
  profile="/usr/bin/wsdd" name="/usr/bin/env" pid=74694 comm="wsdd"
  requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  
  The audit indicates that AppArmor is preventing mmap of /usr/bin/env, the 
program specified in the shebang.
  Indeed changing the rule from `/usr/bin/env ix` to `/usr/bin/env mrix` solves 
the issue.
  But why is `mrix` only required inside LXD?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor 4.0.1really4.0.0-beta3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 19 12:17:54 2024
  InstallationDate:

[Bug 2071692] Re: Confine wsdd with apparmor

Oops! We actually added a new autopkgtest and the new apparmor profile
in a single upload, but apparently I never tested the two in
combination; sorry!

Attaching a fix (that also includes other minor changes addressing a
late review @
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071453/comments/9 )

I've also built this version in my ppa; once it's published you can
verify that this solves the issue by triggering
https://autopkgtest.ubuntu.com/request.cgi?release=oracular&package=wsdd&arch=amd64&trigger=wsdd%2F2%3A0.8-2ubuntu2~ppa1&ppa=aleasto%2Ftests

** Patch added: "wsdd_0.8-2ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071692/+attachment/5798557/+files/wsdd_0.8-2ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073589] Re: Confined executable script needs 'mrix' rule on its shebang only when running inside LXD

** Changed in: wsdd (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073589

Title:
  Confined executable script needs 'mrix' rule on its shebang only when
  running inside LXD

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

** Changed in: wsdd (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069633] Re: package exfatprogs (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man8/exfatlabel.8.gz', which is also in package exfat-utils 1.2.8-1

Where are you getting `exfat-utils` from?
It should not be available in the Noble repositories. `exfatprogs` replaced 
`exfat-utils` many releases ago.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069633

Title:
  package exfatprogs (not installed) failed to install/upgrade: trying
  to overwrite '/usr/share/man/man8/exfatlabel.8.gz', which is also in
  package exfat-utils 1.2.8-1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073783] Re: [MIR] exfatprogs

$ lintian --pedantic exfatprogs_1.2.4-1.dsc   
W: exfatprogs source: newer-standards-version 4.7.0 (current is 4.6.2)
P: exfatprogs source: no-dep5-copyright [debian/copyright]

$ lintian --pedantic exfatprogs_1.2.4-1_amd64.deb
W: exfatprogs: groff-message an.tmac::75: warning: tbl 
preprocessor failed, or it or soelim was not run; table(s) likely not rendered 
(TE macro called with TW register undefined) 
[usr/share/man/man8/mkfs.exfat.8.gz:1]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073783

Title:
  [MIR] exfatprogs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073783] [NEW] [MIR] exfatprogs

Public bug reported:

[Availability]
The package exfatprogs is already in Ubuntu universe.
The package exfatprogs build for the architectures it is designed to work on.
It currently builds and works for all Ubuntu architectures
Link to package https://launchpad.net/ubuntu/+source/exfatprogs

[Rationale]
- The package exfatprogs is required in Ubuntu main as an optional runtime 
dependency of udisks2
- The package exfatprogs will generally be useful for a large part of
  our user base
- Additionally new use-cases enabled by this are out-of-the-box support for 
creating and fixing exFAT volumes: exFAT is commonly used on larger USB drives 
or SD cards; in many cases pre-formatted that way from the manufacturer
- There is no other/better way to solve this that is already in main or
  should go universe->main instead of this.
- The binary package exfatprogs needs to be in main to achieve out-of-the-box 
support for creating and fixing exFAT volumes.

- It would be great and useful to community/processes to have the
  package exfatprogs in Ubuntu main, but there is no definitive deadline.

[Security]
- Had 1 security issues in the past
  - Links to CVE trackers:
https://ubuntu.com/security/CVE-2023-45897
https://security-tracker.debian.org/tracker/CVE-2023-45897
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-45897

- no `suid` or `sgid` binaries
- Binaries dump.exfat, exfat2img, exfatlabel, fsck.exfat, mkfs.exfat, 
tune.exfat in sbin are no problem because they're not suig/sgid; they will be 
executed by the udisks2 daemon
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024).
- Package does not expose any external endpoints

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

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does
  not have too many, long-term & critical, open bugs
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/exfatprogs/+bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=exfatprogs
  - Upstream's bug tracker https://github.com/exfatprogs/exfatprogs/issues
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
RULE: - The package must include a non-trivial test suite
RULE:   - it should run at package build and fail the build if broken
TODO-A: - The package runs a test suite on build time, if it fails
TODO-A:   it makes the build fail, link to build log TBD
TODO-A: - This is WIP involving upstream and debian: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076705

RULE:   - The package should, but is not required to, also contain
RULE: non-trivial autopkgtest(s).
TODO-A: - The package runs an autopkgtest, and is currently passing on
TODO-A:   this TBD list of architectures, link to test logs TBD
TODO-A: - This is also WIP involving upstream and debian: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076705

- The package does have not failing autopkgtests right now

[Quality assurance - packaging]
- debian/watch is present and works
  - I noticed that the debian maintainer is not using the tarball that uscan 
would download, but a different tarball. I'm trying to fix that here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076722

- debian/control defines a correct Maintainer field

- This package does not yield massive lintian Warnings, Errors
  - 
https://launchpadlibrarian.net/735597444/buildlog_ubuntu-oracular-amd64.exfatprogs_1.2.4-1_BUILDING.txt.gz
- Lintian overrides are not present

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

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

- Packaging and build is easy, link to debian/rules
https://git.launchpad.net/ubuntu/+source/exfatprogs/tree/debian/rules

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

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

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

[Maintenance/Owner]
- The owning team will be ~desktop-packages and I have their acknowledgement for
  that commitment
- The future owning team is not yet subscribed, but will subscribe to
  the package before promotion

- This does not use static builds
- This does not use vendored code
- This package is not rust based

- The package has been built within the last 3 months in the archive

- Build link on launchpad:
https://launchpad.net/ubuntu/+source/exfatprogs/1.2.4-1

[Background information]
The Package description explains the package well
Upstream Name is exfatprogs
Link to upstream project https://github.com/exfatprogs/exfatprogs

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

-- 
You received this bug notification because you are a memb

[Bug 2016368] Re: WSDD Package missing UFW application profile

** Changed in: wsdd (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016368

Title:
  WSDD Package missing UFW application profile

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

2024-07-23 Thread Alessandro Astone

Found more differences between a local cloud vm and ubuntu infra...
Verified this works from ppa: 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-aleasto-tests/oracular/amd64/w/wsdd/20240723_070819_f0714@/log.gz


** Patch added: "wsdd_0.8-2ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/2071692/+attachment/5799542/+files/wsdd_0.8-2ubuntu3.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU

2024-07-25 Thread Alessandro Astone

Submitted a fix: https://code.launchpad.net/~aleasto/chromium-
browser/+git/snap-from-source/+merge/470118

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967488

Title:
  [nvidia] Chromium stable snap doesn't display anything on Wayland with
  Nvidia as primary GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061744] Re: Evolution does not handle RSS feeds anymore: libevolution-rss-common.so: cannot open shared object file

2024-07-26 Thread Alessandro Astone

Verified the following binary packages on Ubuntu 24.04 LTS:

evolution-plugins:amd64=3.52.3-0ubuntu1
libevolution:amd64=3.52.3-0ubuntu1
evolution-plugin-pstimport:amd64=3.52.3-0ubuntu1
evolution-plugin-bogofilter:amd64=3.52.3-0ubuntu1
evolution:amd64=3.52.3-0ubuntu1
evolution-common:amd64=3.52.3-0ubuntu1


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061744

Title:
  Evolution does not handle RSS feeds anymore: libevolution-rss-
  common.so: cannot open shared object file

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072547] Re: [SRU] Update evolution to 3.52.3

2024-07-26 Thread Alessandro Astone

Verified the following packages in Ubuntu 24.04 LTS:

evolution-plugins:amd64=3.52.3-0ubuntu1
libevolution:amd64=3.52.3-0ubuntu1
evolution-plugin-pstimport:amd64=3.52.3-0ubuntu1
evolution-plugin-bogofilter:amd64=3.52.3-0ubuntu1
evolution:amd64=3.52.3-0ubuntu1
evolution-common:amd64=3.52.3-0ubuntu1


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072547

Title:
  [SRU] Update evolution to 3.52.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073783] Re: [MIR] exfatprogs

2024-07-26 Thread Alessandro Astone

build tests, autopkgtests, and debian/watch improvements were uploaded
to debian experimental (but not to debian unstable due to the debian
maintainer leaving for vacation).

If we need that sooner we can temporarily branch out from debian,
otherwise we should get it auto-imported in 2~3 weeks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073783

Title:
  [MIR] exfatprogs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU

2024-07-29 Thread Alessandro Astone

Can confirm it's fixed in latest/candidate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967488

Title:
  [nvidia] Chromium stable snap doesn't display anything on Wayland with
  Nvidia as primary GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071692] Re: Confine wsdd with apparmor

2024-07-30 Thread Alessandro Astone

** Changed in: wsdd (Ubuntu)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071692

Title:
  Confine wsdd with apparmor

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075145] [NEW] exfatprogs CVE-2023-45897 backport to jammy

2024-07-30 Thread Alessandro Astone

Public bug reported:

Upon inspection exfatprogs in jammy is affected by CVE-2023-45897 with one of 
the three patched vulnerabilities:
https://ubuntu.com/security/CVE-2023-45897

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

** Affects: exfatprogs (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075145

Title:
  exfatprogs CVE-2023-45897 backport to jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075145] Re: exfatprogs CVE-2023-45897 backport to jammy

2024-07-30 Thread Alessandro Astone

Backport of the patch:
https://github.com/exfatprogs/exfatprogs/commit/ec78688e5fb5a70e13df82b4c0da1e6228d3ccdf

The CVE was released with 3 patches, but only that one seems to apply to
version 1.1.3, while the other patches are for vulnerabilities
introduced in later versions.

** Patch added: "exfatprogs_1.1.3-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/exfatprogs/+bug/2075145/+attachment/5801367/+files/exfatprogs_1.1.3-1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075145

Title:
  exfatprogs CVE-2023-45897 backport to jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found

2024-08-01 Thread Alessandro Astone

This might not end up being related, but interesting nonetheless:
I was hacking on the stable Firefox snap using https://snapcraft.io/overlay

After mounting the overlay `sudo /snap/overlay/current/overlay
$(realpath /snap/firefox/current)` I tried to start firefox and it did
not launch. I haven't seen this happening with other snaps. The journal
contains:

Aug 01 10:40:59 thinkpad kernel: audit: type=1400 audit(1722501659.347:4687): 
apparmor="DENIED" operation="open" class="file" 
profile="snap-update-ns.firefox" name="/proc/379042/maps" pid=379042 comm="5" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 01 10:40:59 thinkpad firefox_firefox.desktop[379021]: Content snap 
command-chain for 
/snap/firefox/4630/gnome-platform/command-chain/desktop-launch not found: 
ensure slot is connected

Do we know if this bug also came with the AppArmor denial?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072395

Title:
  [snap] Chromium with core24 base won't start: desktop-launch not found

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

2024-08-02 Thread Alessandro Astone

** Changed in: ubuntu-drivers-common (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065294] Re: Diagnostics settings flips to Never without any user action

2024-08-02 Thread Alessandro Astone

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

** Also affects: gnome-control-center (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065294

Title:
  Diagnostics settings flips to Never without any user action

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found

2024-08-02 Thread Alessandro Astone

No we don't know, or no it did not have an AppArmor denial? :P

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072395

Title:
  [snap] Chromium with core24 base won't start: desktop-launch not found

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062082] Re: Nvidia drivers fail to install libnvidia-egl-wayland1, resulting in Zink being used

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Status: Triaged => Fix Committed

** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062082

Title:
  Nvidia drivers fail to install libnvidia-egl-wayland1, resulting in
  Zink being used

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062082] Re: Nvidia drivers fail to install libnvidia-egl-wayland1, resulting in Zink being used

** Description changed:

+ [ Impact ]
+ 
+ In a Ubuntu 24.04 system with NVIDIA as the sole GPU, graphical programs
+ in the GNOME Wayland session will use MESA's Zink as the OpenGL driver.
+ 
+ [ Test Plan ]
+ 
+  * Log into the Wayland session from a machine with an NVIDIA GPU and no
+ other GPU (such as integrated graphics, or iGPU).
+ 
+  * In a terminal window run `eglinfo -B -p wayland`
+ 
+  * Verify that there are no mentions of "zink" in the output
+ 
+ [ Where problems could occur ]
+ 
+ The fix is being included as part of a new nvidia driver release, so
+ unrelated regressions from that version upgrade may show up.
+ 
+ 
+ [ Original description ]
+ 
  Apologies if I have misfiled this bug - this is a report of an issue
  affecting Wayland in Ubuntu 24.04 beta.
  
  Using 24.04 beta logging in with Wayland. Nautilus has very significant
  performance issues. Doesn't happen when logging in with Xorg instead of
  Wayland.
  
  Opening Nautilus windows - including normal windows navigation, and the
  file download location dialogue in things like Chrome - extremely slow.
  Takes approx. 10 seconds to process user double clicking to open folder.
  Attempting to drag folder across screen usually doesn't work, or takes a
  very long time.
  
  Not very skilled at debugging, but programmes like Gimp, which has its
  own built-in folder explorer for choosing a location to save an image,
  do not have this problem. Ubuntu 24.04 with X does not have this
  problem. No performance issues have been noticed with folder navigation,
  stat'ing files etc. over the command line. It is only nautilus and
  Wayland that give me this issue, so I suspect it is not an issue with my
  SSD.
  
  The following output was observed when starting nautilus over the
  command line:
  
  /home/me/ $ nautilus .
  ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files
  libEGL warning: egl: failed to create dri2 screen
  
- 
- After approx. 10 seconds, the folder opened on screen. I double clicked on a 
sub directory, and it took about 9 seconds to open.
+ After approx. 10 seconds, the folder opened on screen. I double clicked
+ on a sub directory, and it took about 9 seconds to open.
  
  I have attempted to show that this is not an issue with my SSD here:
  
  /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date;
  Wed Apr 17 11:58:16 PM BST 2024
  foo.txt
  Wed Apr 17 11:58:16 PM BST 2024
  
  As you can see, no unusual slowdown was observed.
  
  Obtaining the following setting for my bug report, I note that the
  'Settings' GUI utility is among the areas affect by my very significant
  system slowdown. I have copied some details about my system including
  its graphics card in case that helps.
  
  # System Details Report
  ---
  
  ## Report details
  - **Date generated:**  2024-04-17 23:59:54
  
  ## Hardware Information:
  - **Hardware Model:**  ASUS ROG STRIX B550-F 
GAMING
  - **Memory:**  32.0 GiB
  - **Processor:**   AMD Ryzen™ 7 5800X × 16
  - **Graphics:**zink Vulkan 1.3(NVIDIA 
GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY))
  - **Disk Capacity:**   2.0 TB
  
  ## Software Information:
  - **Firmware Version:**2006
  - **OS Name:** Ubuntu Noble Numbat 
(development branch)
  - **OS Build:**(null)
  - **OS Type:** 64-bit
  - **GNOME Version:**   46
  - **Windowing System:**Wayland
  - **Kernel Version:**  Linux 6.8.0-22-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  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..09.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  545.29.06  Thu Nov 16 
01:59:08 UTC 2023
-  GCC version:
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 
01:59:08 UTC 2023
+  GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 23:44:47 2024
  DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources()
  Di

[Bug 2063827] Re: Gnome apps segfault in Nvidia (535) Wayland sessions on Noble, but 550 works

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Status: Triaged => Fix Committed

** Description changed:

+ [ Impact ]
+ 
+ Graphical programs in the GNOME Wayland session crash in a Ubuntu 24.04
+ system with NVIDIA as the sole GPU and the NVIDIA 535 driver.
+ 
+ [ Test Plan ]
+ 
+  * Log into the Wayland session from a machine with an NVIDIA GPU and no
+ other GPU (such as integrated graphics, or iGPU).
+ 
+  * Run a graphical application such as `gnome-control-center` or
+ `nautilus`
+ 
+  * Verify that the application opens without crashing.
+ 
+ [ Where problems could occur ]
+ 
+ The fix is being included as part of a new nvidia driver release, so
+ unrelated regressions from that version upgrade may show up.
+ 
+ 
+ [ Original description ]
+ 
  Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome
  Control Center does not open on Wayland, but does on Xorg, attempting to
  open it will simply open the crash dialog after some time.
  
  When running from the terminal:
  
- $ gnome-control-center 
+ $ gnome-control-center
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)
  
  Version installed:
  
  gnome-control-center:
-   Installed: 1:46.0.1-1ubuntu7
-   Candidate: 1:46.0.1-1ubuntu7
+   Installed: 1:46.0.1-1ubuntu7
+   Candidate: 1:46.0.1-1ubuntu7
  
  My current installation is very lightweight, and I haven't removed any
  packages or changed any system files.
  
  This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB
  with the driver version being 535.171.04
  
  If more information is needed, please let me know, however I might be
  slow to respond.
  
  Thank you.

** Description changed:

  [ Impact ]
  
  Graphical programs in the GNOME Wayland session crash in a Ubuntu 24.04
  system with NVIDIA as the sole GPU and the NVIDIA 535 driver.
  
  [ Test Plan ]
  
-  * Log into the Wayland session from a machine with an NVIDIA GPU and no
+  * Log into the Wayland session from a machine with an NVIDIA GPU and no
  other GPU (such as integrated graphics, or iGPU).
  
-  * Run a graphical application such as `gnome-control-center` or
+  * Run a graphical application such as `gnome-control-center` or
  `nautilus`
  
-  * Verify that the application opens without crashing.
+  * Verify that the application opens without crashing.
  
  [ Where problems could occur ]
  
- The fix is being included as part of a new nvidia driver release, so
- unrelated regressions from that version upgrade may show up.
- 
+ The fix should be distributed as a simple new library dependency, with
+ low risk of side effects.
  
  [ Original description ]
  
  Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome
  Control Center does not open on Wayland, but does on Xorg, attempting to
  open it will simply open the crash dialog after some time.
  
  When running from the terminal:
  
  $ gnome-control-center
  libEGL warning: egl: failed to create dri2 screen
  Segmentation fault (core dumped)
  
  Version installed:
  
  gnome-control-center:
    Installed: 1:46.0.1-1ubuntu7
    Candidate: 1:46.0.1-1ubuntu7
  
  My current installation is very lightweight, and I haven't removed any
  packages or changed any system files.
  
  This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB
  with the driver version being 535.171.04
  
  If more information is needed, please let me know, however I might be
  slow to respond.
  
  Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827

Title:
  Gnome apps segfault in Nvidia (535) Wayland sessions on Noble, but 550
  works

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu-appindi

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064698

Title:
  Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error
  occurred in Get [### Promise created here: ###
  getProperty@file:///usr/share/gnome-shell/extensions/ubuntu-
  appindicat...@ubuntu.com/dbusProxy.js:89:33]

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072395] Re: [snap] Chromium with core24 base won't start: desktop-launch not found

2024-08-07 Thread Alessandro Astone

Actually I see `apparmor="DENIED" operation="open" class="file"
profile="snap-update-ns.firefox" name="/proc/379042/maps" pid=379042
comm="5" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0` in my
journal for all snaps, so might not be the cause afterall.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072395

Title:
  [snap] Chromium with core24 base won't start: desktop-launch not found

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065294] Re: Diagnostics settings flips to Never without any user action

2024-08-08 Thread Alessandro Astone

** Description changed:

+ [ Impact ]
+
+ In GNOME Settings' Diagnostics page, the switch to control automatic bug
+ reporting to Canonical automatically flips to "Never" after 1 minute of
+ the page being open without interaction
+
+ The bug triggered because the DBus service that manages the
automatic-bug-reporting configuration ("whoopsie-preferences") quits after 1
minute of inactivity, and GNOME Settings receives an "invalidation" signal when
that happens.
+ We are fixing the issue by detecting that the service has quit in which case
we should not refresh the state of the setting.
+
+ A further change should be applied to the whoopsie-preferences service
+ to avoid quitting when there are clients still listening for potential
+ settings changes.
+
+ [ Test Plan ]
+
+ * Open GNOME Settings -> Privacy & Security -> Diagnostics
+
+ * You should see `Send error reports to Canonical` set to `Manual` by
default.
+> If instead it is set to Never, change it now to another option.
+
+ * Stay on the settings page for more than 60 seconds
+
+ * The setting should have remained the same and *not* have
+ automatically changed to `Never`.
+
+ [ Where problems could occur ]
+
+ This patch also tries to re-start the "whoopsie-preferences" daemon when
+ it automatically stops after 60 seconds, because GNOME Settings should
+ keep listening for settings changes from external factors. This should
+ not present any issues, but it's the most "intrusive" part of the patch.
+
+
+ [ Original Description ]
steps to reproduce.
1. Open Gnome Settings
2. Go to Privacy -> Diagnostics
3. You should see `Send error reports to Canonical` set to Manual by default.
4. Stay on the settings page for some time (maybe <2 mins), the setting will
slip to Never.

You could also try to change the settings to Automatic and stay on the
page, it will also flip to Never within a couple of minutes.

I noticed this on Jammy, Mantic, and Noble.

** Also affects: whoopsie-preferences (Ubuntu)
Importance: Undecided
Status: New

** Changed in: whoopsie-preferences (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: whoopsie-preferences (Ubuntu)
Status: New => Triaged

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

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

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065294

Title:
Diagnostics settings flips to Never without any user action

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076428] [NEW] Enable CONFIG_EXFAT_FS in s390x too

2024-08-09 Thread Alessandro Astone

Public bug reported:

There doesn't seem to be a specific reason for keeping this disabled in
s390x.

The Desktop Team is looking to MIR exfatprogs and include it in the Desktop 
image.
Autopkgtests detected missing support for CONFIG_EXFAT_FS in s390x when trying 
to mount an exfat image.

We should be able to just enable it in s390x making it match all other
Ubuntu architectures.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076428

Title:
  Enable CONFIG_EXFAT_FS in s390x too

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076428] Re: Enable CONFIG_EXFAT_FS in s390x too

2024-08-09 Thread Alessandro Astone

** Description changed:

- There doesn't seem to be a specific reason for keeping this disabled in
- s390x.
- 
  The Desktop Team is looking to MIR exfatprogs and include it in the Desktop 
image.
  Autopkgtests detected missing support for CONFIG_EXFAT_FS in s390x when 
trying to mount an exfat image.
  
- We should be able to just enable it in s390x making it match all other
- Ubuntu architectures.
+ There doesn't seem to be a specific reason for keeping this disabled in s390x.
+ We should be able to just enable it in s390x making it match all other Ubuntu 
architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076428

Title:
  Enable CONFIG_EXFAT_FS in s390x too

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072771] Re: Update gnome-remote-desktop to 46.3

2024-08-09 Thread Alessandro Astone

Verified gnome-remote-desktop=46.3-0ubuntu1 on Ubuntu 24.04 LTS against
the test plans "Basic RDP Test Case" and "Basic Remote Login Test Case
(For Ubuntu 24.04 LTS and later only)"

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072771

Title:
  Update gnome-remote-desktop to 46.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072596] Re: long delay when first installing version 46

On Ubuntu 24.04 LTS:
- Verified using the Test Case that I could reproduce the issue with version 
46.2-1~ubuntu24.04.2
- Verified using the Test Case that the issue is fixed with version 
46.3-0ubuntu1

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072596

Title:
  long delay when first installing version 46

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072782] Re: Update gnome-online-accounts to 3.50.4

Verified version 3.50.4-0ubuntu2 of:

libgoa-1.0-common:amd64
libgoa-1.0-0b:amd64
libgoa-backend-1.0-2:amd64
gnome-online-accounts:amd64

in Ubuntu 24.04 LTS

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072782

Title:
  Update gnome-online-accounts to 3.50.4

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075553] Re: gnome-text-editor crashed with SIGSEGV in editor_text_buffer_spell_adapter_invalidate_all() from editor_document_load_notify_completed_cb() from g_closure_invoke() from g_hash_table_

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075553

Title:
  gnome-text-editor crashed with SIGSEGV in
  editor_text_buffer_spell_adapter_invalidate_all() from
  editor_document_load_notify_completed_cb() from g_closure_invoke()
  from g_hash_table_lookup_node() from g_hash_table_lookup()

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075553] Re: gnome-text-editor crashed with SIGSEGV in editor_text_buffer_spell_adapter_invalidate_all() from editor_document_load_notify_completed_cb() from g_closure_invoke() from g_hash_table_

** Changed in: gnome-text-editor (Ubuntu Noble)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075553

Title:
  gnome-text-editor crashed with SIGSEGV in
  editor_text_buffer_spell_adapter_invalidate_all() from
  editor_document_load_notify_completed_cb() from g_closure_invoke()
  from g_hash_table_lookup_node() from g_hash_table_lookup()

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075553] Re: gnome-text-editor crashed with SIGSEGV in editor_text_buffer_spell_adapter_invalidate_all() from editor_document_load_notify_completed_cb() from g_closure_invoke() from g_hash_table_