Hi,
ne 2. 5. 2021 v 10:26 odesílatel David Edmundson <david(a)davidedmundson.co.uk>
napsal:
>
>
> On Sat, 1 May 2021, 20:10 Jan Grulich, <jgrulich(a)redhat.com> wrote:
>
>>
>> so 1. 5. 2021 v 17:51 odesílatel Jonas Ådahl <jadahl(a)redhat.com> napsal:
>>
>>> On Sat, May 01, 2021 at 10:49:57AM -0400, Owen Taylor wrote:
>>> > On Sat, May 1, 2021 at 10:09 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
>>> > >
>>> > > On Sat, May 1, 2021 at 9:48 AM Owen Taylor <otaylor(a)redhat.com>
>>> wrote:
>>> > >
>>> > > I agree, do we know anyone who understands Mutter that could work
>>> with
>>> > > someone who understands Qt to figure this out? I've got a couple of
>>> > > folks in mind who could help on the KDE side (who I've CC'd to this
>>> > > email).
>>> >
>>> > Added Jonas Adahl (all things output), Carlos Garnacho (all things
>>> > input) and Oliver Fourdan (compat problems expert) to the Cc:- one of
>>> > them should be able to help.
>>> >
>>> > Since the context is trimmed, the thread here is:
>>> >
>>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
>>>
>>> I have yet to find any recent bugs in mutter that causes issues that
>>> happens only with Qt; last time I and Jan debugged some issues with
>>> Dolphin and Kate resizing wierdly, there were still some Qt issues with
>>> incorrectly committed surface state. I think he is still looking into
>>> those.
>>>
>>
>> Yes, still working on those, but I don't think this issue is relevant
>> here. And I would really like to know whether the "unable to type... "
>> issue is KeepassXC only thing, because so far I haven't seen it and didn't
>> get any other report.
>>
>>
>>
>>> Some issues likely doesn't cause issues on kwin because kwin takes over
>>> window decoration from Qt applications, meaning Qts inability to commit
>>> correct state is papered over by the incorrect intermediate state not
>>> existing, but for example oddly placed menus (that I have seen and can
>>> reproduce) behave exactly the same in e.g. weston as in mutter.
>>>
>>
> Oddly placed menus is something we hit with fractional scaling, it's a
> known Qt bug.
>
> I'm unaware of issues with QtWayland committing invalid state.
>
>
This is the weird resizing issue I mentioned here
https://codereview.qt-project.org/c/qt/qtwayland/+/339395. It's happening
when you move for example with a window from maximized state. I attached a
debug output with some comments from Jonas when we were trying to
investigate why it's happening. It doesn't happen in KDE Plasma as it
doesn't use the shared memory backingstore (I think). I'm still trying to
find out how to fix it.
Regards,
Jan
Hello,
As a part of the initiative of replacing "python-mysql" package by
"python-mysqlclient" package, we tried to fill PRs to the packages to
switch to the new implementation. [1]
We filed PR against the "python-sqlobject" package [2], however even
though the maintainer committed since then to the package, he hasn't
responded to the PR.
Hope this message will reach him and the request will be taken care of.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1929101
[2] https://src.fedoraproject.org/rpms/python-sqlobject/pull-request/1
--
Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat
--
No missing expected images.
Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-32-20210501.0):
ID: 875861 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/875861
ID: 875868 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/875868
Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
Has anyone encountered a build problem /usr/bin/strip: /builddir/build/BUILDROOT/here-is-full-path-to-file.so: file truncated ?
I have this problem regularly when I building mesa from git for the i686 architecture.
And the same spec file is successfully builded for the x86_64 architecture.
What's even stranger is that when I call the `strip` command manually for problematic file from the command line, there are no errors.
For exapmple:
$ sudo /usr/bin/systemd-nspawn -q --ephemeral -D /var/lib/mock/fedora-rawhide-i386-bootstrap/root
[root@root-25096e82fbde3423 ~]# /usr/bin/strip /builddir/build/BUILDROOT/mesa-21.2.0-0.3.20210428.0.7ae0719.fc35.i386/usr/lib/dri/nouveau_dri.so
[root@root-25096e82fbde3423 ~]# echo $?
0
I don't understand how to solve this build problem :(
I fill bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1954321 but mainteiner mock package said me that fedora devel list is a proper place.
No missing expected images.
Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-33-20210501.0):
ID: 875845 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/875845
ID: 875852 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/875852
Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
Hello,
As a part of the initiative of replacing "python-mysql" package by
"python-mysqlclient" package, we tried to fill PRs to the packages to
switch to the new implementation. [1]
We filed PR against the "trytond" package [2], however even
though the maintainer was active in Fedora since then, he hasn't
responded to the PR.
Hope this message will reach him and the request will be taken care of.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1929101
[2] https://src.fedoraproject.org/rpms/trytond/pull-request/3
--
Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat
--
Hi,
Userspace OOM killer nohang [1] is orphaned [2] now.
This oom killer supports PSI and GUI notifications.
The package may be of interest to users who are not suitable for
systemd-oomd for some reason. For example, systemd-oomd may kill the whole
session (this applies to XFCE, Mate, LXDE etc. i.e DE in which all
applications are launched in one control group like session-1.session) [4].
Anyone wishing to take over the maintenance is welcome to do so
[1] https://github.com/hakavlad/nohang
[2] https://src.fedoraproject.org/rpms/nohang/
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1933494
Regards,
Alexey Avramov