[Desktop-packages] [Bug 2079895]

2024-09-12 Thread Mcatanzaro-c
Pull request: https://github.com/WebKit/WebKit/pull/33553 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: epiphany-browser fails to build on s390x with webkit 2.45 S

[Desktop-packages] [Bug 2079895]

2024-09-12 Thread Mcatanzaro-c
Just kidding, I think I have a cairo build rather than a skia build. Anyway, a good opportunity for me to fix it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: e

[Desktop-packages] [Bug 2079895]

2024-09-12 Thread Mcatanzaro-c
This is now happening on x86_64 as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: epiphany-browser fails to build on s390x with webkit 2.45 Status in Webkit:

[Desktop-packages] [Bug 1966418]

2024-08-19 Thread Mcatanzaro-c
In the past two years, the WPE renderer has itself also been removed. This bug is surely not relevant to anybody in 2024. You're hitting some other bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpa

[Desktop-packages] [Bug 2023322]

2024-02-23 Thread Mcatanzaro-c
Hi Craig and Thomas (and Emil if you're still around): if you're still encountering problems with NVIDIA graphics, please report new a bug and leave a comment here linking to the new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ye

[Desktop-packages] [Bug 2023322]

2023-09-22 Thread Mcatanzaro-c
(In reply to Thomas Zajic from comment #56) > Is this the same bug that is being discussed here? No, because the problem here is specific to GTK 4 and has been around for years. That is, since you didn't have this problem with 2.40, this bug is not your bug. You're probably hitting either bug #25