[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
setting `sudo snap set system experimental.robust-mount-namespace- updates=false` fixes it but just leaving /tmp/.X11-unix untouched doesn't -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Samuele Pedroni (pedronis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
this was also addressed in snapd in https://github.com/snapcore/snapd/pull/9530 in 2.48 ** Changed in: snapd Status: In Progress => Won't Fix ** Changed in: snapd Status: Won't Fix => Fix Committed ** Changed in: snapd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: Fix Released Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Released Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1876083 Title: chromium snap from focal fails DNS lookups, or delays them (ipv6) Status in snapd: New Status in chromium-browser package in Ubuntu: New Bug description: When working with the chromium snap included in focal, it sometimes takes a few seconds to lookup an URL, sometimes it cannot resolve the hostname of the URL at all. Doing the same browsing using firefox doesn't show such behavior, no timeouts, no failed lookups, no delays. Any way how to debug that? That is using IPv6 only. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1876083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Contributing to the discussion with rudeness is not conductive to collaboration, and will be moderated. We do take the fact that people are recompiling snapd because of this as a signal that we need to think whether there are possible ways we can improve the situation. ** Changed in: snapd Assignee: (unassigned) => Samuele Pedroni (pedronis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199439] [NEW] segfault in xorg-server during install of saucy 32bits under vmware
Public bug reported: this is the /var/log/installer/dm with the traceback: X.Org X Server 1.14.1 Release Date: 2013-04-17 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-37-generic i686 Ubuntu Current Operating System: Linux ubuntu 3.10.0-2-generic #10-Ubuntu SMP Fri Jul 5 18:06:05 UTC 2013 i686 Kernel command line: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity Build Date: 04 July 2013 10:10:47AM xorg-server 2:1.14.1-0ubuntu0.8 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.28.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Jul 9 17:54:39 2013 (==) Using system config directory /usr/share/X11/xorg.conf.d Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension XFree86-VidModeExtension Initializing built-in extension XFree86-DGA Initializing built-in extension XFree86-DRI Initializing built-in extension DRI2 Loading extension GLX The XKEYBOARD keymap compiler (xkbcomp) reports: Internal error: Could not resolve keysym XF86AudioMicMute Errors from xkbcomp are not fatal to the X server Activating service name='org.a11y.atspi.Registry' Successfully activated service 'org.a11y.atspi.Registry' SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd:2342): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (at-spi2-registryd:2342): WARNING **: Unable to register client with session manager Error getting login monitor: -2 (panel:2334): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_client_get_root: assertion 'DBUSMENU_IS_CLIENT(client)' failed (panel:2334): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_get_children: assertion 'DBUSMENU_IS_MENUITEM(mi)' failed The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Compat map for group 2 redefined Using new definition Warning: Compat map for group 3 redefined Using new definition Warning: Compat map for group 4 redefined Using new definition Errors from xkbcomp are not fatal to the X server Error getting login monitor: -2 (panel:2334): libindicator-WARNING **: IndicatorObject class does not have an accessible description. (panel:2334): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (panel:2334): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (panel:2334): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_double: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_DOUBLE)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (panel:2334): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (panel:2334): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_double: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_DOUBLE)' failed (panel:2334): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (panel:2334): GLib-CRITICAL **:
[Desktop-packages] [Bug 964597] Re: no keys reported in login keyrings in seahorse after upgrade
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/964597 Title: no keys reported in login keyrings in seahorse after upgrade Status in “seahorse” package in Ubuntu: New Bug description: I have just upgraded from oneiric to precise, I still have a ~/.gnome2/keyrings/login.keyring and it seems gwibber, evolution and ubuntuone can get to and use its content, but if I launch seahorse no keys are listed under login keyring... is this a gnome2/3 thing? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: seahorse 3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 17:07:13 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: Upgraded to precise on 2012-03-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/964597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964597] [NEW] no keys reported in login keyrings in seahorse after upgrade
Public bug reported: I have just upgraded from oneiric to precise, I still have a ~/.gnome2/keyrings/login.keyring and it seems gwibber, evolution and ubuntuone can get to and use its content, but if I launch seahorse no keys are listed under login keyring... is this a gnome2/3 thing? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: seahorse 3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 17:07:13 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: Upgraded to precise on 2012-03-25 (0 days ago) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/964597 Title: no keys reported in login keyrings in seahorse after upgrade Status in “seahorse” package in Ubuntu: New Bug description: I have just upgraded from oneiric to precise, I still have a ~/.gnome2/keyrings/login.keyring and it seems gwibber, evolution and ubuntuone can get to and use its content, but if I launch seahorse no keys are listed under login keyring... is this a gnome2/3 thing? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: seahorse 3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 17:07:13 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: Upgraded to precise on 2012-03-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/964597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
