[Bug 1084643] Re: Colour casting on black text using the default renderer pdftops (workaround: use gs)
[Expired for poppler (Ubuntu) because there has been no activity for 60 days.] ** Changed in: poppler (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1084643 Title: Colour casting on black text using the default renderer pdftops (workaround: use gs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1084643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1540941] Re: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which
[Expired for adwaita-icon-theme (Ubuntu) because there has been no activity for 60 days.] ** Changed in: adwaita-icon-theme (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1540941 Title: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1540941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1540941] Re: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which
[Expired for One Hundred Papercuts because there has been no activity for 60 days.] ** Changed in: hundredpapercuts Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1540941 Title: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1540941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916341] Re: poppler-utils/pdfimages list function names the wrong color in output table
[Expired for poppler (Ubuntu) because there has been no activity for 60 days.] ** Changed in: poppler (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1916341 Title: poppler-utils/pdfimages list function names the wrong color in output table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
Sponsored to impish and hirsute. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-terminal (Ubuntu) Assignee: Iain Lane (laney) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: gnome-terminal (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: gnome-terminal (Ubuntu Hirsute) Assignee: Iain Lane (laney) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946175] [NEW] gnome disk cannot read SMART data (and self tests) from nvme
Public bug reported: It is impossible to select "SMART data and self test" option for nvme disks. Nvme disks are becoming more common and this functionality should be added. I was able to read smart data from my nvme SSD using HDSentinel (linux version). So it certainly can be done. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1946175 Title: gnome disk cannot read SMART data (and self tests) from nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1946175/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946049] Re: Caps LED ON but caps lock is disabled after logout
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4667 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1946049 Title: Caps LED ON but caps lock is disabled after logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1946049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
Thanks. That's not the GNOME onscreen keyboard so can you tell us which package you installed to get that keyboard? ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946150] [NEW] Seg fault on Select > Grow
Public bug reported:
```
GNU Image Manipulation Program version 2.10.22
git-describe: GIMP_2_10_20-217-g0c8a7891f7
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
10.2.1-23ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210312 (Ubuntu 10.2.1-23ubuntu1)
# Libraries #
using babl version 0.1.86 (compiled against version 0.1.86)
using GEGL version 0.4.28 (compiled against version 0.4.28)
using GLib version 2.68.1 (compiled against version 2.67.5)
using GdkPixbuf version 2.42.2 (compiled against version 2.42.2)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.48.2 (compiled against version 1.48.2)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 1177601 - Thread 1177601 #
[New LWP 1177604]
[New LWP 1177605]
[New LWP 1177606]
[New LWP 1177607]
[New LWP 1177608]
[New LWP 1177609]
[New LWP 1177611]
[New LWP 1177624]
__libc_read (nbytes=256, buf=0x7ffc23858e10, fd=17) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1LWP 1177601 "gimp-2.10"__libc_read (nbytes=256, buf=0x7ffc23858e10,
fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
2LWP 1177604 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3LWP 1177605 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4LWP 1177606 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5LWP 1177607 "gmain"0x7f1f0cf2d22f in __GI___poll
(fds=0x55586ff00450, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
6LWP 1177608 "dconf worker" 0x7f1f0cf2d22f in __GI___poll
(fds=0x55586ff03080, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
7LWP 1177609 "gdbus"0x7f1f0cf2d22f in __GI___poll
(fds=0x7f1ee8016cf0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
8LWP 1177611 "async"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9LWP 1177624 "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 9 (LWP 1177624 "swap writer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f1f0d228dd3 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f1f0d724fed in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f1f0d209901 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f1f0d016450 in start_thread (arg=0x7f1efaffd640) at
pthread_create.c:473
ret =
pd = 0x7f1efaffd640
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139771036816960,
6348358488871504876, 140720904443806, 140720904443807, 0, 139771036816960,
-6475028826831877140, -6473928399146087444}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
#5 0x7f1f0cf38d53 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 8 (LWP 1177611 "async"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f1f0d228dd3 in g_cond_wait () from
[Bug 1945700] Re: [DisplayLink] Settings for multiple displays do not persist
Interestingly, the problem disappears when using Xorg, so it seems to be only with Wayland. -- 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/1945700 Title: [DisplayLink] Settings for multiple displays do not persist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1945700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()
Reported upstream as https://gitlab.gnome.org/GNOME/gdm/-/issues/739 now ** Changed in: gdm3 (Ubuntu) Importance: Medium => High ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #739 https://gitlab.gnome.org/GNOME/gdm/-/issues/739 ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Triaged ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/739 Importance: Unknown Status: Unknown -- 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/1945061 Title: gdm3 crashed with SIGSEGV in ensure_display_for_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1945061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946140] [NEW] /usr/libexec/xdg-desktop-portal-gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to
*** This bug is a duplicate of bug 1945871 *** https://bugs.launchpad.net/bugs/1945871 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xdg-desktop-portal-gtk. This problem was most recently seen with package version 1.8.0-1, the problem page at https://errors.ubuntu.com/problem/07bd19f1fc495e9223ca4bf47fba4c00fa2f72f5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan focal groovy hirsute impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1946140 Title: /usr/libexec/xdg-desktop-portal- gtk:11:gdk_window_set_transient_for:popover_realize:popover_realize:_gtk_window_add_popover:gtk_popover_update_relative_to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1946140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946130] Re: Opening a new tab changes environment
*** This bug is a duplicate of bug 1922839 *** https://bugs.launchpad.net/bugs/1922839 ** This bug has been marked a duplicate of bug 1922839 Opening new tab in gnome-terminal launched from nautilus loses most environment variables -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1946130 Title: Opening a new tab changes environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1946130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938605] Re: Gnome Terminal "Copy As HTML" produces HTML containing depreciated features
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938605 Title: Gnome Terminal "Copy As HTML" produces HTML containing depreciated features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1938605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946130] [NEW] Opening a new tab changes environment
Public bug reported: Steps to reproduce 1. Open the file manager 2. Right click -> Open in Terminal 3. In the terminal type "echo $USER", then press enter. The user name is printed in the line below. 5. Right click in the terminal, select New Tab. 6. In the terminal type "echo $USER", then press enter. An empty line is printed. Expected result: in step 6 the user name should be printed. There are many other environment variables affected. As a result many programs can't be executed or don't behave properly in the second tab. When the terminal is launched from the dash, new tabs work as expected. Only terminals launched from nautilus are affected. I tried to file this against nautilus-extension-gnome-terminal but launchpad tells me the package does not exist. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Oct 5 19:31:06 2021 InstallationDate: Installed on 2020-05-05 (518 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1946130 Title: Opening a new tab changes environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1946130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
** Also affects: gtk+3.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** No longer affects: gtk+3.0 (Ubuntu Hirsute) ** Changed in: gtk+3.0 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1922464 Title: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings- daemon.plugins.xsettings' does not contain a key named 'antialiasing' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
This bug was fixed in the package gssproxy - 0.8.2-2ubuntu0.20.04.1 --- gssproxy (0.8.2-2ubuntu0.20.04.1) focal; urgency=medium * d/p/0001-Fix-handling-of-selinux-context-when-NULL.patch: Fix handling of SELinux context when NULL. Do not segfault when gssproxy is called by rpc.gssd. (LP: #1788459) -- Sergio Durigan Junior Wed, 30 Jun 2021 13:33:56 -0400 ** Changed in: gssproxy (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
This bug was fixed in the package gssproxy - 0.8.2-2ubuntu0.21.04.1 --- gssproxy (0.8.2-2ubuntu0.21.04.1) hirsute; urgency=medium * d/p/0001-Fix-handling-of-selinux-context-when-NULL.patch: Fix handling of SELinux context when NULL. Do not segfault when gssproxy is called by rpc.gssd. (LP: #1788459) -- Sergio Durigan Junior Wed, 30 Jun 2021 14:44:13 -0400 ** Changed in: gssproxy (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo
Updated and tested. There is no crash at logout or restart Den tis 5 okt. 2021 kl 17:05 skrev Launchpad Bug Tracker < 1943...@bugs.launchpad.net>: > This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 > > --- > gnome-shell (40.5-1ubuntu2) impish; urgency=medium > > [ Daniel van Vugt ] > * debian/patches: Avoid full meta context finalization. > To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, > #1942121, > LP: #1943406, #1944054, #1945010, #1945116, #1944388) > > -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 > 04:52:11 +0200 > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Fix Released > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1944583). > https://bugs.launchpad.net/bugs/1943406 > > Title: > [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in > release_expired_buffers_locked() from pb_cache_add_buffer() from > pb_destroy() from pb_reference_with_winsys() from > radeon_bo_reference() > > Status in Mutter: > Unknown > Status in gnome-shell package in Ubuntu: > Fix Released > > Bug description: > The Ubuntu Error Tracker has been receiving reports about a problem > regarding gnome-shell. This problem was most recently seen with package > version 40.2-1ubuntu6, the problem page at > https://errors.ubuntu.com/problem/17edbc90dd7001a4a55edc878d9b3719dd3a4815 > contains more details, including versions of packages affected, stacktrace > or traceback, and individual crash reports. > If you do not have access to the Ubuntu Error Tracker and are a software > developer, you can request it at http://forms.canonical.com/reports/. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1943406/+subscriptions > > -- Skickat från min Sony Xperia eller Ubuntu -- 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/1943406 Title: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo_reference() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1943406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() fr
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942121] Re: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group()
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1942121 Title: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo_ref
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1943406 Title: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo_reference() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1943406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944054] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in list_del() from destroy_buffer_locked() from release_expired_buffers_locked() from pb_cache_add_buffer()
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1944054 Title: [vmwgfx] gnome-shell crashed with SIGSEGV in list_del() from destroy_buffer_locked() from release_expired_buffers_locked() from pb_cache_add_buffer() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1944054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944388] Re: gnome-shell crashed with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach()
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1944388 Title: gnome-shell crashed with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1944388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945010] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy()
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1945010 Title: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945116] Re: [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release() from old_intel_miptree_release() from intel_free_texture_image_buffer()
This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 --- gnome-shell (40.5-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * debian/patches: Avoid full meta context finalization. To workaround (prevent) shutdown crashes (LP: #1936826, #1942031, #1942121, LP: #1943406, #1944054, #1945010, #1945116, #1944388) -- Marco Trevisan (Treviño) Tue, 05 Oct 2021 04:52:11 +0200 ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1945116 Title: [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release() from old_intel_miptree_release() from intel_free_texture_image_buffer() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945116/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933168] Re: Show Applications button does not bring up application after setting show-favorites to false
let's be realistic while it would be nice to fix we don't have the resources to commit to it, we could still help uploading if someone want to work on cherry picking a fix though ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Status: Confirmed => Incomplete ** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1933168 Title: Show Applications button does not bring up application after setting show-favorites to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1933168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
This is 100% scale ** Attachment added: "100%.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+attachment/5530721/+files/100%25.png -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
This is screenshot of my screen in 200% scale. ** Attachment added: "200%.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+attachment/5530720/+files/200%25.png -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1945992/+attachment/5530715/+files/monitors.xml.txt -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1945992/+attachment/5530714/+files/ShellJournal.txt -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1945992/+attachment/5530713/+files/ProcCpuinfoMinimal.txt -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1945992/+attachment/5530712/+files/GsettingsChanges.txt -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
apport information ** Tags added: apport-collected ** Description changed: I use computer in 200% screen scale. In this scale onscreen keyboard is to big so it is useless because there are invisible space, Alt and Ctrl keys. When the screen is in 100% scale keyboard is in proper size. Moreover there is no possibility to use diacritical marks using onscreen keyboard. Diacritical marks are displayed well but when pressed there is no effect. I tried to check it with different kernels but either on 5.4.0-42 or on 5.11.0-37 the issue occurs. Device: ThinkPad X1 carbon 3 gen. System: Ubuntu 20.04.3 gnome-shell x11 window. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-26 (8 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 + RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 + Tags: focal + Uname: Linux 5.11.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1945992/+attachment/5530711/+files/Dependencies.txt -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946099] [NEW] Stuck on the Ubuntu Single Sign-On Account | Connecting....
Public bug reported: After making a fresh Ubuntu installation it showed me the windows to connect the online cloud accounts, as soon as I clicked on Ubuntu single sign on it pop up the small sized windows to enter the credentials and when I entered the mail Id and password and clicked on connect. After this step it keeps connecting forever and it not even gets connected and neither it gets cancelled by clicking the cancel button.. I tried installing Ubuntu several time the problem still exist and I haven't found any solution for that yet. Hope it gets solved soon. Thanks. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1946099 Title: Stuck on the Ubuntu Single Sign-On Account | Connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1946099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
I can't undestand why this bug still unatended. Certificates and signing is a common practice for today. This bug affects any application who searchs for certificates on operating system storage. Install the same certificate many times in multiple applications increase probabilities for vulnerabilities impacts and private key leaks. It impacts in user experience too, and make hard to handle digital identities in Ubuntu for personal and SOHO users. Finally, it impacts Ubuntu image. less deb Please, considere to change priority for this bug. ** Attachment added: "Import disabled" https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880/+attachment/5530692/+files/Captura%20de%20pantalla%20de%202021-10-05%2013-20-04.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946049] Re: Caps LED ON but caps lock is disabled after logout
@Daniel, I'm not quite sure it's related to gnome-shell. I just shared what I found here and could be solved by gnome-shell. If upstream things there is the other appropriate place to fix then I can create the other thread on that project. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4667 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4667 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4667 -- 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/1946049 Title: Caps LED ON but caps lock is disabled after logout To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11.
** Summary changed: - [nvidia] gdm3 do not connect to the right session on 21.10 beta + GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11. ** Description changed: - I've updated to 21.10 beta to test wayland for nvidia successfully. - - Even when the dot is for "ubuntu with wayland" choice, gdm3 launch X11 - session - - I have to select "ubuntu with wayland" to have the wayland session + GDM3 does not correctly memorize the Wayland choice for NVIDIA cards + (driver 470) and randomly launches X11. The user must always select + Wayland before logging if he wants to be sure to have a Wayland session. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- 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/1945750 Title: GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946082] Re: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()
I'm not sure that's the right bug ID. Can you please tell us the contents of /var/lib/whoopsie/whoopsie-id on this machine? Also if you are experiencing gnome-shell bugs of any sort then it's a good idea to disable all non-Ubuntu extensions in the 'Extensions' app and then log in again. Because extensions cause so many bugs, that's always the first thing to try. ** Information type changed from Public to Private ** This bug is no longer a duplicate of bug 1942121 gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group() ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1946082 Title: gnome-shell crashed with SIGSEGV in __pthread_kill_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
the symptoms are multiple and I also had yours. About the title, I'd say something like that : GDM3 does not correctly memorize the Wayland choice for NVIDIA cards (driver 470) and randomly launches X11. The user must always select Wayland before logging if he wants to be sure to have a Wayland session -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946082] Re: gnome-shell crashed with SIGSEGV in __pthread_kill_internal()
*** This bug is a duplicate of bug 1942121 *** https://bugs.launchpad.net/bugs/1942121 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1942121, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1946082/+attachment/5530662/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530664/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530668/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530669/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530670/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530673/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1946082/+attachment/5530674/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1942121 gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1946082 Title: gnome-shell crashed with SIGSEGV in __pthread_kill_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
That's why I suggested the steps in comment #15 -- to remove all ambiguity from multiple logins. I've just retested Nvidia myself and did notice Wayland is never the default, and that does change the session names too, surprisingly. Is that the main issue this bug should be about? Can you summarize the problem in one or two sentences because it would seem at least part of the original Bug Description above is no longer correct. -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
The second login after logout is the one I explicitly select (knowing that it was already the default). To be sure to have a wayland session I have to select it in the list whatever the default selection which is misleading and even sometimes absent (no point) -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946078] [NEW] package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le
Public bug reported: Bonjour,je sais que ma version est beaucoup trop ancienne,j'ustement a chaque fois que j'utilise la ligne de commande je ne peux rien faire a chaque fois le ( package lib tracker-sparql) m'en empéche, j'aimerai comprendre ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Tue Oct 5 10:32:41 2021 DpkgHistoryLog: Start-Date: 2021-10-05 10:32:33 Commandline: apt install grub Requested-By: thomas (1000) Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 (0.97-29ubuntu68) Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 (2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7) ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2018-09-14 (1116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: tracker Title: package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Description changed: Bonjour,je sais que ma version est beaucoup trop ancienne,j'ustement a chaque fois que j'utilise la ligne de commande je ne peux rien faire a chaque fois le ( package lib tracker-sparql) m'en empéche, j'aimerai comprendre ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Tue Oct 5 10:32:41 2021 DpkgHistoryLog: - Start-Date: 2021-10-05 10:32:33 - Commandline: apt install grub - Requested-By: thomas (1000) - Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 (0.97-29ubuntu68) - Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 (2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7) + Start-Date: 2021-10-05 10:32:33 + Commandline: apt install grub + Requested-By: thomas (1000) + Install: libc6-i386:amd64 (2.23-0ubuntu11.3, automatic), grub:amd64 (0.97-29ubuntu68) + Remove: grub2-common:amd64 (2.02~beta2-36ubuntu3.32), grub-pc:amd64 (2.02~beta2-36ubuntu3.32), grub-gfxpayload-lists:amd64 (0.7) ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2018-09-14 (1116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: - dpkg 1.18.4ubuntu1.7 - apt 1.2.35 + dpkg 1.18.4ubuntu1.7 + apt 1.2.35 SourcePackage: tracker Title: package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1946078 Title: package libtracker-sparql-1.0-0:amd64 1.6.2-0ubuntu1.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1946078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
That log seems to end with Gnome Shell using Wayland. It is gnome-shell process ID 7906. Is that not what you expected? -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
Here is what I got this morning as describe before. (last session I explicitly selected yesterday was Ubuntu for Wayland) ** Attachment added: "journal1.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+attachment/5530645/+files/journal1.txt -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
Only tracking in https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 now, which only affects focal and later. ** Description changed: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 - https://errors.ubuntu.com/problem/73a2092e4c2d306d8a8e329a29a0f6ffd9a2dfeb --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: - https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Tags added: hirsute impish ** Tags removed: bionic -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886405] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_unload_stylesheet:ffi_call_unix64:ffi_call_int
No crashes since 3.36 so consider it fixed. ** This bug is no longer a duplicate of bug 1702151 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1886405 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_unload_stylesheet:ffi_call_unix64:ffi_call_int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886405/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759167] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call
No crashes since 3.36 so consider it fixed. Although bug 1702151 is still open. ** This bug is no longer a duplicate of bug 1702151 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1759167 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
If the problem is that you get a session different to what you expected then please: 1. Reboot. 2. Log in. 3. If the session type is not what you expected then run: journalctl -b0 > wrongsession.txt and attach the resulting text file here. 4. If the session type is what you expected then goto 1. ** Changed in: gdm3 (Ubuntu) Status: Invalid => Incomplete -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
I didn't want to log with Xorg as this last days I was logging without checking anything to wayland. I'm playing with Schrodinger Cat Again, this morning I logged with Xorg when I checked Ubuntu with Wayland yesterday. I left the session and saw that "Ubuntu with Wayland" was checked ( !!!???) I checked it again and now I'm with wayland. -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945750] Re: [nvidia] gdm3 do not connect to the right session on 21.10 beta
I didn't want to log with Xorg as this last days I was logging without checking anything to wayland. I'm playing with Schrodinger Cat again, this morning I logged with Xorg when I checked Ubuntu with Wayland yesterday. -- 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/1945750 Title: [nvidia] gdm3 do not connect to the right session on 21.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727716] Re: 17.10 sticky keys doesn t work
Fixed in 3.28 onward ** Bug watch added: bugzilla.gnome.org/ #788564 https://bugzilla.gnome.org/show_bug.cgi?id=788564 ** Changed in: gnome-shell Importance: Medium => Unknown ** Changed in: gnome-shell Status: Fix Released => Unknown ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #788564 => bugzilla.gnome.org/ #788564 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- 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/1727716 Title: 17.10 sticky keys doesn t work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Triaged -- 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/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]
https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36 https://launchpadlibrarian.net/562041828/gnome- shell_40.5-1ubuntu2_source.changes ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() fr
https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36 https://launchpadlibrarian.net/562041828/gnome- shell_40.5-1ubuntu2_source.changes ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942121] Re: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group()
https://salsa.debian.org/gnome-team/gnome-shell/-/commit/6e18ad3e36 https://launchpadlibrarian.net/562041828/gnome- shell_40.5-1ubuntu2_source.changes ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1942121 Title: gnome-shell crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from st_focus_manager_remove_group() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
