[Bug 1848125] [NEW] GIMP crashed when exploring dockable tools?
Public bug reported: OS Ubuntu 19.04 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: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 4302 - Thread 4302 # [New LWP 4303] [New LWP 4304] [New LWP 4305] [New LWP 4306] [New LWP 4307] [New LWP 4308] [New LWP 4309] [New LWP 4310] [New LWP 4311] [New LWP 4312] [New LWP 4313] [New LWP 4314] [New LWP 4315] [New LWP 4316] [New LWP 4317] [New LWP 4318] [New LWP 4319] [New LWP 4361] [New LWP 6132] [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=0x7ffd41fefe90, fd=45) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f3579818e00 (LWP 4302) "gimp-2.10" __libc_read (nbytes=256, buf=0x7ffd41fefe90, fd=45) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f357884d700 (LWP 4303) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f357804c700 (LWP 4304) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f357784b700 (LWP 4305) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f357704a700 (LWP 4306) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f3576849700 (LWP 4307) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7f3576048700 (LWP 4308) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f3575847700 (LWP 4309) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f35571f9700 (LWP 4310) "gmain" 0x7f357b502729 in __GI___poll (fds=0x55afc3074d20, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7f35569f8700 (LWP 4311) "gdbus" 0x7f357b502729 in __GI___poll (fds=0x55afc3087fe0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7f3543965700 (LWP 4312) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f3543164700 (LWP 4313) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7f3542963700 (LWP 4314) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7f3542162700 (LWP 4315) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7f3541961700 (LWP 4316) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7f3541160700 (LWP 4317) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7f354095f700 (LWP 4318) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 18 Thread 0x7f353bfff700 (LWP 4319) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 19 Thread 0x7f3539682700 (LWP 4361) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 20 Thread 0x7f353adae700 (LWP 6132)
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1848119 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #1791 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1791 -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview
There's nothing in /var/crash related to this. I guess I associated stack traces with crashes, perhaps error is the appropriate description here. I've edited the title and description to reflect this. ** Summary changed: - gnome-shell infinite crash loop when closing app in activities overview + gnome-shell infinite error loop when closing app in activities overview ** Description changed: Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 How to reproduce: 1) Open terminal and watch journalct -f 2) Open Files 3) Close Files in the activities overview - 4) gnome-shell loop crashes non stop. - + 4) gnome-shell errors in journal non stop. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1791 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1791 -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview
I also reported this upstream https://gitlab.gnome.org/GNOME/gnome- shell/issues/1791 -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I wonder if it's a coincidence that both bug reports for this involve the Nvidia driver... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848093] Re: Login loop with gdm3 and 19.10 beta
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 Nevermind. I found bug 1845801, which this is a duplicate of. ** This bug has been marked a duplicate of bug 1845801 Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. -- 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/1848093 Title: Login loop with gdm3 and 19.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848093] Re: Login loop with gdm3 and 19.10 beta
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 Please run this command to send us more information about the machine: apport-collect 1848093 ** Changed in: gdm3 (Ubuntu) Status: New => 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/1848093 Title: Login loop with gdm3 and 19.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Also affects: gdm3 (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/1845801 Title: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] Re: gnome-shell infinite crash loop when closing app in activities overview
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: eoan ** 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/1848119 Title: gnome-shell infinite crash loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] Re: gnome-shell infinite crash loop when closing app in activities overview
Note also that "Stack trace for context" followed by JavaScript is more often not a crash, just an error. But it might be a crash... -- 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/1848119 Title: gnome-shell infinite crash loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] [NEW] gnome-shell infinite crash loop when closing app in activities overview
Public bug reported: Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 How to reproduce: 1) Open terminal and watch journalct -f 2) Open Files 3) Close Files in the activities overview 4) gnome-shell loop crashes non stop. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) ** 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/1848119 Title: gnome-shell infinite crash loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847112] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() from reset_current_config() from on_screen_changed() from g_closure_invoke() from signal_emit_unlock
** Summary changed: - /usr/bin/gnome-control-center:11:cc_display_config_set_minimum_size:reset_current_config:on_screen_changed:g_closure_invoke:signal_emit_unlocked_R + gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() from reset_current_config() from on_screen_changed() from g_closure_invoke() from signal_emit_unlocked_R() -- 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/1847112 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() from reset_current_config() from on_screen_changed() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847103] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() from complete_in_idle
** Summary changed: - /usr/bin/gnome-control-center:11:g_type_check_instance_cast:BG_RECENT_SOURCE:enumerate_children_finished_cb:g_task_return_now:complete_in_idle_cb + gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() from complete_in_idle_cb() ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1847103 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() from complete_in_idle_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1847103/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847103] Re: /usr/bin/gnome-control-center:11:g_type_check_instance_cast:BG_RECENT_SOURCE:enumerate_children_finished_cb:g_task_return_now:complete_in_idle_cb
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1847103 Title: /usr/bin/gnome-control- center:11:g_type_check_instance_cast:BG_RECENT_SOURCE:enumerate_children_finished_cb:g_task_return_now:complete_in_idle_cb To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1847103/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848093] Re: Login loop with gdm3 and 19.10 beta
I was thinking of bug 1844944 but it sounds like you would have that fix already. ** 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/1848093 Title: Login loop with gdm3 and 19.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848093] Re: Login loop with gdm3 and 19.10 beta
Was there a user already logged in? If so then this sounds like a bug that has already been fixed in updates (after beta was released). ** Tags added: eoan ** Changed in: gdm3 (Ubuntu) Status: New => 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/1848093 Title: Login loop with gdm3 and 19.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
** Also 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
** Tags added: performance -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847960] Re: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1532508, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1532508 Screen contents revealed briefly on resume, before even unlocking -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1847960 Title: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1847960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings
** Tags added: eoan -- 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/1847633 Title: 19.10 wifi networks menu doesn't respect natural scrolling settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
thebravoman, Please be sure to uninstall that extension. Just turning extensions off is not enough to prevent them from interfering with the shell :( -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848093] [NEW] Login loop with gdm3 and 19.10 beta
Public bug reported: The user is unable to login from the login screen. The password is accepted but the password prompt is displayed again. Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Note that the login screen appears even though I had specified auto login. Perhaps this one line is important: Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for username (null) I am using an NVIDIA RTX 2080Ti with the bundled drivers. When used via ssh, the following brings the system to a working desktop: sudo service gdm restart However, when this was used from a terminal from ctrl-alt-F3 the system locked completely and was unresponsive over ssh. /var/log/syslog is below: Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated username Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: PAM conversation returning 0: Success Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHENTICATED Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated username Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: username is 'ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: old-username='ted' new-username='ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change state to AUTHORIZED Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: determining if authenticated user (password required:0) is authorized to session Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHORIZED Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change state to ACCREDITED Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'LOGNAME=ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'USER=ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'USERNAME=ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'HOME=/home/ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'PWD=/home/ted' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'SHELL=/usr/bin/zsh' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment variable: 'PATH=/usr/local/bin:/usr/bin:/bin:/usr/games' Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state ACCREDITED Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: pid 1802 reauthenticated user 124 with service 'gdm-password' Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Stopping job pid:3419 Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: sending signal 15 to process 3419 Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Waiting on process 3419 Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: process (pid:3419) done (status:0) Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: SessionWorkerJob died Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: client cancelled reauthentication request Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations Oct 14 14:41:24 carbon gdm3: GdmSession: Emitting 'reauthenticated' signal Oct 14 14:41:24 carbon gdm3: GdmSession: type (null), program? no, seat seat0 Oct 14 14:41:24 carbon gdm3: GdmManager: Considering session 1 on seat seat0 belonging to user ted Oct 14 14:41:24 carbon gdm3: GdmManager: yes, found session 1 Oct 14 14:41:24 carbon gdm3: Unlocking session 1 Oct 14 14:41:24 carbon gdm3: GdmManager: trying to open new session Oct 14 14:41:24 carbon gdm3: Finding a graphical session for user 124 Oct 14 14:41:24 carbon gdm3: Considering session 'c1' Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for username (null) Oct 14 14:41:24 carbon gdm3: GdmDBusServer: new connection 0x5631e08edec0 Oct 14 14:41:24 carbon gdm3: GdmSession: Handling new connection from outside Oct 14 14:41:24 carbon gdm3: GdmManager: client with pid 1802 connected Oct 14 14:41:24 carbon gdm3: GdmDisplay: Got timed login details for display: 0 Oct 14 14:41:31 carbon xdg-desktop-por[1623]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Oct 14 14:41:33 carbon gdm-autologin]: GdmSession: external connection closed Oct 14 14:41:33 carbon gdm-autologin]: GdmSessionWorker: client disconnected from reauthentication server Oct 14 14:41:33 carbon gdm3: GdmSession: external connection closed Oct 14 14:41:33 carbon gdm-autologin]: GdmSession: Disposing
[Bug 1848086] [NEW] Keyboard shortcuts to launch apps sometimes launch twice
Public bug reported: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1848086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847960] Re: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1847960 Title: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1847960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
yeah ok just checked, that totally fixes it, have asked the systemd maintainer if that patch can be included in the next update ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
To expand on what Daniel said: 1. Start with one extension and remove it from Gnome Tweak Tools or the GNOME Shell Extensions web site: https://extensions.gnome.org/local/ 2. Restart GNOME Shell with ALT+F2, type in r then hit enter 3. If don't experience this bug for a few hours or days (days would be preferred) let us know in this bug report and which extension you completely removed. Perhaps we can narrow down on the problematic extension this way, if it is actually an extension. 4. If you still hit this bug a few minutes or hours later, logout from your session completely and try use the desktop for a few days. If you still have this problem try the next extension and repeat 1-3. If you have no more extensions installed and the error occurs, please consider filing a new bug report as soon as possible with ubuntu-bug gnome-shell and link the new bug report as a comment in this bug report. I hope the steps above are useful. Thanks -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826040] Re: examples.desktop file is not executable and only opens into default text editor(gedit)
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1826040 Title: examples.desktop file is not executable and only opens into default text editor(gedit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785456] Re: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.1 failed to install/upgrade: package libedataserverui-1.2-1:amd64 is not ready for configuration cannot configure (current status
Thank you for your bug report, it looks like a local corruption/download error rather than a package bug though ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1785456 Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.1 failed to install/upgrade: package libedataserverui-1.2-1:amd64 is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1785456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844100] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: evolution-data-server (Ubuntu) Importance: Medium => Low ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1844100 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1844100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
s/D-Bus session/logind session/ -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847104] Re: /usr/bin/gnome-calendar:11:gdk_rgba_to_string:process_sources:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
The issue is fixed in 3.34.2 ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Fix Released -- 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/1847104 Title: /usr/bin/gnome- calendar:11:gdk_rgba_to_string:process_sources:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1847104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
I haven't tested this, but since seb128 pasted the relevant messages in IRC. I bet you that it's because polkit isn't considering the D-Bus session of the greeter to be 'active', because it's not finding it. If someone would like to test build a systemd with this commit included: https://github.com/systemd/systemd/commit/a2dcb1d78737d3daa301ee63fbdd02837acb71a8 I suspect the problem would be fixed. ** Also affects: systemd (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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@Seb128, Sorry to bother you again, but I've noticed some (at least for me) unexpected fallout from this bug. Using Xubuntu Eoan with 20.4-2ubuntu2 from proposed. When connecting to my Wi-Fi network (which is set to WPA2/WPA3 mixed mode) using NM-Applet (the GUI not NMTUI) it will show the authn dialog but the Wi-Fi password field is missing. I've attached a screenshot depicting the Issue. If I'm not mistaken, the following commit fixes this issue: https://gitlab.gnome.org/GNOME/network-manager-applet/commit/1272e7fa2e976ac5db6352302962aba439ce6dd7 ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+attachment/5297059/+files/NM-Applet-fail.png ** Also affects: network-manager-applet (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/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Oct 14 15:46:09 ubuntu gnome-shell[925]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: c1 Oct 14 15:46:10 ubuntu gnome-session[916]: gnome-session-binary[916]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive authentication required. Oct 14 15:46:10 ubuntu gnome-session-binary[916]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive authentication required. Oct 14 15:46:10 ubuntu gnome-session-binary[916]: Entering running state Oct 14 15:46:10 ubuntu gnome-shell[925]: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848011] Re: Samba share connection only works once
Thanks for the fast response. > Could you get a 'journalctl -b 0' log after getting the issue? When the connection fails these lines show up: Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. > When you say 'disconnect' do you mean you software unmount it? or turn off the server/disconect the cable? Here I mean clicking the unmount button for the network connection in nautilus. > do you get the same issue using gio mount? I hope I did it right (anonymized paths / user name): gio mount smb://username@server.intern/share mountpoint After a while it asks me for "Password required for share". Then I have to enter domain and password. After another while it asks the same question again. Same journal output as above occurs: Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. -- 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/1848011 Title: Samba share connection only works once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Yes, confirmed the Activites view is slow to load also. -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
** Tags added: rls-ee-incoming -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Discussed a bit at the gnome-shell hackfest, it's probably because the overview 'download sreenshots' of all the open windows for the overview (which also gets open when you open the app grid, as you can see if you press 'esc' from that view). Upstream has a branch to remove that 'download' step but it's next- cycle-material They suggested we could probably do optimize to not load the overview in app-grid-mode if we were after a solution for the current stable serie -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Thanks, seems it's not only the applications view but it's also slow to open the activities? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => 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/1848009 Title: Delay launching application launcher gets longer the more apps are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848011] Re: Samba share connection only works once
Thank you for your bug report. - Could you get a 'journalctl -b 0' log after getting the issue? - When you say 'disconnect' do you mean you software unmount it? or turn off the server/disconect the cable? - do you get the same issue using gio mount? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1848011 Title: Samba share connection only works once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792085] Re: MTP not working/very slow on Bionic
Same problem with Samsung Galaxy S6 on Ubuntu 19.04 and 19.10. When I try to connect/open in Nautilus, I get the error "Unhandled error message: The name 1.153 was not provided by any .service files". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848009] [NEW] Delay launching application launcher gets longer the more apps are open
Public bug reported: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. + On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. + + Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848009 Title: Delay launching application launcher gets longer the more apps are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848011] [NEW] Samba share connection only works once
Public bug reported: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description:Ubuntu 19.04 Release:19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- 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/1848011 Title: Samba share connection only works once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848011] Re: Samba share connection only works once
If I can provide any further info to solve this issue please let me know. -- 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/1848011 Title: Samba share connection only works once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Yes. Versions GNOME Shell 3.32.2 Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco Only extension in tweaks is Alt-Tab Switcher Popup Delay Removal I have tried to turn it off, but this does not help. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking
That's the command quoted in the log from the bug description? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1822392 Title: gsd-media-keys fails to adjust the screen brightness after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846215] Re: Unable to rename file on desktop
Thank you for your bug report, that should work better with the recent update https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/19.10.2-1 Could you test if that's still an issue for you? ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846215 Title: Unable to rename file on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1846215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings
** Package changed: evince (Ubuntu) => 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/1847633 Title: 19.10 wifi networks menu doesn't respect natural scrolling settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan
Thank you for your bug report. The setting is working fine here, could you remove the synaptic driver, reboot, trigger the issue and attach your 'journalctl -b 0' log to the bug? Can you also install libinput-tools and run 'sudo libinput-list-devices' before doing the change, after again and one more time after closing the settings? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (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/1845898 Title: Unable to set touchpad Edge Scrolling in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
I've built a test package for 18.04 in my PPA if you want to test it: https://launchpad.net/~tj/+archive/ubuntu/bugfixes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting
** Package changed: bolt (Ubuntu) => 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/1844650 Title: No authentication window pops up if thunderbolt device be plugged before booting To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1844650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844650] [NEW] No authentication window pops up if thunderbolt device be plugged before booting
You have been subscribed to a public bug:
[Summary]
In order to access the docking station resource, the system should pop up an
authentication window after the cold boot. But, currently, no authentication
window pops up after the cold boot. The authentication window only pops up
after replugging it during the running state of the system.
[Pre condition]
- the testing thunderbolt device is not authenticated before
- e.g. this is the 1st time you plugging this device.
- e.g. execute `boltctl forget ${device}` to make sure target device not be
authenticated
[Steps to reproduce]
1. keep the machine in the power-off state.
2. Plugin the docking station(TB16/TB18)
3. Boot up the system
4. Check if an authentication window pops up after Ubuntu desktop displayed
[Expected result]
An authentication window pops up after Ubuntu desktop displayed
[Actual result]
No authentication window pops up after the cold boot
[Failure rate]
100%
[Additional information]
this issue can also be reproduced by 19.10 which has bolt 0.8-2 and kernel
5.2.0-15-generic
** Affects: oem-priority
Importance: Critical
Assignee: Alex Tu (alextu)
Status: Confirmed
** Affects: gnome-shell (Ubuntu)
Importance: High
Status: New
** Tags: originate-from-1842279
--
No authentication window pops up if thunderbolt device be plugged before booting
https://bugs.launchpad.net/bugs/1844650
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to gnome-shell in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832869] Update Released
The verification of the Stable Release Update for mutter 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/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage
This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.2 --- mutter (3.28.4-0ubuntu18.04.2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * d/p/screen-Destroy-window-actors-after-windows-while-unmanagi.patch, d/p/screen-Unset-the-active-workspace-and-remove-workspaces-o.patch: - Destroy window actors after windows while unmanaging compositor (LP: #1832869) * d/p/window-Emit-an-error-and-return-when-trying-to-activate-a.patch: - window: Emit an error and return when trying to activate an unmanaged (LP: #1827401) * d/p/stack-Add-a-function-to-get-a-sorted-list-of-focus-candid.patch, d/p/test-runner-Add-assert_focused-command.patch, d/p/test-runner-Add-dispatch-command.patch, d/p/test-runner-Add-sleep-command.patch, d/p/tests-Add-accept_focus-command-to-runner-and-client.patch, d/p/tests-Add-can_take_focus-command-to-runner-and-client.patch, d/p/tests-Verify-focused-window-in-closed-transient-tests.patch, d/p/tests-stacking-Add-tests-with-no-input-and-no-take-focus-.patch, d/p/window-x11-Accept-any-focusable-window-as-fallback-focus.patch, d/p/window-x11-Don-t-double-check-for-unmanaging-windows.patch, d/p/window-x11-Focus-the-default-window-with-delay-while-wait.patch, d/p/window-x11-Use-any-focusable-window-as-fallback-delayed-f.patch, d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch, d/p/workspace-Focus-only-ancestors-that-are-focusable.patch: - Workspace: Take-Input windows focus fixes (LP: #1791574) * debian/libmutter-2-0.symbols: Update with new symbols [ Iain Lane ] * debian/libmutter-2-0.symbols: Add a tilde. These were added in an Ubuntu revision, so they should cause dependencies on the full version - but we add a tilde in case of backports. -- Iain Lane Tue, 09 Jul 2019 17:03:10 +0100 ** Changed in: mutter (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/1791574 Title: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1791574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827401] Re: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full
This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.2 --- mutter (3.28.4-0ubuntu18.04.2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * d/p/screen-Destroy-window-actors-after-windows-while-unmanagi.patch, d/p/screen-Unset-the-active-workspace-and-remove-workspaces-o.patch: - Destroy window actors after windows while unmanaging compositor (LP: #1832869) * d/p/window-Emit-an-error-and-return-when-trying-to-activate-a.patch: - window: Emit an error and return when trying to activate an unmanaged (LP: #1827401) * d/p/stack-Add-a-function-to-get-a-sorted-list-of-focus-candid.patch, d/p/test-runner-Add-assert_focused-command.patch, d/p/test-runner-Add-dispatch-command.patch, d/p/test-runner-Add-sleep-command.patch, d/p/tests-Add-accept_focus-command-to-runner-and-client.patch, d/p/tests-Add-can_take_focus-command-to-runner-and-client.patch, d/p/tests-Verify-focused-window-in-closed-transient-tests.patch, d/p/tests-stacking-Add-tests-with-no-input-and-no-take-focus-.patch, d/p/window-x11-Accept-any-focusable-window-as-fallback-focus.patch, d/p/window-x11-Don-t-double-check-for-unmanaging-windows.patch, d/p/window-x11-Focus-the-default-window-with-delay-while-wait.patch, d/p/window-x11-Use-any-focusable-window-as-fallback-delayed-f.patch, d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch, d/p/workspace-Focus-only-ancestors-that-are-focusable.patch: - Workspace: Take-Input windows focus fixes (LP: #1791574) * debian/libmutter-2-0.symbols: Update with new symbols [ Iain Lane ] * debian/libmutter-2-0.symbols: Add a tilde. These were added in an Ubuntu revision, so they should cause dependencies on the full version - but we add a tilde in case of backports. -- Iain Lane Tue, 09 Jul 2019 17:03:10 +0100 ** Changed in: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827401 Title: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1827401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()
This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.2 --- mutter (3.28.4-0ubuntu18.04.2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * d/p/screen-Destroy-window-actors-after-windows-while-unmanagi.patch, d/p/screen-Unset-the-active-workspace-and-remove-workspaces-o.patch: - Destroy window actors after windows while unmanaging compositor (LP: #1832869) * d/p/window-Emit-an-error-and-return-when-trying-to-activate-a.patch: - window: Emit an error and return when trying to activate an unmanaged (LP: #1827401) * d/p/stack-Add-a-function-to-get-a-sorted-list-of-focus-candid.patch, d/p/test-runner-Add-assert_focused-command.patch, d/p/test-runner-Add-dispatch-command.patch, d/p/test-runner-Add-sleep-command.patch, d/p/tests-Add-accept_focus-command-to-runner-and-client.patch, d/p/tests-Add-can_take_focus-command-to-runner-and-client.patch, d/p/tests-Verify-focused-window-in-closed-transient-tests.patch, d/p/tests-stacking-Add-tests-with-no-input-and-no-take-focus-.patch, d/p/window-x11-Accept-any-focusable-window-as-fallback-focus.patch, d/p/window-x11-Don-t-double-check-for-unmanaging-windows.patch, d/p/window-x11-Focus-the-default-window-with-delay-while-wait.patch, d/p/window-x11-Use-any-focusable-window-as-fallback-delayed-f.patch, d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch, d/p/workspace-Focus-only-ancestors-that-are-focusable.patch: - Workspace: Take-Input windows focus fixes (LP: #1791574) * debian/libmutter-2-0.symbols: Update with new symbols [ Iain Lane ] * debian/libmutter-2-0.symbols: Add a tilde. These were added in an Ubuntu revision, so they should cause dependencies on the full version - but we add a tilde in case of backports. -- Iain Lane Tue, 09 Jul 2019 17:03:10 +0100 ** Changed in: mutter (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/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847893] Re: gnome-shell[2670]: segfault at fffffffffffffcd0 ip 00007f28ce97559b sp 00007ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000]
Thanks, closing then ** Package changed: gnome-menus (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => 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/1847893 Title: gnome-shell[2670]: segfault at fcd0 ip 7f28ce97559b sp 7ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826040] Re: examples.desktop file is not executable and only opens into default text editor(gedit)
Setting has wontfix for nautilus, they remove support to .desktop link type and don't seem interested to add that backb ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1826040 Title: examples.desktop file is not executable and only opens into default text editor(gedit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843512] Re: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display() from meta_stage_is_focused()
This is fixed by gnome-shell (3.34.1-1ubuntu1) eoan; urgency=medium * Merge with Debian. Remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * Refresh patches through gbp-pq gnome-shell (3.34.1-1) unstable; urgency=medium * New upstream release + Allow editing app folder names + Do not notify systemd before initialization is complete + Don't leak NOTIFY_SOCKET environment variable to applications + Fix accidentally skipped animations + Fix box-shadow glitch with prerendered resources + Fix desktop right click menu appearing in the wrong place if a Terminal window is open (LP: #1842910) + Fix extra icons appearing in "Frequent" view animation + Fix fading out desktop icons (Closes: #940612) + Fix "Frequent" view icons disappearing on hover (LP: #1846083) + Fix lock-up on X11 when ibus is already running on startup (LP: #1845198) + Fix screen dimming on idle (LP: #1846941) + Fix screenshots and window animations when scaled + Fix various regressions with dynamic workspaces + Improve performance when enabling/disabling all extensions + Make menu animations more consistent + Skip property transitions while hidden + Support SAE secrets in network agent (LP: #1844422) * control: Require mutter 3.34.1 -- Iain Lane Wed, 09 Oct 2019 12:18:14 +0100 ** 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/1843512 Title: gnome-shell crashed with SIGSEGV in meta_get_stage_for_display() from meta_stage_is_focused() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847974] [NEW] Some apps terminates on Power-Off dialog
Public bug reported: Calling Power-Off dialog from system menu and then pressing cancel button terminates some apps like fbreader and telegram. Tested on Ubuntu 18.04 and 19.10. Steps to reproduce: 1. Install fbreader from standard repository (sudo apt install fbreader) 2. Run fbreader 3. Press Gnome system menu - power button 4. Power-Off dialog appeared - press Cancel button Expected result: fbreader still running. Actual result: fbreader terminated. Same issue with Telegram app (possible other Qt apps?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 11:35:58 2019 DisplayManager: lightdm SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2017-10-24 (719 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic eoan -- 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/1847974 Title: Some apps terminates on Power-Off dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826040] Re: examples.desktop file is not executable and only opens into default text editor(gedit)
Possibly related: https://gitlab.gnome.org/GNOME/nautilus/issues/448 My interpretation of that upstream bug is that .desktop files of type=link are not supported any more. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #448 https://gitlab.gnome.org/GNOME/nautilus/issues/448 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1826040 Title: examples.desktop file is not executable and only opens into default text editor(gedit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen
I feel we've settled on a poor design, but wasn't going to raise the issue until xnox and popey did recently in these bug reports. If a few of us still have concerns then it's a valid discussion. And at the same time "Won't Fix" and "Opinion" are also understandable responses... Caring about the product is important, and if multiple people still feel it is below par then it is reasonable to discuss this still. -- 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/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
Thanks for upstreaming and following up! -- 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/1845703 Title: Deleting starred files leaves behind starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen
I think this should be closed. I'm going to do that. I actually think that Will meant to when he wrote comment #6. The idea is the the title of a maximised window is below the clock, or (for example) centred when you have two windows side by side. That means it has to be not in the centre of the whole screen when the dock is not auto-hidden, and vice-versa. The team discussed this extensively at the time (when we introduced the dock I think), and most recently in Paris sprint and we re-confirmed that this is the behaviour that we thought was desirable. I don't think there's much sense in having this topic permanently open as an energy and time sink. If there *is* a bug here, perhaps it is that we should not produce default wallpapers which look visually centered. ** Changed in: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826040] Re: examples.desktop file is not executable and only opens into default text editor(gedit)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1826040 Title: examples.desktop file is not executable and only opens into default text editor(gedit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/1826040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847893] Re: gnome-shell[2670]: segfault at fffffffffffffcd0 ip 00007f28ce97559b sp 00007ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000]
This may be extension related to "dynamic panel transparency". Feel free to close this now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1847893 Title: gnome-shell[2670]: segfault at fcd0 ip 7f28ce97559b sp 7ffd57519c18 error 5 in libmutter-5.so.0.0.0[7f28ce91b000+f3000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1847893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Please mention which version of Ubuntu/Gnome Shell you have the problem with. Everyone please also ensure you have tried uninstalling (not just disabling) all non-Ubuntu extensions. Since so many bugs are caused by extensions we need to exclude those as a first step. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
One more person, me, confirming the existing of this and how counter productive it is. My daily work with Gnome involves clicking 7-8 times for every time I want to click on something. I've done my clicks for more than two lifetimes. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@seb128 >From a functional point of view, it is working now. I'm able to connect to my AP with WPA3-SAE/WPA3-Personal using 1.20.4-2ubuntu2 from proposed. Although I'm unable to comment on the gnome-shell part of this bug since i'm using XFCE. Thanks for helping out. -- 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/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
