[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
Next please follow steps 4-5-6 in comment #5, and comment #6. -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
pgim@PGIMdata:~$ sudo ppa-purge ppa:oibaf/graphics-drivers . . PPA purged successfully pgim@PGIMdata:~$ then reboot and the same problem see photo -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
That's a different bug so normally shouldn't be discussed here. However your log shows that the update came from the "oibaf" PPA, which is unsupported and should be removed per comment #5. Start-Date: 2018-11-15 13:49:41 Commandline: apt upgrade Upgrade: libgles2-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libegl-mesa0:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libglapi-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libxatracker2:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libegl1-mesa:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgbm1:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgl1-mesa-dri:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libgl1-mesa-glx:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), mesa-vdpau-drivers:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), mesa-va-drivers:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b), libglx-mesa0:amd64 (19.0~git1811141930.e13dd7~oibaf~b, 19.0~git1811150730.936751~oibaf~b) End-Date: 2018-11-15 13:50:08 That is not an Ubuntu bug. It's a bug in the "oibaf" PPA, just as this bug may also be. -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
OK, before working on your to do list . Yesterday with an update (Start-Date:2018-11-15 13:49:41) on this linux box there where ...libegl-mesa0... in the list of modules. There where no indication of restart required but I reboot the system and the graphic was frozen. See picture attached. There was no possibility to use the mouse or the keyboard to get out of this state. But with ssh I can connect in. You will find also the file var_log_apt_history.log where you find the re-installation of the ubuntu-gnome-desktop (Start-Date: 2018-11-14 11:49:00) which results in recover the screen graphic. ** Attachment added: "Frozen screen, no mouse or keyboard action posible" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803504/+attachment/5213349/+files/IMG_20181116_070043.jpg -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
** Attachment added: "var_log_apt_history.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803504/+attachment/5213350/+files/var_log_apt_history.log -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
Just to let others know: @Plurto 's suggestion to set the dock transparency to FIXED (which makes the dock assume a static color) does not remedy the situation on my machines. I tried with different transparency settings as well. The issue still exists -- 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/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Looking at the gnome-shell JS code referenced by the stack trace, it appears it is indeed disabling extensions when locking the screen. The screenShield.js code handles the lock screen, and pushes and pops a "session mode" of "lock-screen". In sessioMode.js, the "lock-screen" mode is defined with allowExtensions=false. Finally, extensionSystem.js watches session mode changes and calls the various extension enable/disable callbacks as needed. So somehow ubuntu-dock has a stale window in Transparency._trackedWindows that triggers an exception while trying to disable the dock when locking the screen. It fails to fully disable the dock, so it displays over the top of the lock screen. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
The above stack trace seems to be tied to this other message:
Nov 16 11:41:38 scruffy gnome-shell[5626]: Object Meta.WindowActor
(0x560d5092bb00), has been already deallocated — impossible to access
it. This might be caused by the object having been destroyed from C code
using something such as destroy(), dispose(), or remove() vfuncs.
The error seems to be on the disconnect() call in
Transparency.disable():
for (let key of this._trackedWindows.keys())
this._trackedWindows.get(key).forEach(id => {
key.disconnect(id);
});
this._trackedWindows.clear();
Presumably the remainder of the clean-up performed by this function and
its callers is not performed, leaving the shell in an inconsistent
state.
I'm still not sure why gnome-shell is trying to disable the extension.
Does it disable extensions when locking the screen?
--
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/1769383
Title:
Ubuntu dock/launcher is shown on the lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
@jamesh your stack trace is caused by Ubuntu Dock's dynamic transparency which I mentioned before in Comment #17 and can be disabled with the following terminal command: gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
Best I can tell, "workspace-grid" is not in the Ubuntu archive so we should keep this bug closed for now. -- 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/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I noticed this behaviour on my Ubuntu 18.10 system. It is running the Wayland session, and I only have the ubuntu-d...@ubuntu.com and ubuntu- appindicat...@ubuntu.com extensions installed (i.e. no upstream dash-to- dock). I looked in the journal and found the attached GJS stack trace, which seems to be triggered by the disable() call. I haven't been manually enabling/disabling extensions, so don't know why the code path would have been triggered. It might mean some crud was left behind though. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769383/+attachment/5213307/+files/stacktrace.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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
This bug is about the default Ubuntu dock. People installing any additional custom extensions such as dash-to-dock should ideally not comment on bugs in Launchpad until after they have removed the extra extensions. Although it is useful to know if and when some bugs are caused by third party extensions, I don't think this bug falls into that category...? -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785240] Re: Cancelling snapd authorization triggers error notification
The snapd change is not yet in bionic (snapd 2.36.1) so the full test doesn't work. However now the snapd-glib and gnome-software changes are there so and other functionality continues to work so I'm going to mark this as verified. When snapd is updated the error notification will disappear. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1785240 Title: Cancelling snapd authorization triggers error notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785240/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803581] Re: PrepareForShutdown() signal from logind is not handled
Please report this bug to the GDM developers here: https://gitlab.gnome.org/GNOME/gdm/issues and then tell us the new bug ID. ** Summary changed: - PrepareForShutdown() is not handled + PrepareForShutdown() signal from logind is not handled ** 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/1803581 Title: PrepareForShutdown() signal from logind is not handled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799714] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_t
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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1799714
Title:
gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
ffi_closure_unix64_inner() from ffi_closure_unix64() from
_meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout()
while logging {"Function IdleMonitorWatchFunc terminated with
uncatchable exception"}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799714/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
Thanks! To remove the PPA: 1. sudo apt install ppa-purge 2. sudo ppa-purge -o oibaf # or something like that!? 3. Reboot Now tell us if the problem still happens. If it does then please: 4. dpkg -l > allpackages.txt and send us the file 'allpackages.txt'. 5. sudo apt install mesa-utils 6. glxinfo > glxinfo.txt and send us the file 'glxinfo.txt'. ** Summary changed: - Xorg freeze + Screen stops redrawing sometimes when moving windows -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Screen stops redrawing sometimes when moving windows
Oh, also your kernel is stuck in recovery mode: [ 136.650] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=8a9d54df-bf77-4277 -990d-781804a2250b ro recovery nomodeset which will cause graphics problems. To fix that, reboot and then hit Esc as soon as the purple screen appears. Now navigate the menus and choose a regular kernel that does not have the recovery option. -- 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/1803504 Title: Screen stops redrawing sometimes when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799714] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_t
** Summary changed:
- gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
ffi_closure_unix64_inner() from ffi_closure_unix64() from
_meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout()
+ gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
ffi_closure_unix64_inner() from ffi_closure_unix64() from
_meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout() while
logging {"Function IdleMonitorWatchFunc terminated with uncatchable exception"}
--
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/1799714
Title:
gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
ffi_closure_unix64_inner() from ffi_closure_unix64() from
_meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout()
while logging {"Function IdleMonitorWatchFunc terminated with
uncatchable exception"}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799714/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799947] Re: [radeon] Application windows in 18.04.01 go black but launcher is still visible
Please try logging into "Ubuntu on Wayland" instead of "Ubuntu" and tell us if that stopps the bug from happening. ** Summary changed: - Application windows in 18.04.01 go black but launcher is still visible + [radeon] Application windows in 18.04.01 go black but launcher is still visible ** Tags added: radeon ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (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/1799947 Title: [radeon] Application windows in 18.04.01 go black but launcher is still visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1371854] Re: users-admin: group name limited to 16 characters
This bug was fixed in the package gnome-system-tools - 3.0.0-8ubuntu1 --- gnome-system-tools (3.0.0-8ubuntu1) disco; urgency=medium * Sync with Debian. Remaining changes: - debian/control: Recommend packagekit for Ubuntu patches that allow installing packages on demand - Add patches, see patch headers: + 26_user_profiles_conf.patch + 80_gst-packages-common.patch + 81_gst-packages-shares-admin.patch + 82_gst-packages-time-admin.patch + 91_shares_services_detection.patch + 95_timezone_point_selection.patch + 96_ubuntu_ntp_pool.patch + remove_g_thread_init.patch gnome-system-tools (3.0.0-8) unstable; urgency=medium * Removing autotools-dev, it's not required with debhelper 10. gnome-system-tools (3.0.0-7) unstable; urgency=medium * Removing scrollkeeper from build dependencies (Closes: #885630). * Adding max_group_name_32_chars.patch (Closes: #773613, LP: #1371854). * Remove unused files in debian/ directory (Closes: #868981). * Bump debhelper compat to 10. * Bump Standards-Version to 4.1.4. * Making package multiarch-aware. * Dropping GNOME control center mention from description and from suggestions. * Disable services-admin, it does not work with systemd. * Disable network-admin, it's never used nowadays, NetworkManager or Wicd is included into every install. -- Jeremy Bicha Thu, 15 Nov 2018 18:09:15 -0500 ** Changed in: gnome-system-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371854 Title: users-admin: group name limited to 16 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1371854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731628] Re: Cannot add caldav calendar
I got the same behaviour in Ubuntu 18.10 -- 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/1731628 Title: Cannot add caldav calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1731628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730071] Re: Application icons appear stretched when using scaling
Yeah, I've this in my radar for some time. I will. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1730071 Title: Application icons appear stretched when using scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show
As per my tests, it appears in all the versions on a long tap, but not quick one (as X in that case doesn't send two events). -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
It gets better all the while. Now the desktop shows completely (with open application windows). Interaction is not possible in the windows but the content can be seen. -- 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/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772913] Re: Android phone doesn't appear in shotwell
including the url to the upload this time, https://launchpad.net/ubuntu/+source/shotwell/0.28.4-0ubuntu1 -- 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/1772913 Title: Android phone doesn't appear in shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1772913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803586] [NEW] SeaHorse hangs Panel when trying to decrypt file
Public bug reported: Hello , Let's say that we have a file that we need to encrypt , so you go ahead and click Encrypt and then SeaHorse will ask you to choose which PGP to use , if you don't have one then you will be prompted to make one , let's say that we have made the PGP key and we encrypted the key but we didn't save the passphrase in the password manager so you will be prompted to put the password so you can decrypt the file and see the content But when you get prompted to put the passphrase to decrypt, then you decide not to put the passphrase but to cancel the process, you will be prompted second time to put the password automatically , I cancel it again and then the PC works just fine , but the whole menu is stuck , I can't click on Applications/Places/System , but I am able to click on the icons in the panel But it's frozen , I need to logout and login again to be able to use the panel again If I'm missing any information please tell me I would update Thanks. Ubuntu Mate 18.04.1 LTS 4.15.0-39-generic Traditional Panel Marco as Window Manager ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello , Let's say that we have a file that we need to encrypt , so you go ahead and click Encrypt and then SeaHorse will ask you to choose which PGP to use , if you don't have one then you will be prompted to make one , let's say that we have made the PGP key and we encrypted the key but we didn't save the passphrase in the password manager so you will be prompted to put the password so you can decrypt the file and see the content But when you get prompted to put the passphrase to decrypt, then you decide not to put the passphrase but to cancel the process, you will be prompted second time to put the password automatically , I cancel it again and then the PC works just fine , but the whole menu is stuck , I can't click on Applications/Places/System , but I am able to click on the icons in the panel But it's frozen , I need to logout and login again to be able to use the panel again If I'm missing any information please tell me I would update Thanks. - Ubuntu Mate 18.04.1 LTS - 4.15.0-39-generic + 4.15.0-39-generic Traditional Panel + Marco as Window Manager -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1803586 Title: SeaHorse hangs Panel when trying to decrypt file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1803586/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
The following workaround worked for me, no problems now (140.107 - Ubuntu 18.10): 2. Try this as a workaround: edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false -- 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/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803363] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213177/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803363] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213178/+files/ProcEnviron.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/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803363] Re: The default shortcut for taking a screenshot kills X
apport information ** Tags added: apport-collected bionic ** Description changed: I was looking for the default key for taking a screenshot from Unity/GNOME settings and found a list of keyboard shortcuts (as in the attached screenshot). It turns out that Ctrl+Alt+Print also happens to kill X by default. This is not optimal:-) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + GsettingsChanges: + 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 2018-11-13 (2 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213176/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803581] [NEW] PrepareForShutdown() is not handled
Public bug reported: When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutdown() signal is emitted by logind: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ Processes holding delay inhibitor locks can start their pre-shutdown operations and until they finish there is no feedback in a Unity session for the logged in user that shutdown is successfully requested on Xenial. On Bionic, the default Gnome 3 session does handle the signal and logs the user off to GDM, but GDM does not tell that shutdown is pending and the user may think that she/he can log in again or should to something to really start the shutdown. With Ubuntu's default configuration the confusion only lasted up to 5 seconds (default max delay for inhibitor locks), but the next upload of unattended-upgrades increases the delay up to 30 seconds which is more than noticeable (LP: #1803137). Please consider either logging the user off from Unity and stopping GDM to switch over the the plymouth shutdown screen of at least showing a notification about the ongoing shutdown. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1803581 Title: PrepareForShutdown() is not handled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803342] Re: GNOME Shell using older Ubuntu 16.04~18.04 icons on 18.10
The problem is that this bug only happens once out of 20 session starts, so disabling all of my extensions might not show right away. But still, I'm going to do what you asked for. -- 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/1803342 Title: GNOME Shell using older Ubuntu 16.04~18.04 icons on 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797224] Re: Stay on 2.0 for cosmic, update next cycle
https://launchpad.net/ubuntu/+source/tracker/2.1.6-1 ** Changed in: tracker (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1797224 Title: Stay on 2.0 for cosmic, update next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Sorry wrong file this is the file with the $ prime-select intel ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5213087/+files/gpu-manager.log -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Sorry, i missed comment #29, but there are a lot of bug reports out there, some of them over a year old, which describe the same issue. My reproduction steps, tested on a virtualbox machine: 1) Fresh-Install Ubuntu 18.0.4.1 LTS 2) Install package 'chrome-gnome-shell' 3) Navigate to https://extensions.gnome.org/extension/307/dash-to-dock, install firefox/chrome extension and install dash-to-dock extension. 4) Restart 5) On next lock the ubuntu-dock reappears and the following journalctl /usr/bin/gnome-shell output is generated: Nov 15 12:53:15 ubuntu gnome-shell[1143]: Extension "ubuntu- d...@ubuntu.com" had error: TypeError: dockManager is null The suggested fix is resolving this and a quick look into https://git.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/tree/extension.js?h=ubuntu/bionic exposes, that the issue is a simple missing null-check in the disable() function where dockManager.destroy() is called on a null-instance, which should be added in either way. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@albertomilone here is my gpu-manager.log this is a fresh install and all updates have been made ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5213084/+files/gpu-manager.log -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
I'm having the same issue. The login screen appears after I press ctrl+alt+f2 and then ctrl+alt+f1. -- 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/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776978] Re: Update to calendar invitations cannot be processed: HTTP error code 412
I already switched back to Thunderbird. TB has its issues, too. But I can use it as a productive tool. Unfortunately, evolution is not usable in a professional environment at this stage. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1776978 Title: Update to calendar invitations cannot be processed: HTTP error code 412 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292453] Re: after upgrading to 13.10 gnome shell crush
Roi, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Do you still see a problem related to the one that you reported? Please let us know if you do otherwise this bug report will expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: gnome-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1292453 Title: after upgrading to 13.10 gnome shell crush To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1292453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Xorg freeze
Here comes the video. How can I find that PPA indicated above. With lsmod there is no ...oibaf... on the system. Could you make a proposal for a better title? ** Attachment added: "Video with movements on screen to see effect on graphic" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803504/+attachment/5213041/+files/VID_20181115_100642.mp4 -- 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/1803504 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730071] Re: Application icons appear stretched when using scaling
Marco, could you have a look to this one? ** Summary changed: - Application icons appear stretched + Application icons appear stretched when using scaling ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1730071 Title: Application icons appear stretched when using scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795279] Re: 18.10 Wayland session closes when using Slack and possibly other Electron snap app
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 that happens for me too, the first indication something is bad is when XWayland crashes: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7ff1aca21535 in __GI_abort () at abort.c:79 #2 0x56129429c75a in OsAbort () at ../../../../os/utils.c:1350 #3 0x5612942a2263 in AbortServer () at ../../../../os/log.c:877 #4 0x5612942a30c9 in FatalError (f=f@entry=0x5612942c7090 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1015 #5 0x561294299b71 in OsSigHandler (signo=11, sip=, unused=) at ../../../../os/osinit.c:156 #6 #7 0x7ff1a840 in st_renderbuffer_delete (ctx=0x5612949b9c30, rb=0x56129510d120) at ../../../src/mesa/state_tracker/st_cb_fbo.c:241 #8 0x7ff1a8e51521 in _mesa_reference_renderbuffer_ (ptr=ptr@entry=0x56129510d6f8, rb=rb@entry=0x0) at ../../../src/mesa/main/renderbuffer.c:212 #9 0x7ff1a8ddfd2a in _mesa_reference_renderbuffer (rb=0x0, ptr=0x56129510d6f8) at ../../../src/mesa/main/renderbuffer.h:72 #10 _mesa_free_framebuffer_data (fb=fb@entry=0x56129510d5b0) at ../../../src/mesa/main/framebuffer.c:229 #11 0x7ff1a8ddfd7e in _mesa_destroy_framebuffer (fb=0x56129510d5b0) at ../../../src/mesa/main/framebuffer.c:207 #12 0x7ff1a8ddfe29 in _mesa_reference_framebuffer_ (ptr=ptr@entry=0x5612954d4630, fb=fb@entry=0x0) at ../../../src/mesa/main/framebuffer.c:265 #13 0x7ff1a8d45cd2 in _mesa_reference_framebuffer (fb=0x0, ptr=0x5612954d4630) at ../../../src/mesa/main/framebuffer.h:63 #14 _mesa_free_context_data (ctx=ctx@entry=0x5612954d4520) at ../../../src/mesa/main/context.c:1326 #15 0x7ff1a8efbd1d in st_destroy_context (st=0x5612951067d0) at ../../../src/mesa/state_tracker/st_context.c:653 #16 0x7ff1a90de1e9 in dri_destroy_context (cPriv=) at ../../../../../src/gallium/state_trackers/dri/dri_context.c:239 #17 0x7ff1a90dd0d3 in driDestroyContext (pcp=0x561294f0c870) at ../../../../../../src/mesa/drivers/dri/common/dri_util.c:524 #18 0x5612941bf2d9 in __glXDRIcontextDestroy (baseContext=0x561294f1e6b0) at ../../../../glx/glxdriswrast.c:132 #19 0x5612941be02b in __glXFreeContext (cx=0x561294f1e6b0) at ../../../../glx/glxext.c:190 #20 ContextGone (cx=0x561294f1e6b0, id=) at ../../../../glx/glxext.c:82 #21 0x56129428845d in doFreeResource (res=0x56129510c490, skip=skip@entry=0) at ../../../../dix/resource.c:880 #22 0x561294289116 in FreeResourceByType (id=, type=, skipFree=skipFree@entry=0) at ../../../../dix/resource.c:941 #23 0x5612941c32d9 in __glXDisp_DestroyContext (cl=, pc=0x561294e3cc70 "\227\004\002") at ../../../../glx/glxcmds.c:437 #24 0x5612942a8195 in dispatch_DestroyContext (client=0x561294ea51b0) at ../../../../glx/vnd_dispatch_stubs.c:82 #25 0x561294263b4e in Dispatch () at ../../../../dix/dispatch.c:478 #26 0x561294267af6 in dix_main (argc=12, argv=0x7ffe34281638, envp=) at ../../../../dix/main.c:276 #27 0x7ff1aca2309b in __libc_start_main (main=0x5612941391b0 , argc=12, argv=0x7ffe34281638, init=, fini=, rtld_fini=, stack_end=0x7ffe34281628) at ../csu/libc-start.c:308 #28 0x5612941391ea in _start () at ../../../../glx/glxcmds.c:125 which I think makes this a duplicate of bug #1754693 ** This bug has been marked a duplicate of bug 1754693 Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] -- 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/1795279 Title: 18.10 Wayland session closes when using Slack and possibly other Electron snap app To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1795279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
The same is happening on 18.04.1 kernel 4.15.0-39-generic @ 15/11/2018 -- 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/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: The wrong background flashes up briefly during the login animation since Yaru was introduced
I now think the proposed gnome-shell version 3.30.1-2ubuntu1.18.10.1 is fine. It doesn't need fixing in itself but it does hit a mutter bug which needs fixing per the above link. Since they would be released at different times anyway, and the secondary regression is probably already visible in disco, we may as well release the gnome-shell fix to cosmic now. The mutter fix is complete and will come soon (only waiting on upstream review). ** Tags removed: verification-failed verification-failed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1789356 Title: The wrong background flashes up briefly during the login animation since Yaru was introduced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803515] [NEW] Update to 3.30.5
Public bug reported: There is a new stable version available, we should update (and maybe SRU it?) ** Affects: gnome-software (Ubuntu) Importance: Wishlist Assignee: Robert Ancell (robert-ancell) Status: Triaged ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1803515 Title: Update to 3.30.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1803515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795279] Re: Slack and possibly other Electron snap apps crash under Wayland
Same thing happens for me. Ubuntu 18.04 on Wayland. It also happens with the Vscode snap. -- 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/1795279 Title: 18.10 Wayland session closes when using Slack and possibly other Electron snap app To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1795279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795279] Re: Slack and possibly other Electron snap apps crash under Wayland
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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/1795279 Title: 18.10 Wayland session closes when using Slack and possibly other Electron snap app To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1795279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795279] Re: Slack and possibly other Electron snap apps crash under Wayland
Could you add your journalctl log after triggering the issue? ** Tags added: rls-cc-incoming ** Summary changed: - Slack and possibly other Electron snap apps crash under Wayland + 18.10 Wayland session closes when using Slack and possibly other Electron snap app -- 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/1795279 Title: 18.10 Wayland session closes when using Slack and possibly other Electron snap app To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1795279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This requires the following fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19fffc8450d4378580a8f019b195c4617083176f https://gitlab.freedesktop.org/upower/upower/merge_requests/19 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/278 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/266 ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-control-center (Ubuntu Artful) ** No longer affects: gnome-shell (Ubuntu Artful) ** No longer affects: upower (Ubuntu Artful) ** No longer affects: linux (Ubuntu Artful) -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show
per re-test #16, and #17, confirmed that 1. on bionic, with new gnome-shell, app grid properly appears after upgrade to new version. 2. on cosmic, app grid works without the upgrade to new version. (test with the cosmic cd as live image) -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776978] Re: Update to calendar invitations cannot be processed: HTTP error code 412
So this bug was reported on 14th of June 2018 but it was _confirmed_ only on 7th of November 2018? With this speed we can expect the fix to be rolled out some time end of 2019? This is a serious issue and I got a plenty of troubles at work already because I always click on "Accept" directly in the email invitation which does not display any error but an "information" saying exactly this: "Unable to send item to calendar 'myCal'. Cannot receive calendar objects: Invalid object" and nothing else. I have never noticed this small information to popup somewhere in the calendar part of the invitation email and always thought I am fine. Until I got few notices from my boss that I am not accepting the invitations. So I started to look for a problem and only then I realized that all my "accepts" from Evolution are not sent. Besides that the fact I cannot edit my calendar entries eventhough I am not the organizer is also a problem. I cannot add (invite) anybody else for example and always have to go to Google Calendar (which I have to everytime now to either accept or decline the invitation). I started using Evolution only recently as I was using Thunderbird for dozens of years before but got tired with it. But now when I see the speed of solving serious issues, I think I am switching back soon. Evolution v.: 3.28.5-0ubuntu0.18.04.1 OS: Ubuntu 18.04 x64 Desktop: Unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1776978 Title: Update to calendar invitations cannot be processed: HTTP error code 412 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Xorg freeze
Can you please: 1. Change the bug title to better describe the problem; and 2. Attach a video of the problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (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/1803504 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803504] Re: Xorg freeze
Also, 3. You seem to be using an unsupported version of Mesa and other packages. Please remove that PPA (LP-PPA-oibaf-graphics-drivers) from the system and retest. -- 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/1803504 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show
** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon, or app grid won't show To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+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
** Description changed: https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5 Upstream issue (reopened): https://gitlab.gnome.org/GNOME/mutter/issues/15 Originally reported as bug 1422253 and fixed in 18.04, but that crash (fixed) was due to a different condition. + + Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453 --- gnome-shell crashed and restarted while I was using it. ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-1ubuntu1 Uname: Linux 4.19.0-041900rc3-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 10 12:39:16 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1536081658 InstallationDate: Installed on 2017-08-16 (389 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago) UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo -- 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/ubuntu/+source/gnome-shell/+bug/1791574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
