[Bug 1846674] [NEW] GIMP closed unexpectedly.
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--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-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --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 --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)
using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.60.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 12375 - Thread 12375 #
[New LWP 12377]
[New LWP 12378]
[New LWP 12379]
[New LWP 12380]
[New LWP 12381]
[New LWP 12382]
[New LWP 12383]
[New LWP 12384]
[New LWP 12385]
[New LWP 12413]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffefe31a350, fd=43) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7fb80771be00 (LWP 12375) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffefe31a350, fd=43) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7fb806642700 (LWP 12377) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7fb805e41700 (LWP 12378) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7fb805640700 (LWP 12379) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7fb7ff1f9700 (LWP 12380) "gmain" 0x7fb809405729 in
__GI___poll (fds=0x559856b016b0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7fb7fe276700 (LWP 12381) "gdbus" 0x7fb809405729 in
__GI___poll (fds=0x559856b1a1f0, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7fb7e42bd700 (LWP 12382) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7fb7e3abc700 (LWP 12383) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7fb7db2bb700 (LWP 12384) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
10 Thread 0x7fb7e32bb700 (LWP 12385) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
11 Thread 0x7fb7e2aba700 (LWP 12413) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 11 (Thread 0x7fb7e2aba700 (LWP 12413)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7fb8096ef93f in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fb809b96799 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7fb8096cd87d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7fb8094ea182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140427758642944,
1536959686940628873, 140733163083998, 140733163083999, 140733163084144,
140427758639360, -1568477637432502391, -1575008434549614711}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#5 0x7fb809411b1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 10 (Thread 0x7fb7e32bb700 (LWP 12385)):
#0 syscall () at
[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed
** Changed in: gnome-shell Status: Unknown => 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844354] Re: Starting indicator-multiload (with peculiar config) crashes gnome-shell
*** This bug is a duplicate of bug 1787512 *** https://bugs.launchpad.net/bugs/1787512 ** This bug has been marked a duplicate of bug 1787512 gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_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/1844354 Title: Starting indicator-multiload (with peculiar config) crashes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1743 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1743 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1743 Importance: Unknown Status: Unknown ** Tags removed: artful kylin-17.10 ** Tags added: disco -- 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846477] Re: Dragging icons in launcher is slow until shell restarted
It looks like this might be related to the bubble menu pointer lingering. I can't seem to reproduce it yet. Any hints on when/how it starts happening? ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (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/1846477 Title: Dragging icons in launcher is slow until shell restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846503] Re: Installing just one extension makes Ubuntu Eoan to fail
Unfortunately extensions have free access to everything in the shell and so can easily break any part of the shell. Why this problem only affects Ubuntu is likely related to Ubuntu- specific changes. That does not suggest those Ubuntu changes are faulty, only different to the other distros. Since the extension 'desktop-icons-ng-ding' is not part of Ubuntu we are unable to track bugs related to it here. ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Package changed: gnome-shell (Ubuntu) => 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/1846503 Title: Installing just one extension makes Ubuntu Eoan to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1846503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846612] Re: Unable to launch Caja file manager on GNOME Shell
It sounds like Caja is trying to fulfill a role that some other component is already registered for. This would not be a bug in gnome-shell. You would need to find out what other package/component is conflicting and find a way to disable or uninstall it. ** No longer affects: gnome-shell (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/1846612 Title: Unable to launch Caja file manager on GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1846612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846252] Re: gnome-shell segfault
It sounds like you have a manually installed copy of python3-urllib3 version 1.25.3 somewhere on the machine. The official Ubuntu versions are older than that... https://launchpad.net/ubuntu/+source/python-urllib3 -- 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/1846252 Title: gnome-shell segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Eoan) ** No longer affects: mutter -- 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1841718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen
** No longer affects: gnome-shell (Ubuntu) -- 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/1834967 Title: Activities overview doesn't shrink some windows adequately and they are partially off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1834967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
** Changed in: mutter (Ubuntu Bionic) Status: Incomplete => Confirmed -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
** Changed in: mutter (Ubuntu Bionic) Status: Confirmed => New ** Changed in: mutter (Ubuntu Bionic) Status: New => Incomplete -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846612] [NEW] Unable to launch Caja file manager on GNOME Shell
Public bug reported: Steps to reproduce: 1. Install Ubuntu 19.04 2. Install Caja with `sudo apt install caja` 3. Try to start Caja with `caja` disco@disco:~$ caja (caja:5226): Gtk-WARNING **: 00:03:15.323: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client disco@disco:~$ caja --no-desktop (caja:5262): Gtk-WARNING **: 00:04:07.741: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client disco@disco:~$ caja --no-desktop --browser (caja:5270): Gtk-WARNING **: 00:04:12.536: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client disco@disco:~$ killall caja caja: no process found Expected results: * Caja started, its window is shown Actual results: * Caja is not started, its window is not shown ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 23:58:17 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: caja (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Steps to reproduce: 1. Install Ubuntu 19.04 2. Install Caja with `sudo apt install caja` 3. Try to start Caja with `caja` + + disco@disco:~$ caja + + (caja:5226): Gtk-WARNING **: 00:03:15.323: Failed to register client: + GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to + register client + + disco@disco:~$ caja --no-desktop + + (caja:5262): Gtk-WARNING **: 00:04:07.741: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client + disco@disco:~$ caja --no-desktop --browser + + (caja:5270): Gtk-WARNING **: 00:04:12.536: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client + disco@disco:~$ killall caja + caja: no process found + Expected results: * Caja started, its window is shown Actual results: * Caja is not started, its window is not shown ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 23:58:17 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: caja (Ubuntu) Importance: Undecided Status: 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/1846612 Title: Unable to launch Caja file manager on GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1846612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846612] Re: Unable to launch Caja file manager on GNOME Shell
Caja starts only with ``` caja --no-desktop computer: caja --no-desktop network: caja --no-desktop ~ ``` As for me - this is very strange and unpredictable behavior. -- 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/1846612 Title: Unable to launch Caja file manager on GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1846612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846554] [NEW] 'Files' icon should not be listed twice in the Cinnamon start menu
Public bug reported: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1846554 Title: 'Files' icon should not be listed twice in the Cinnamon start menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846541] Re: sigsegv in gtk_widget_get_scale_factor
Details from address sanitizer: Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer:DEADLYSIGNAL Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: = Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc 0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==The signal is caused by a READ memory access. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==Hint: address points to the zero page. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #0 0x7f58b1ab7c7c in g_slice_alloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #1 0x7f58b1abc687 in g_string_sized_new (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x74687) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #2 0x7f58b1a9baef (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x53aef) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #3 0x7f58b1a9e01a in g_markup_parse_context_parse (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5601a) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #4 0x7f58b22f1bdd (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x13abdd) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #5 0x7f58b22ebd50 in gtk_builder_add_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x134d50) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #6 0x7f58b22ef2eb in gtk_builder_new_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x1382eb) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #7 0x7f58b22d5c9f (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x11ec9f) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #8 0x7f58b1b87de2 in g_cclosure_marshal_VOID__OBJECTv (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x17de2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #9 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #10 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #11 0x7f58b1ba19b2 in g_signal_emit (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x319b2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #12 0x7f58b2565e57 in gtk_window_set_application (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3aee57) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #13 0x7f58b1b8a710 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1a710) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #14 0x7f58b1b8c277 in g_object_new_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c277) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #15 0x7f58b1b8c5cc in g_object_new (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c5cc) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #16 0x56047418a910 in gcal_application_activate ../src/gui/gcal-application.c:385 Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #17 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #18 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #19 0x7f58b1ba1fa8 in g_signal_emit_by_name (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x31fa8) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #20 0x7f58b1cb0bbc (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xe1bbc) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #21 0x7f58b1cda053 (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0x10b053) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #22 0x7f58b1a9972d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5172d) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #23 0x7f58b1a99adf (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51adf) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #24 0x7f58b1a99b82 in g_main_context_iteration (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51b82) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #25 0x7f58b1caea64 in g_application_run (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xdfa64) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #26 0x56047418881f in main ../src/main.c:40 Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #27 0x7f58b15aa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #28 0x56047418460d in _start (/usr/bin/gnome-calendar+0x5360d) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer can not provide additional info. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: SUMMARY: AddressSanitizer: SEGV (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) in g_slice_alloc Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ABORTING -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is
[Bug 1846541] Re: sigsegv in gtk_widget_get_scale_factor
AddressSanitizer:DEADLYSIGNAL = ==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc 0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0) ==11918==The signal is caused by a READ memory access. ==11918==Hint: address points to the zero page. #0 0x7f58b1ab7c7c in g_slice_alloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) #1 0x7f58b1abc687 in g_string_sized_new (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x74687) #2 0x7f58b1a9baef (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x53aef) #3 0x7f58b1a9e01a in g_markup_parse_context_parse (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5601a) #4 0x7f58b22f1bdd (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x13abdd) #5 0x7f58b22ebd50 in gtk_builder_add_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x134d50) #6 0x7f58b22ef2eb in gtk_builder_new_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x1382eb) #7 0x7f58b22d5c9f (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x11ec9f) #8 0x7f58b1b87de2 in g_cclosure_marshal_VOID__OBJECTv (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x17de2) #9 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) #10 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) #11 0x7f58b1ba19b2 in g_signal_emit (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x319b2) #12 0x7f58b2565e57 in gtk_window_set_application (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3aee57) #13 0x7f58b1b8a710 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1a710) #14 0x7f58b1b8c277 in g_object_new_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c277) #15 0x7f58b1b8c5cc in g_object_new (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c5cc) #16 0x56047418a910 in gcal_application_activate ../src/gui/gcal-application.c:385 #17 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) #18 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) #19 0x7f58b1ba1fa8 in g_signal_emit_by_name (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x31fa8) #20 0x7f58b1cb0bbc (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xe1bbc) #21 0x7f58b1cda053 (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0x10b053) #22 0x7f58b1a9972d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5172d) #23 0x7f58b1a99adf (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51adf) #24 0x7f58b1a99b82 in g_main_context_iteration (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51b82) #25 0x7f58b1caea64 in g_application_run (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xdfa64) #26 0x56047418881f in main ../src/main.c:40 #27 0x7f58b15aa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) #28 0x56047418460d in _start (/usr/bin/gnome-calendar+0x5360d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) in g_slice_alloc ==11918==ABORTING -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1846541 Title: sigsegv in gtk_widget_get_scale_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846499] Re: e2scrub_all.service is a disabled or a static unit not running, not starting it.
I'm going to start tagging by number instead of codenames. Code-names are stupid. ** Tags removed: eel eely ** Tags added: 19.10 eoan -- 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/1846499 Title: e2scrub_all.service is a disabled or a static unit not running, not starting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1846499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846541] [NEW] sigsegv in gtk_widget_get_scale_factor
Public bug reported: Occasionally when launching the calendar from the overview, it segfaults at startup. This does not seem to happen when launched from the terminal. Logs from journald: Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I'm on Debian Buster, seeing the same behaviour (i.e. long timeout before being shown the login screen in GDM3). Before the upgrade from Stretch all worked as expected. Uninstalling fprintd and libpam-fprintd solves the issue. But I like to have the fingerprint reader working ;-) This is on a Lenovo T430 laptop, fingerprint reader ID 147e:2020 Upek TouchChip Fingerprint Coprocessor. So, I now downgraded both of those packages to version 0.8.0-2, and all works fine. Note, I did not change the installed version of libfprint0, currently this is 0.8.2-3. Installed version of systemd is 241-7~deb10u1. -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846503] Re: Installing just one extension makes Ubuntu Eoan to fail
** Description changed: You can find the information about the bug here. https://discourse.ubuntu.com/t/installing-just-one-extension-makes- ubuntu-eoan-to-fail/12816 + + How to reproduce? + Install this extension from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ in Ubuntu 19.10 development release. + + Then, install the same in Fedora 30, or Arch with Gnome. Gnome shell + works in those distros, or any other, but fails in Ubuntu 19.10. ** Description changed: You can find the information about the bug here. https://discourse.ubuntu.com/t/installing-just-one-extension-makes- ubuntu-eoan-to-fail/12816 How to reproduce? Install this extension from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ in Ubuntu 19.10 development release. Then, install the same in Fedora 30, or Arch with Gnome. Gnome shell - works in those distros, or any other, but fails in Ubuntu 19.10. + works in those distros, or any other, but fails in Ubuntu 19.10. Ubuntu + simply crashes, after clicking on Show Applications button. ** Description changed: You can find the information about the bug here. https://discourse.ubuntu.com/t/installing-just-one-extension-makes- ubuntu-eoan-to-fail/12816 How to reproduce? Install this extension from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ in Ubuntu 19.10 development release. Then, install the same in Fedora 30, or Arch with Gnome. Gnome shell works in those distros, or any other, but fails in Ubuntu 19.10. Ubuntu simply crashes, after clicking on Show Applications button. + + Why this extension over the system one? + Because it allows drag and drop to and fro from the desktop folders and back. -- 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/1846503 Title: Installing just one extension makes Ubuntu Eoan to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846505] [NEW] package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
Public bug reported: Erro ao instalar o pacote. O que fazer? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 3 11:18:46 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2019-06-21 (103 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.26 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1846505 Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1846505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846503] [NEW] Installing just one extension makes Ubuntu Eoan to fail
Public bug reported: You can find the information about the bug here. https://discourse.ubuntu.com/t/installing-just-one-extension-makes- ubuntu-eoan-to-fail/12816 How to reproduce? Install this extension from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ in Ubuntu 19.10 development release. Then, install the same in Fedora 30, or Arch with Gnome. Gnome shell works in those distros, or any other, but fails in Ubuntu 19.10. Ubuntu simply crashes, after clicking on Show Applications button. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/1846503 Title: Installing just one extension makes Ubuntu Eoan to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846499] [NEW] e2scrub_all.service is a disabled or a static unit not running, not starting it.
Public bug reported: Upon attempting to upgrade form Ubuntu 19.04 to Ubuntu 19.10. The installation got stuck with this being the last command line output: "e2scrub_all.service is a disabled or a static unit not running, not starting it." ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: eel eely -- 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/1846499 Title: e2scrub_all.service is a disabled or a static unit not running, not starting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1846499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)
** Changed in: gtk Status: Unknown => Fix Released -- 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/1846188 Title: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1846188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846252] Re: gnome-shell segfault
Well dang again. I happened again this morning when I unlocked the machine, producing a 290meg crash file. Ran this in /var/crash apport-cli _usr_bin_gnome-shell.1000.crash and got this The collected information can be sent to the developers to improve the application. This might take a few minutes. .../usr/lib/python3/dist-packages/requests/__init__.py:80: Re questsDependencyWarning: urllib3 (1.25.3) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) This is a stock 18.04 system, and the python3-urllib3 package is python3-urllib3: Installed: 1.22-1ubuntu0.18.04.1 Candidate: 1.22-1ubuntu0.18.04.1 Slight difference this time though. I switched to console F3 and ran gnome-shell --replace & which always reports back Window Manager Warning: Unsupported Session type But going back to gnome with alt-f2, the usual windows were there, mouse moved, but no mouse-clicks would register. I could switch windows with alt-tab, and once active, could click in there (change tabs in chrome etc). Normally when this happens the terminal sessions are gone. alt-f2 brought up the usual prompt, and "r" restarted gnome-shell and it all seemed to work. Any ideas for pushing that crash file up ? -- 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/1846252 Title: gnome-shell segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen
It's Ubuntu dock bug пн, 30 сент. 2019 г. в 07:35, Daniel van Vugt : > ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) >Status: Incomplete => Confirmed > > ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) >Status: Incomplete => Confirmed > > ** Also affects: gnome-shell (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1834967 > > Title: > Activities overview doesn't shrink some windows adequately and they > are partially off screen > > Status in gnome-shell package in Ubuntu: > Incomplete > Status in gnome-shell-extension-dashtodock package in Ubuntu: > Confirmed > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Confirmed > > Bug description: > Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.32.2-2ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 > Uname: Linux 5.0.0-17-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 1 20:38:43 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2019-07-01 (0 days ago) > InstallationMedia: > > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834967/+subscriptions > -- 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/1834967 Title: Activities overview doesn't shrink some windows adequately and they are partially off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
thanks! ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1240 Importance: Unknown Status: Unknown -- 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/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
Debate? I haven't seen any debate. And no, your proposed "solution" is no solution to the issue. That's a good possible improvement to the search itself, but type-ahead should do select, NOT search for the obvious reasons that have already been pointed out which are not solved by your proposed improvements to the search -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
This bug was fixed in the package xserver-xorg-video-ati - 1:19.0.1-1ubuntu1 --- xserver-xorg-video-ati (1:19.0.1-1ubuntu1) eoan; urgency=medium * dri3-always-flush-glamor.diff: Fix broken tooltips. (LP: #1841718) -- Timo Aaltonen Thu, 03 Oct 2019 11:47:01 +0300 ** Changed in: xserver-xorg-video-ati (Ubuntu Eoan) 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1841718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
This bug was fixed in the package xserver-xorg-video-amdgpu - 19.0.1-1ubuntu1 --- xserver-xorg-video-amdgpu (19.0.1-1ubuntu1) eoan; urgency=medium * dri3-always-flush-glamor.diff: Fix broken tooltips. (LP: #1841718) -- Timo Aaltonen Thu, 03 Oct 2019 11:56:41 +0300 ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1841718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846477] Re: Dragging icons in launcher is slow until shell restarted
First gif was with 3 screens attached (internal panel and two 1080p screens). This gif is with the laptop screen only enabled (laptop removed from dock) ** Attachment added: "Peek 2019-10-03 12-17.gif" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+attachment/5293972/+files/Peek%202019-10-03%2012-17.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846477] Re: Dragging icons in launcher is slow until shell restarted
Finally this gif is after alt-f2, r. ** Attachment added: "Peek 2019-10-03 12-22.gif" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+attachment/5293973/+files/Peek%202019-10-03%2012-22.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846477] [NEW] Dragging icons in launcher is slow until shell restarted
Public bug reported: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Peek 2019-10-03 12-14.gif" https://bugs.launchpad.net/bugs/1846477/+attachment/5293965/+files/Peek%202019-10-03%2012-14.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1534873. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-01-16T07:40:09+00:00 araszka wrote: Description of problem: After update to F27, I am facing issue during login to the system as a user. When a screen is locked (screen with the clock) and I hit any key to show password screen a system completely freeze for 15-20 seconds and after that time I am finally able to type my password. Journalctl shows following error message: Jan 16 08:19:36 araszka-rh gnome-shell[2622]: Failed to connect to Fprint service: Error calling StartServiceByName for net.reactivated.Fprint: Timeout was reached Jan 16 08:19:36 araszka-rh dbus-daemon[981]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms) Version-Release number of selected component (if applicable): libfprint-0.7.0-3.fc27.x86_64 fprintd-0.8.0-1.fc27.x86_64 fprintd-pam-0.8.0-1.fc27.x86_64 How reproducible: always Steps to Reproduce: 1. Lock a screen 2. Log in as a user 3. Actual results: System freeze for 15-20 second in the middle of lock screen and password screen Expected results: No delay Additional info: The bug is reproducible on my Lenovo Thinkpad T450s. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1824855/comments/0 On 2018-01-17T14:38:36+00:00 cfergeau wrote: Hitting that occasionally on my f27. Once it starts triggering, 'fprintd-list $username' triggers it too (it hangs for 25 seconds and dies with a service timeout rather than telling me "no device found). Commenting out ProtectSystem=strict in /usr/lib/systemd/system/fprintd.service makes it go away Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1824855/comments/1 On 2018-01-17T14:58:49+00:00 cfergeau wrote: Looking at fprintd strace/backtrace while it's stuck, I figured out it was trying to run statfs on some stale cifs mountpoints I had on my laptop. After unmounting them (and with an unmodified systemd service file), I no longer get hangs running 'fprintd-list $username' Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1824855/comments/2 On 2018-01-17T14:59:35+00:00 cfergeau wrote: backtrace of fprintd while it's hung #0 0x7fbcdde84287 in statfs64 () from target:/lib64/libc.so.6 #1 0x7fbcdde84309 in statvfs64 () from target:/lib64/libc.so.6 #2 0x5627d4a130f7 in get_mount_flags ( path=path@entry=0x5627d5f54710 "/media/synology/backup", flags=flags@entry=0x7ffc8e276778) at ../src/basic/mount-util.c:314 #3 0x5627d4a1577a in bind_remount_recursive_with_mountinfo (ro=true, proc_self_mountinfo=, blacklist=, prefix=) at ../src/basic/mount-util.c:489 #4 make_read_only (proc_self_mountinfo=, blacklist=, m=) at ../src/core/namespace.c:803 #5 setup_namespace.constprop.59 (root_directory=, root_image=, ns_info=, read_write_paths=, read_only_paths=, inaccessible_paths=, bind_mounts=, n_bind_mounts=, tmp_dir=, var_tmp_dir=, protect_home=, protect_system=, mount_flags=, dissect_image_flags=) at ../src/core/namespace.c:1115 #6 0x5627d4a17654 in apply_mount_namespace.lto_priv.263 ( u=0x5627d610b5b0, command=0x5627d606cc40, context=0x5627d610b9e0, params=, runtime=) at ../src/core/execute.c:2002 #7 0x5627d4a851f4 in exec_child.constprop.47 (unit=0x5627d610b5b0, command=0x5627d606cc40, context=, params=0x7ffc8e277180, runtime=, dcreds=, argv=, socket_fd=, named_iofds=, fds=, n_storage_fds=, n_socket_fds=, files_env=, user_lookup_fd=, exit_status=, error_message=) at ../src/core/execute.c:2626 #8 0x5627d4ab5060 in exec_spawn (unit=, command=0x5627d606cc40, context=0x5627d610b9e0, params=, runtime=0x0, dcreds=0x5627d610bd28, ret=0x7ffc8e277170) at ../src/core/execute.c:2983 #9 0x5627d4a5801f in service_spawn (s=s@entry=0x5627d610b5b0, c=, timeout=, flags=flags@entry=(EXEC_APPLY_PERMISSIONS | EXEC_APPLY_CHROOT | EXEC_APPLY_TTY_STDIN | EXEC_PASS_FDS | EXEC_SET_WATCHDOG), _pid=_pid@entry=0x7ffc8e2772c4) at ../src/core/service.c:1375 #10 0x5627d4a60c6c in service_enter_start (s=s@entry=0x5627d610b5b0) at ../src/core/service.c:1817 #11 0x5627d4a61098 in service_enter_start_pre (s=0x5627d610b5b0) at ../src/core/service.c:1886 #12 service_start.lto_priv.375 (u=0x5627d610b5b0) at ../src/core/service.c:2099 #13
[Bug 1164016] Re: restore type-ahead find
I think a nice way to solve this stupid debate could be to ensure that the files are displayed in a STABLE order - type ahead results from the current folder first - folders first - files in the current folder before the other files... what is MOST annoying with the current feature is that when you have spotted the file you're interested it (or quite often the folder) then - there can be other files/folder with the same name and it is impossible to know which is relevant (it should be the closest, the one from the current folder, etc). It seems to be the last used, so it changes - when you have spotted the folder or file you want to open, the time you move your pointer to open it the files are reorganized as further search has been done, and you open some other random file. How is it possible to maintain such a feature the way it currently works? The search should be done in some order, and this order should not change so rapidly while you're trying to find your result... -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I tested uninstalling fprintd, this indeed works around the problem. -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 577825] Re: Either battery status icon not being shown, or the icon showing "Laptop battery is charged".
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/577825 Title: Either battery status icon not being shown, or the icon showing "Laptop battery is charged". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/577825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845198] Re: GNOME Shell seemingly locked up at login
** Changed in: gnome-shell 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/1845198 Title: GNOME Shell seemingly locked up at login To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
** Changed in: fprintd (Ubuntu) Status: Incomplete => Confirmed -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I experience the same problem on my xps9360 (without fingerprint reader) after a clean install of ubuntu 19.10. I never experienced this problem on 18.04 and the earlier ubuntu versions I ran on this laptop. The delay is ~ 15-20 seconds and there are error messages in the Journactl log: kt 03 11:18:55 paraiko-XPS-13-9360 systemd[1]: NetworkManager-dispatcher.service: Succeeded. okt 03 11:19:07 paraiko-XPS-13-9360 dbus-daemon[851]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms) okt 03 11:19:07 paraiko-XPS-13-9360 gnome-shell[2403]: Failed to connect to Fprint service: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated okt 03 11:19:11 paraiko-XPS-13-9360 gdm-password][21463]: gkr-pam: unlocked login keyring. There is also an intersting discussion on the fedora bugtracker about this problem which might be of interest. -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
I created a bug report on the gnome project… for reference https://gitlab.gnome.org/GNOME/nautilus/issues/1240 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1240 https://gitlab.gnome.org/GNOME/nautilus/issues/1240 -- 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/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
** Bug watch added: Red Hat Bugzilla #1534873 https://bugzilla.redhat.com/show_bug.cgi?id=1534873 ** Also affects: fprintd (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1534873 Importance: Unknown Status: Unknown -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 213053] Re: Totem is 'uninterruptible'
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/213053 Title: Totem is 'uninterruptible' To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/213053/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
I made a short clip of it… the folder it displays in between is not even on the level up, but a completely different previously displayed folder. ** Attachment added: "Screencast from 03.10.2019 11:29:21.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+attachment/5293925/+files/Screencast%20from%2003.10.2019%2011%3A29%3A21.webm -- 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/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
Thank you for your bug report, could you open it upstream as well on https://gitlab.gnome.org/GNOME/nautilus/issues/ ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] [NEW] Disconcerting Folder/Selection flashing when deleting files/folders
Public bug reported: When entering a folder in nautilus and deleting a file permanently "shift+del" the selection jumps and sometimes even the previous folder level is being displayed. This is super confusing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 3 11:06:08 2019 InstallationDate: Installed on 2018-05-02 (518 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages wayland-session -- 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/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832875] Re: On-screen keyboard lacks several French layouts
This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.2 --- gnome-shell (3.28.4-0ubuntu18.04.2) bionic; urgency=medium * d/p/osk-layouts-Fix-French-layout.patch: - osk-layouts: Fix French layout (LP: #1832875) -- Marco Trevisan (Treviño) Thu, 27 Jun 2019 21:07:13 +0100 ** Changed in: gnome-shell (Ubuntu Bionic) 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/1832875 Title: On-screen keyboard lacks several French layouts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1841718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832875] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832875 Title: On-screen keyboard lacks several French layouts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Holy cow, I completely misunderstood the UI. Sorry for bothering!!! ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819193] Re: Document search does not work
** Changed in: gnome-documents (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/1819193 Title: Document search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-documents/+bug/1819193/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Changed in: xserver-xorg-driver-ati Status: Unknown => 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1841718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
> Cursor color: checked, same colors Well, if cursor color is the same as the default color then it is requested to be invisible. What you need for the cursor color is something very different from the defaults (e.g. the two colors swapped). Nitpicking: You shouldn't need to restart gnome-terminal, it should pick up the preference changes immediately. -- 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/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845802] Re: [radeon] Corrupt/skewed gnome-shell panel rendering
** Tags removed: xrandr-scaling -- 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/1845802 Title: [radeon] Corrupt/skewed gnome-shell panel rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845198] Re: GNOME Shell seemingly locked up at login
** Tags added: fixed-in-3.34.1 fixed-upstream -- 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/1845198 Title: GNOME Shell seemingly locked up at login To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795421] Re: [cosmic] sidebar requires scrolling
Is this still a problem? This seems to have been reported against only cosmic so far. ** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => Incomplete ** Changed in: yaru-theme (Ubuntu) Status: New => Incomplete -- 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/1795421 Title: [cosmic] sidebar requires scrolling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
