[Bug 1871082] Re: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Fixed with today's 20.10 update (gedit 3.38.0). ** Changed in: gedit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871082] Re: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Fixed upstream (v3.38). https://gitlab.gnome.org/GNOME/gedit/issues/177 https://gitlab.gnome.org/GNOME/gedit/-/issues/188 Meanwhile, before v3.38 is released and imported, just updating get_active_window (in gedit-app.c) fixes the bug. I built gedit from source and compared before/after, it works fine. ** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #177 https://gitlab.gnome.org/GNOME/gedit/issues/177 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #188 https://gitlab.gnome.org/GNOME/gedit/-/issues/188 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871082] [NEW] gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup)
Public bug reported: I've had this bug for I'd say a couple of weeks, maybe a month or two. I use a dual screen setup. If the gedit window is on my secondary (right) screen and I open a recent file, gedit does not open it in the current window and creates a new one (which is annoying and unexpected). The bug doesn't happen if gedit is on my primary (left) screen, or if the gedit window is at the edge of my secondary screen. Also, if there is a gedit window on both screens and I try to open a recent file on the secondary monitor, it will open it in the gedit window on the other (primary) screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 12:40:31 2020 InstallationDate: Installed on 2016-10-27 (1256 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2019-11-09 (149 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1871082 Title: gedit unexpectedly opens a new window when opening a recent file (on a dual screen setup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1871082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
Thanks Rocko. I had this bug too. It used to happen systematically when I moved a Firefox tab over a LibreOffice Writer window. So now, after the gnome-shell 3.36.0-2ubuntu2 update, I tried again and failed to make it crash. Seems fixed. -- 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/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
I will look into it. Here is how to reproduce the bug very easily: - open LibreOffice Writer - open Firefox - resize and move the windows so that they don't overlap - drag the Firefox tab (not window) over LibreOffice Then you instantly get the 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is the backtrace and registers. At first I couldn't reproduce the bug by just moving youtube videos (in firefox) around. But then when I had a document in LibreOffice Writer open (which is the situation I was in over the last few days of crashes), it happened very easily. --- Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 (gdb) bt #0 0x7f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #1 0x7f65563fe3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #2 0x7f65563ff413 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #3 0x7f6556420110 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #4 0x7f65563dee69 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #5 0x7f6555ff0f6f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #6 0x7f6555ff135a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #7 0x7f6555fb9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x7f6555ff1006 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x7f6556ef0fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f6556ef1240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6556ef1533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f65563bb970 in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #13 0x560782a19d85 in ?? () #14 0x7f655613d1e3 in __libc_start_main (main=0x560782a19930, argc=1, argv=0x7ffe0362fc48, init=, fini=, rtld_fini=, stack_end=0x7ffe0362fc38) at ../csu/libc-start.c:308 #15 0x560782a19f5e in ?? () (gdb) info registers rax0xffb0 -80 rbx0x56078765c2c0 94590336352960 rcx0x7 7 rdx0x5607850dab40 94590297025344 rsi0x5607857211d0 94590303605200 rdi0x0 0 rbp0x 0x rsp0x7ffe0362f698 0x7ffe0362f698 r8 0x7f650c003300 140071969764096 r9 0x56078a5d8740 94590386145088 r100x560784463018 94590283952152 r110x7ffe0362f538 140728955237688 r120x1 1 r130x7f650c003350 140071969764176 r140x56078765c2c0 94590336352960 r150x560784e680b0 94590294458544 rip0x7f6555da3624 0x7f6555da3624 eflags 0x10202 [ IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Here is a log with a few crashes. It seems to always come after a few of these: Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5 processes of 1 users. Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [ Supervising 9 threads of 5 processes of 1 users.] Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: Successfully made thread 122522 of process 122427 owned by '1000' RT at priority 10. The log lacks the last crash (~19:20) since I attached gdb to the running gnome-shell process but couldn't switch back to the console gdb was started from (frozen screen, but I could hear the video was still playing). Will try attaching through ssh from another computer next time. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+attachment/5334373/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866222] Re: GNOME Shell crashed with signal 11
Got the same bug (GNOME Shell crashed with signal 11 after a short video freeze) on 20.04. It's pretty recent, it's been crashing my computer a couple of times a day since March 3 (according to the logs). I keep my computer updated every day. Seems to happen when I move a video from one monitor to the other. -- 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/1866222 Title: GNOME Shell crashed with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
