[Touch-packages] [Bug 1966418]
Is this still a problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Fix Released Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418]
I've chatted with Jeremy about this, and he understands that -DUSE_WPE_RENDERER=OFF was intended to allow a transition period for distros to package libwpe and wpebackend-fdo, that WebKit developers don't test it anymore, and that Ubuntu needs to turn it on. I've also reported bug #238932 to consider making it mandatory in the GTK 4 version of WebKit. In the meantime, I wonder how hard it would be to upgrade the legacy internal compositor to support zwp_linux_dmabuf_v1 so that Ubuntu doesn't have to patch mesa. No clue about that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418]
(In reply to Marian Rainer-Harbach from comment #7) > This issue occurs on my machine as well, which has an AMD GPU. So it does > not seem to be directly related to the graphics driver in use. Beware: if you're not certain the issue is caused by the same mesa 21.3 -> 22.0 upgrade, you might have a different underlying issue. Anyway, I'm going to close this as MOVED since the issue is being tracked by mesa now and it seems unlikely that WebKit developers will be able to help more. We can reopen if the mesa issue gets closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418]
OK, then for sure this bug is not the problem that Ubuntu users are seeing. Hi Ubuntu, please file a separate bug. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418]
(In reply to seb128 from comment #12) > The issue also got reported on launchpad for the incoming Ubuntu > https://bugs.launchpad.net/webkit/+bug/1966418 > > It is only an issue under wayland, login into an x11 session makes things > work again You have different/additional information in that downstream bug. I'm not convinced that it's the same as this issue. In your downstream bug, you are seeing: EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) But Adrian has not reported this error. Adrian, do you see that anywhere? If not, we'll need a separate bug report for them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide
So for the avoidance of doubt, every independent distro has its own custom ca-certificates package with no shared history. I know Debian, Fedora, and openSUSE all have their own completely separate upstreams. Looking at what Fedora does is probably a good idea indeed, just keep in mind it has no shared history with Debian's package. I took a quick look at openSUSE's package and it looks like it has good p11-kit integration as well. Arch uses Fedora; not sure about other independent distros. They all use Mozilla's certificates, but Mozilla doesn't release a package in a way that's directly usable by distros. Debian's ca-certificates implements certificate blacklisting by putting a ! character at the start of a line in /etc/ca-certificates.conf (which doesn't exist on other distros). Once a certificate is removed, it stays removed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743339 which was never fixed. ** Bug watch added: Debian Bug tracker #743339 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743339 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 844081]
(In reply to jeff from comment #5) > To my knowledge, Canonicals contribution is only in Canonicals patched > version of accountsservice. If I install accountsservice-ubuntu from the > Arch AUR, LightDM will then show the user background. Meaning, the > underlying code is indeed in LightDM. But hey, what do I know? Canonical is still shipping 0011-add-background-file-support.patch, which adds a background-file property to ActUser. Probably they feel no need to switch to the extension interface because the patch is working fine for them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/844081 Title: Unity Greeter - Background of the Unity Greeter should reflect the background chosen by the user that is currently selected Status in accountsservice: Fix Released Status in Ayatana Design: Fix Released Status in Light Display Manager: Fix Released Status in Unity Greeter: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Bug description: Background of the Unity Greeter should reflect the background chosen by the user that is currently selected. e.g. the background the user has selected on their desktop should be displayed in the greeter. See the attached animation login_screen_v02_WP.mov to understand exactly how the backgrounds should crossfade. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/844081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1259562]
Seems these patches have been forgotten -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1259562 Title: Old guest users pollute accountsservice Status in accountsservice: Confirmed Status in Light Display Manager: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: When you log out from a guest session, the temporary guest account is removed - but only almost. The folder /var/lib/AccountsService/users gets 'polluted' with files for previous guest users. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1259562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Also affects: systemd (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1141137 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404702] Re: selected radio button is not visible in WebKit 2.6 in Ambiance
Hi from upstream, WebKitGTK+ uses GTK_STATE_FLAG_CHECKED to indicate that the toggle button is selected when built against GTK+ 3.14 or newer. When built against older GTK+, it uses GTK_STATE_FLAG_ACTIVE. That is the correct behavior. See: https://github.com/WebKit/webkit/blob/master/Source/WebCore/rendering/RenderThemeGtk.cpp#L490 So what is wrong in Ubuntu? I dunno. :) Maybe Ambiance has not been updated for GTK+ 3.14 (but then I would expect toggle buttons to be broken in all apps), or perhaps you just need to rebuild WebKitGTK+ (but presumably that has happened sometime since this bug was filed). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1404702 Title: selected radio button is not visible in WebKit 2.6 in Ambiance Status in ubuntu-themes package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: I'm running WebKit 2.6.2 on Ubuntu 15.04 (Vivid). With this version of WebKit, a selected radio button looks exactly like an unselected radio button in the Ambiance theme. You can see this, for example, if you run Epiphany and visit http://www.w3schools.com/HTML/tryit.asp?filename=tryhtml_radio, or any other web page with radio buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1404702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
