Installing the scdaemon package solves the issue.
scdaemon seems to be a mandatory dependency of gpg-agent, it should be
added to the dependency chain
** Changed in: seahorse (Ubuntu)
Status: New => Triaged
** Changed in: seahorse (Ubuntu)
Assignee: (unassigned) => Alessandro
Package: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: seahorse (Ubuntu)
Importance: Undecided
Assignee: Alessandro Astone (aleasto)
Status: Triaged
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification bec
This might have been a very unfortunate timing coincidence. After
waiting for over an hour for the key to appear on keyserver.ubuntu.com I
installed scdaemon, synced the keys again, and it immediately appeared
on the server.
I'm trying with a new key now, let's see if it appears on the server afte
Well, I cannot get any new key to show up regardless of scdaemon now. It
would seem to be on the mercy of the server, probably not a bug here.
** Changed in: seahorse (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Description changed:
- .
+ [ Impact ]
+
+ * This is a new stable release in the 46 series.
+
+https://gitlab.gnome.org/GNOME/gnome-calculator/-/blob/46.1/NEWS
+
+
+ [ Test Plan ]
+
+ * Complete the test case from
+ https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeCalculator
+
+ [
Public bug reported:
[ Impact ]
* This is a new stable release in the 46 series.
https://gitlab.gnome.org/GNOME/evince/-/blob/46.3/NEWS
[ Test Plan ]
* Complete the test case from
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Evince
[ Where problems could occur ]
* Evince is pre-instal
Public bug reported:
Impact
--
This is a new stable release in the 3.52 series.
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.52.2/NEWS
Test Case
-
Install the update
Log out and log back in (or restart)
Ensure that GNOME Calendar and Evolution still work fine.
You ma
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,
whi
** 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 follow
** 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 follow
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
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
Desktop Bugs, wh
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-21t6
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
Desktop Bugs, which is subscribed to evolution in Ubuntu.
http
** Changed in: evolution (Ubuntu Noble)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/2072547
Title:
[SRU] Update evolution to 3.52.3
T
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
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
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-0u
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
** 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 receive
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
ht
s (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 Jamm
> it looks like it only knows how to switch GLX (Xorg sessions) and not
EGL (Wayland sessions)
Then why is this specific to nvidia?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs
Ah well, because for mesa drivers you don't need to fiddle with glvnd.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2076975
Title:
switcherooctl and "Launch using Discrete Gr
nce: Undecided
Assignee: Alessandro Astone (aleasto)
Status: In Progress
** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
Status: New => Triaged
** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone
** Changed in: gnome-shell-extension-appindicator (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/206469
** Description changed:
+ [ Impact ]
+
+ Chromium and Electron apps implement the KStatusNotifierItem spec without
exposing some DBus properties that the spec describes.
+ The app-indicator feature can work without those properties, but
gnome-shell-extension-appindicator will log a big error me
** Changed in: whoopsie-preferences (Ubuntu Jammy)
Status: New => Triaged
** Changed in: whoopsie-preferences (Ubuntu Noble)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5616
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2065294
Title:
Diagnostics settings flips to Ne
Could you try downgrading `ubuntu-drivers-common` to see if it's a
regression there?
Here's a link to the previous build:
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.7.6ubuntu3/+build/28021470/+files/ubuntu-drivers-
common_0.9.7.6ubuntu3_arm64.deb
--
You received this bug n
Sorry for the link, arm64 and amd64 are too similar looking!
Thanks for the test, it's good info.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2077530
Title:
Gnome-shell sud
.
** Also affects: xdg-desktop-portal-gnome (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Status: New => Triaged
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Tags a
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't lau
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don'
Can you try https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3997
?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2080073
Title:
47rc: unable to resize mattermost, discord w
** 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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
> 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 n
> 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 sou
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 eglGe
** 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)
** Tags added: udeng-1202
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2080282
Title:
Apps run on the discrete Nvidia GPU by default instead of the Intel
integrated GPU
To
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, rat
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-contr
*** 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-c
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 work
** 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
**
** 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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: udeng-1202
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in 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 ab
Thank you for the bug report.
I've verified the issue and understand the cause.
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** Changed in: gnome-con
** Changed in: nautilus (Ubuntu)
Status: Fix Released => In Progress
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Description changed:
Can't move file/directory by drag and drop by using a touch monitor
+
+ As of 24.10 you can drag a file around but you cannot drop it into a
+ directory.
OS: 22.04, up to date @ Mar 28, 2022.
nautilus: 1:42~rc-1-ubuntu1
mode: wayland
--
You received this bug n
** Tags added: udeng-4891
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2084554
Title:
touchscreen drag-select is interrupted by context menu
To manage notifications about this
** Tags removed: udeng-4073
** Tags added: udeng-4959
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635
Title:
can't move file/directory by drag and drop by using touch monitor
Status: Fix Released
** Affects: nautilus (Ubuntu Noble)
Importance: Undecided
Assignee: Alessandro Astone (aleasto)
Status: In Progress
** Tags: udeng-4891
** Also affects: nautilus (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: nautilus (Ubuntu
nautilus (Ubuntu)
Status: Won't Fix => Fix Released
** Changed in: nautilus (Ubuntu Noble)
Status: New => In Progress
** Changed in: nautilus (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: nautilus (Ubuntu)
Importan
** Description changed:
- Context:
-
- I usually set the lock delay to 30 minutes, and do it via gsettings since
GNOME Settings allows values of 15 min max.
+ [ Impact ]
- Problem:
-
- This value is reset to "uin
** Changed in: gnome-control-center (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2083869
Title:
Screen Blank del
ontrol-center (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gnome-control-center (Ubuntu Noble)
Milestone: None => noble-updates
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-co
** Description changed:
[ Impact ]
I usually set the lock delay to 30 minutes, and do it via gsettings
since GNOME Settings allows values of 15 min max.
This value is reset to "uint32 0" (zero) when I click the tab Privacy &
Security in GNOME Settings. Since the change happens sile
trol-center (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: gnome-control-center (Ubuntu Noble)
Importance: Undecided
Assignee: Alessandro Astone (aleasto)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Verified the test plan with gnome-control-
center{,-data,-faces}=1:46.4-0ubuntu0.24.04.1 on Ubuntu 24.04.1 LTS
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Verified the test plan with gnome-control-
center{,-data,-faces}=1:41.7-0ubuntu0.22.04.9 on Ubuntu 22.04.5 LTS
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of
** Tags added: udeng-5009
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2085143
Title:
/usr/libexec/gsd-
power:11:__GI___libc_free:g_hash_table_unref:g_hash_table
** Tags added: 1202
** Tags removed: 1202
** Tags added: udeng-5009
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2085061
Title:
gsd-power crashed with SIGSEGV in g
Very similar crash but when freeing `proxy->priv->properties` instead of
`proxy->priv->expected_interface`: https://launchpad.net/bugs/2085143
** Tags added: 1202
** Tags removed: 1202
** Tags added: udeng-5009
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
This seems very related to https://launchpad.net/bugs/2085060, probably the
same bug.
But I really can't see anything wrong with how gsd-power uses gdbus...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubun
** Changed in: mutter (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ub
ess
** Changed in: mutter (Ubuntu Noble)
Status: New => In Progress
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: mu
This was already fixed in GNOME 47 and thus it's not an issue in
Oracular.
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Fix Released
** Changed in: gnome-control-center (Ubuntu)
Milestone: oracular-updates => None
--
You received this bug notification because you a
** Changed in: gdm3 (Ubuntu)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gdm3 (Ubuntu)
Milestone: None => jammy-updates
--
You received this bug notification because you are a member
There's a stack explosion because of a cyclic loop of CoglFramebuffer*
dependencies:
framebuffer=0x606abb7a52f0
has priv->deps [framebuffer=0x606abf70fe20, ...]
which has priv->deps [framebuffer=0x606abb7a52f0, ...]
--
You received this bug notification because you are a member of Ubuntu
Desktop
Thank you for looking into this: your results confirm my theory.
Indeed the rules are racy so the result depends on the ordering of events.
Your fix seems correct, however we're going in another direction:
We got feedback that the Ubuntu certified laptops with hybrid graphics
all got certified wit
Currently upower is a required dependency of:
gnome-applets
gnome-session-bin
gnome-power-manager
It is also a Recommends for gnome-settings-daemon, through gnome-
settings-daemon → libupower-glib3 → upower.
The logic did not take into account that connecting to UPower might
fail, so
** Description changed:
+ Stacktrace
+
+ #0 0x7093e8ab3395 in __GI___libc_free (mem=0x361101620) at
./malloc/malloc.c:3375
+ ar_ptr =
+ p =
+ err =
+ #1 0x7093e8e1c04c in g_hash_table_unref (hash_table=0x558b610fda00) at
../../../glib/ghash.c:1442
+
** Description changed:
+ Stacktrace
+
+ #0 g_hash_table_lookup_node (hash_table=0x58ffa9856880, key=0x7e16cc008b80,
hash_return=) at ../../../glib/ghash.c:428
+ node_hash =
+ hash_value = 288199634
+ have_tombstone = 0
+ step = 0
+ node_index = 1
+
** Description changed:
+ Stacktrace
+
+ #0 0x7ad719ab3395 in __GI___libc_free (mem=0xbf293fbb0) at
./malloc/malloc.c:3375
+ ar_ptr =
+ p =
+ err =
+ #1 0x7ad719e1c04c in g_hash_table_unref (hash_table=0x5770f293bf10) at
../../../glib/ghash.c:1442
+
Oct 29 15:23:39 drakkar gvfsd-wsdd[801574]: Failed to spawn the wsdd daemon:
Failed to execute child process “wsdd” (No such file or directory)
Oct 29 15:23:39 drakkar gvfsd-network[801519]: Couldn't create directory
monitor on wsdd:///. Error: Automount failed: Failed to spawn the underlying
ws
See https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929
The verification of the gdm update that was supposed to make Wayland the
default option was not done correctly:
We can see that all comments between #37 and #45 mention that Xorg was still
their default but that they now had the opt
Actually, I don't think Wayland was disabled but just not the default.
So we need another explanation. Luckily I got another explanation :)
Both the default Xorg and the default Wayland sessions are called
"ubuntu.desktop" (under /usr/share/xsessions/ and /usr/share/wayland-sessions/
respectivel
*** This bug is a duplicate of bug 2085610 ***
https://bugs.launchpad.net/bugs/2085610
** This bug has been marked a duplicate of bug 2085610
/usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:g_static_resource_fini:g_static_resource_fini:_sub_D_65535_1
--
You r
> The default session type is meant to be remembered. So GDM's preference of
> default should actually be irrelevant if the user has ever logged in prior to
> the kernel update.
>
> If previous successful logins used Xorg and suddenly it's going to Wayland
> then perhaps the attempt to use Xorg
** Description changed:
[ Impact ]
+ This is a minor point release update for Gnome Control Center, which has
+ a minor release exception:
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME.
+
+ https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.5/NEWS
+
+ https://gitlab.gnome.
uest it at http://forms.canonical.com/reports/.
** Changed in: gnome-control-center (Ubuntu)
Status: New => In Progress
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Also affects: gnome-control-center (Ubuntu Noble)
Importance: Un
** Description changed:
- Hello,
+ [ Impact ]
Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer possible
to restart gnome-shell without crashing the session. The only way not to
- crash it is to close all applications before restarting gnome-shell. I
- have verified this too.
** Changed in: mutter (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Tags added: udeng-5206
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
: Alessandro Astone (aleasto)
Status: New
** Also affects: gnome-control-center (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-control-center (Ubuntu Noble)
Assignee: (unassig
signee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: nvidia-graphics-drivers-560 (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Bug watch added: gitlab.gnome.org/GNOME/gn
Public bug reported:
tbd.
** Affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2081735
Title:
[FFE] Enable wsdd b
** Description changed:
- tbd.
+ The wsdd backend in gvfs allows Nautilus, and potentially other clients,
+ to discover Windows 10+ network folders (SMB), using the WS-Discovery
+ protocol.
+
+ gvfs implements this feature by using `wsdd` if it is installed. This
+ change thus adds wsdd as a Reco
> That's bug 2062082 but I'm not sure how much it matters on Jammy.
There's no fallback-to-zink in jammy, so it would fall back to swrast instead.
However that's an issue for single-NVIDIA systems, while on hybrids it should
pick the integrated GPU.
--
You received this bug notification because
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #1001
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1001
** Also affects: gnome-calendar via
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1001
Importance: Unknown
Status: Unknown
--
You received
I'm able to reproduce the bug in 24.04.1
It appears to be already fixed in GNOME 47 because I cannot reproduce in 24.10
** No longer affects: gnome-shell (Ubuntu)
** Also affects: gnome-calendar (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: gnome-calendar (Ubuntu O
Verified the test plan against gnome-shell-extension-
appindicator=58-1ubuntu24.04.1 on Ubuntu 24.04.1 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 U
I get good performance with Nvidia 560 on both kernel 6.11.0 and 6.8.0.
This was a fresh install of Oracular, using a Pascal card.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/208114
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
Also, please open a new bug because this bug report affected GSK_RENDERER=gl
while your issue does not.
I suspect the new bug is with Vulkan, which verifying that GSK_RENDERER=ngl
works should definitively
** Changed in: gnome-control-center (Ubuntu Jammy)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2065
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
Thanks!
For what we know nvidia-driver-560 is the best fit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bug
All gtk-4 apps are affected when using the default renderer
GSK_RENDERER=vulkan, only with nvidia-driver-560.
GSK_RENDERER=ngl doesn't crash.
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
> Using: GSK_RENDERER=gl baobab doesn't crash.
Can you also try GSK_RENDERER=ngl?
Also please limit the tests to drivers available in the Ubuntu archive
like 535, 550 and 560, to avoid inserting more varia
> It seems to work with Intel graphics card, but when using the Nvidia
one instead (RTX 4080 on laptop, with drivers 560), nothing happens.
Can you expand on this?
Is the machine with the "Intel graphics card" a different machine than
the Nvidia laptop? Or is it the same machine where you are usi
1 - 100 of 331 matches
Mail list logo
