[Bug 1727958] Re: Libreoffice writer / calc etc show as white icon in launcher when opened
Launchpad has imported 8 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=100158. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-31T09:21:46+00:00 Rene Engelhard wrote: Hi, from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825043. --- snip --- Since a few versions, it seems that libreoffice processes are not groupped under the same icon in the gnome-shell bar anymore. Each document is creating a new entry (without an icon and named "soffice") in the bar instead of being groupped under their type (one icon for the wordprocessing documents, one for the spreadsheet...) This is rather ugly. I'm using gnome-shell wayland if it matters --- snip --- Turns out it's not "Since a few [LO] versions" but with wayland, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825043#15: --- snip --- OK I just tried on my laptop, running the same version of gnome but running X instead of gnome-shell as a wayland compositor and it's working as expected --- snip --- Quick chat on IRC gives (2016-05-23): 12:31 < _rene_> caolan: you did some gtk3/wayland stuff lately according to https://cgit.freedesktop.org/libreoffice/core/log/?qt=grep=wayland. Is http://bugs.debian.org/825043 known? 12:32 -!- KhaledHosny [~khaled@41.69.28.11] has quit [Ping timeout: 244 seconds] 12:34 <@erAck> cloph: nice idea with COS(PI()*2) 12:34 <@caolan> _rene_: its probably https://bugzilla.redhat.com/show_bug.cgi?id=1334915 12:34 < IZBot> bug 1334915: Fedora-['libreoffice'] low/unspecified NEW Libreoffice Missing icons on dock and Alt+tab on Wayland 12:34 -!- KhaledHosny [~khaled@41.69.97.189] has joined #libreoffice-dev 12:35 <@caolan> something "extra" might have gone wrong reason, but nevertheless there isn't a way to *change* the group of a window in gtk, so when you go from calc to startcenter to writer it gets "stuck" at the first group 12:36 <@caolan> under X we can tweak the bits that gtk3 sets in X manually to move it around, no so under wayland yet. Its super down my list at the moment though Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/0 On 2016-08-02T12:03:12+00:00 Beluga wrote: I guess we can set to NEW. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/1 On 2016-12-01T07:20:09+00:00 Dtardon wrote: *** Bug 104285 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/2 On 2017-02-23T17:01:15+00:00 Caolanm wrote: https://bugzilla.gnome.org/show_bug.cgi?id=779143 for my proposed change to let me at the property we need via gtk Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/3 On 2017-03-23T14:17:46+00:00 Libreoffice-commits wrote: Caolán McNamara committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6903066822900a700ccf67ae70fa171c94644a9a Related: rhbz#1334915 tdf#100158 hack using startcenter icon under wayland It will be available in 5.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/4 On 2017-03-26T05:07:50+00:00 Luke wrote: Ever since http://cgit.freedesktop.org/libreoffice/core/commit/?id=6903066822900a700ccf67ae70fa171c94644a9a Related: rhbz#1334915 tdf#100158 hack using startcenter icon under wayland When I try to launch libreoffice, nothing happens. Reverting this commit fixes the issue. I have reproduced this bug on both Ubuntu 16.04 and 16.10. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1727958/comments/5 On 2017-03-26T09:22:42+00:00 Beluga wrote: (In reply to Luke from comment #5) > Ever since > http://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=6903066822900a700ccf67ae70fa171c94644a9a > > Related: rhbz#1334915 tdf#100158 hack using startcenter icon under wayland > > When I try to launch libreoffice, nothing
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Testing upstream kernel, I can tell this situation is not a Ubuntu kernel specific issue. I can reproduce using upstream kernel. This is where I'm at the moment: BAD kernel : v4.16.18 GOOD kernel : v4.17-rc1 Leaving us to the following 'vmwgfx' commits to bisect: $ git log --oneline v4.16.18..v4.17-rc1 --grep="drm/vmwgfx:" 320b164abb32 Merge tag 'drm-for-v4.17' of git://people.freedesktop.org/~airlied/linux 2a2553cc45c8 Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next 43bfefedd028 drm/vmwgfx: Bump version patchlevel and date 37efe80ce85f drm/vmwgfx: use monotonic event timestamps 20fb5a635a0c drm/vmwgfx: Unpin the screen object backup buffer when not used 89dc15b76fd3 drm/vmwgfx: Stricter count of legacy surface device resources 6073a09210e0 drm/vmwgfx: Use kasprintf 4e3e733b45df drm/vmwgfx: Get rid of the device-private suspended member c3b9b1657344 drm/vmwgfx: Improve on hibernation bf833fd36f9b drm/vmwgfx: Avoid pinning fbdev framebuffers dc366364c4ef drm/vmwgfx: Fix multiple command buffer context use ef86cfee7d74 drm/vmwgfx: Use the cpu blit utility for framebuffer to screen target blits 79273e1b7eb0 drm/vmwgfx: Add a cpu blit utility that can be used for page-backed bos 25db875401c8 drm/vmwgfx: Cursor update fixes 904efd9e3f4c drm/vmwgfx: Send the correct nonblock option for atomic_commit ac3069e67f56 drm/vmwgfx: Move the stdu vblank event to atomic function aa64b3f18aeb drm/vmwgfx: Move screen object page flip to atomic function 3cbe87fcf026 drm/vmwgfx: Remove drm_crtc_arm_vblank_event from atomic flush 4e2f9fa7ffb5 drm/vmwgfx: Move surface copy cmd to atomic function 91e9f352cd1b drm/vmwgfx: Avoid iterating over display unit if crtc is available 25a28906ebee drm/vmwgfx: replace drm_*_unreference with drm_*_put 4f4becef17d6 drm/vmwgfx: Use drm_mode_get_hv_timing() to populate plane clip rectangle As I said, I'll start the bisection on Monday. My first feeling about the potential good candidate assumption was wrong but with recent testing, we now know the fix is amongst the commits listed above ^ - Eric -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1623603] Re: display stays on tty1 on timed login
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- 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/1623603 Title: display stays on tty1 on timed login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1623603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803294] Re: NetworkManager fails establishing OpenVPN connection
[Expired for network-manager-openvpn (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1803294 Title: NetworkManager fails establishing OpenVPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1803294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832971] [NEW] Gimp crashes when the batch processing dialog is opened
Public bug reported: Running Gimp under Ubuntu 19.04. I used David's Batch Processor, files were not opened yet. Unexpectedly i've got this crash message ``` 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.0 (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: Ошибка сегментирования Stack trace: ``` # Stack traces obtained from PID 10028 - Thread 10028 # [New LWP 10030] [New LWP 10031] [New LWP 10032] [New LWP 10033] [New LWP 10034] [New LWP 10035] [New LWP 10036] [New LWP 10038] [New LWP 10039] [New LWP 10040] [New LWP 10041] [New LWP 10042] [New LWP 10043] [New LWP 10044] [New LWP 10045] [New LWP 10046] [New LWP 10047] [New LWP 10073] [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=0x7ffd6ee9ad90, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7fb6544cde00 (LWP 10028) "gimp-2.10" __libc_read (nbytes=256, buf=0x7ffd6ee9ad90, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fb653409700 (LWP 10030) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fb652c08700 (LWP 10031) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fb652407700 (LWP 10032) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fb651c06700 (LWP 10033) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7fb651405700 (LWP 10034) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7fb650c04700 (LWP 10035) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fb643fff700 (LWP 10036) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fb64240b700 (LWP 10038) "gmain" 0x7fb6561b8729 in __GI___poll (fds=0x5572debf9430, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7fb641c0a700 (LWP 10039) "gdbus" 0x7fb6561b8729 in __GI___poll (fds=0x5572dec119a0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7fb61f057700 (LWP 10040) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fb61e856700 (LWP 10041) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fb61e055700 (LWP 10042) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7fb61d854700 (LWP 10043) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7fb61d053700 (LWP 10044) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7fb61c852700 (LWP 10045) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7fb607fff700 (LWP 10046) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 18 Thread 0x7fb6077fe700 (LWP 10047) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 19
[Bug 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1723181 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
I have regular snapshots of my ESXi virtual machines and so using a snapshot before updating packages, I was able to install as many packages as I could before login broke in the way everyone is describing. I got down to the following packages: gir1.2-mutter-2/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2] gnome-shell/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2] gnome-shell-common/bionic-updates,bionic-updates 3.28.4-0ubuntu18.04.1 all [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2] libmutter-2-0/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2] Seems the recent troubleshooting is on the right track. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Thanks Pat. Glad you had the same result as I did. I will start the kernel bisect to find out the commit which introduce the fix and confirm my potential good candidate that I found by doing a git log inspection. Will keep you guys posted. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Eric, I installed the 4.18 kernel on one of my Ubuntu 18.04 VMs by doing 'sudo apt install linux-generic-hwe-18.04' As further evidence that you may be onto something... The system boots up fine, presents a GUI login prompt, and I am able to login and use the system as expected (without having to uncomment #WaylandEnabled=false in /etc/gdm3/custom.conf) -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
I marked this bug affect the kernel 'linux' project, but I can't 'target to series' and choose Bionic, it's not in the option list (something went wrong with that bug I think, but we can figure this out later (when/if an SRU is needed)): The only option I have available are: Ff-series Disco Cosmic Xenial Trusty Precise ** Also affects: linux (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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
I marked this bug affecting the kernel 'linux', but I can't 'target to series' and choose Bionic. It's not in the option list anymore (something went wrong with that bug I think, but we can figure this out later (when/if an SRU is needed)): The only option I have available are: Ff-series Disco Cosmic Xenial Trusty Precise -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
*** This bug is a duplicate of bug 1832138 *** https://bugs.launchpad.net/bugs/1832138 Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes. I have strong belief this kernel fix to be a potential good candidate, but I need to run a bisection to confirm my assumption : commit 140bcaa23a1c37b694910424075a15e009120dbe Author: Thomas Hellstrom Date: Thu Mar 8 10:07:37 2018 +0100 drm/vmwgfx: Fix black screen and device errors when running without fbdev When we are running without fbdev, transitioning from the login screen to X or gnome-shell/wayland will cause a vt switch and the driver will disable svga mode, losing all modesetting resources. However, the kms atomic state does not reflect that and may think that a crtc is still turned on, which will cause device errors when we try to bind an fb to the crtc, and the screen will remain black. Fix this by turning off all kms resources before disabling svga mode. Cc: Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh ** This bug has been marked a duplicate of bug 1832138 Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it -- 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/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
can someone impacted try v4.18 hwr kernel ? and let me know if it works fine (without workarounds) just like it did for me ? I will perform the kernel bisect next week to see what v4.15 is missing that 4.18 has to fix this bug. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
I reported the exact same problem and was able to reproduce. Only using v4.15, if I use the hwe kernel 4.18 on Bionic it passes. I have strong belief this kernel fix to be a potential good candidate, but need to run a bisection to confirm my assumption : commit 140bcaa23a1c37b694910424075a15e009120dbe Author: Thomas Hellstrom Date: Thu Mar 8 10:07:37 2018 +0100 drm/vmwgfx: Fix black screen and device errors when running without fbdev When we are running without fbdev, transitioning from the login screen to X or gnome-shell/wayland will cause a vt switch and the driver will disable svga mode, losing all modesetting resources. However, the kms atomic state does not reflect that and may think that a crtc is still turned on, which will cause device errors when we try to bind an fb to the crtc, and the screen will remain black. Fix this by turning off all kms resources before disabling svga mode. Cc: Signed-off-by: Thomas Hellstrom Reviewed-by: Sinclair Yeh -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
my bug report : https://bugs.launchpad.net/bugs/1832903 -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832947] [NEW] Icons keep selected forever until explicitly deselected
Public bug reported: Every time you click on a desktop icon to do something (open it, open the menu context, etc) the icon gets selected and the selection won't disappear until you click elsewhere in the desktop. The behavior is against the usual expectation that the thing gets selected just to carry on an action on it and don't stay selected afterwards. Indeed, opening a folder or file, opening a context menu, etc. are actions that usually don't require selection at all. It's weird having those selected icons sitting there all the time in orange. ** Affects: gnome-shell-extension-desktop-icons (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-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832947 Title: Icons keep selected forever until explicitly deselected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832946] [NEW] Gnome Shell works the worst after I will launch some apps
Public bug reported: You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 15 18:50:37 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832946 Title: Gnome Shell works the worst after I will launch some apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832946/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832943] [NEW] When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background
Public bug reported: Details in my video: https://photos.app.goo.gl/rNfzi9W4WJPbVc329 ///Add I won't see this bug, if other windows is appeared. I want to compliment Ubuntu developers. Firefox have worked excellent after few updates. Gno-menu animation become more beautiful. But I see sticking small icons near gno-menu button only. And gno-menu still opens slowly on my machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 15 17:56:49 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1832943 Title: When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Hi Daniel, Sorry for the delay. As requested, I reproduced the bug. - I SSH'd into the VM - /var/crash was empty - 'pidof gnome-shell' returned a pid of 1423 - I ran 'sudo kill -ABRT 1423' - two crash reports/files appeared in /var/crash -rw-r- 1 gdm whoopsie 20574823 Jun 15 06:12 _usr_bin_gnome-shell.120.crash -rw-r- 1 gdm whoopsie 2496646 Jun 15 06:12 _usr_bin_Xwayland.120.crash - I ran 'sudo ubuntu-bug' on each crash file - There is now two crash reports at; https://errors.ubuntu.com/user/d0d31e5e858096f38cba06e106ab0375a0e96fd9fda7031d320fa3966f0064bba364acdc53d42bce08a29148a49314d352455fe8b6cb716c20dbf804d8711876 -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
