https://bugs.kde.org/show_bug.cgi?id=494948
--- Comment #2 from Adam Williamson ---
It's still happening frequently in openQA, I have to restart tests that fail on
this two or three times per day (and that means they're failing much more
often, as there's already one automat
https://bugs.kde.org/show_bug.cgi?id=495098
--- Comment #5 from Adam Williamson ---
https://a11ysupport.io/learn/at/orca documents "Key Pad Plus" as "start reading
from current position"...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495098
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=494948
Bug ID: 494948
Summary: Launchers sometimes missing from Favorites menu in
Fedora openQA testing
Classification: Plasma
Product: plasmashell
Version: 6.2.1
Platform: Fedora RP
https://bugs.kde.org/show_bug.cgi?id=494251
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=493295
--- Comment #4 from Adam Williamson ---
Hah. Yes. And I just spent an hour re-investigating the same damn
problem...because the backport of this fix got dropped from the Fedora package
when it was bumped to 6.2.0, but this fix is not actually in 6.2.0
https://bugs.kde.org/show_bug.cgi?id=493295
Bug ID: 493295
Summary: Substantially worse software rendering performance
with KDE 6.2 beta compared to 6.1 (Fedora Rawhide)
Classification: Plasma
Product: kwin
Version: 6.1.90
https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #10 from Adam Williamson ---
I think there was some debate about that in the GNOME issue(s), which is partly
why I linked there...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #8 from Adam Williamson ---
actually, I *think*
https://fedorapeople.org/groups/qa/openqa-repos/openqa-testrepo-2/ should fit
the bill, it contains an unsigned package. This repo definition should work:
[openqa-testrepo-2]
name=openQA test
https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #6 from Adam Williamson ---
well, I ran into this testing Fedora side tags, which are designed to be
ephemeral unfortunately. There aren't any permanent ones AFAIK. It should be
relatively easy to just build a dummy RPM package and cre
https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #3 from Adam Williamson ---
On a quick look, it seems like PK does actually provide an interface for this
which g-s is using. g-s sets an `untrusted_question` attribute on some class
(there is too much obfuscation for me to bother figuring
https://bugs.kde.org/show_bug.cgi?id=487595
--- Comment #7 from Adam Williamson ---
Not beyond the one in the initial comment, no. That's as far as I looked. I got
here via https://bugzilla.redhat.com/show_bug.cgi?id=2270572 , where I noticed
that the Papirus icon theme has some copyri
https://bugs.kde.org/show_bug.cgi?id=487595
--- Comment #5 from Adam Williamson ---
Nate: I asked Richard Fontana and he broadly confirmed my view, seems we didn't
get around to getting a public comment posted, though.
> Adam, please do feel free to contact a lawyer about this, as
https://bugs.kde.org/show_bug.cgi?id=488388
--- Comment #1 from Adam Williamson ---
This is specifically an issue for doing openQA testing of side tags in Fedora,
which we do for e.g. the Python mass rebuilds. The packages in the side tag are
not signed. We set up a repo config with `gpgcheck=0
https://bugs.kde.org/show_bug.cgi?id=488388
Bug ID: 488388
Summary: Discover shows an unrecoverable error when packages
are unsigned, even if the repo has `gpgcheck=0`
Classification: Applications
Product: Discover
Version: 6.1.0
https://bugs.kde.org/show_bug.cgi?id=487715
Bug ID: 487715
Summary: alt-d-s shortcut to open desktop settings does nothing
until you click on the desktop once (Plasma 6.0.90)
Classification: Plasma
Product: kwin
Version: unspecif
https://bugs.kde.org/show_bug.cgi?id=487595
--- Comment #2 from Adam Williamson ---
The icon you are using for Facebook *is* the 'f' from the Facebook logo,
isolated from the rest of the Facebook logo and with its color changed, both
against Facebook's guidelines for using t
https://bugs.kde.org/show_bug.cgi?id=487595
Bug ID: 487595
Summary: Breeze icon theme uses copyrighted icons without
acknowledgement or compliance with the owners'
guidelines
Classification: Plasma
Product: Breeze
https://bugs.kde.org/show_bug.cgi?id=478614
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=479235
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=473835
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=466282
--- Comment #5 from Adam Williamson ---
No, that can't work. It has to be something that can be poked by a script
during startup, basically - some kind of config file entry, magic file,
something like that.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=466318
--- Comment #1 from Adam Williamson ---
https://invent.kde.org/plasma/discover/-/merge_requests/486 seems to fix it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466318
Bug ID: 466318
Summary: fwupd backend errors on startup with fwupd 1.8.11:
"user agent unset"
Classification: Applications
Product: Discover
Version: 5.27.1
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=466282
--- Comment #2 from Adam Williamson ---
well, there may not be a good cross-distro way to do it :/ AFAIK, live boot is
implemented differently on different distros, so there isn't just one reliable
indicator. Fedora's live environment user
https://bugs.kde.org/show_bug.cgi?id=458865
--- Comment #49 from Adam Williamson ---
oof, and I just realized...we do actually run SDDM on X on Fedora (because it
has bugs running on Wayland). So the patch from this issue is probably relevant
to that case after all...
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458865
--- Comment #47 from Adam Williamson ---
(In reply to Antonio Rojas from comment #46)
> (In reply to Adam Williamson from comment #45)
> > So we have folks running into this on Fedora:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2133
https://bugs.kde.org/show_bug.cgi?id=458865
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #45 from
https://bugs.kde.org/show_bug.cgi?id=452837
--- Comment #3 from Adam Williamson ---
Yeah, that's the commit I thought had changed things too. I didn't know how
much of the change was intentional, though.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452837
Bug ID: 452837
Summary: Automount mounts non-removable devices
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=427060
--- Comment #28 from Adam Williamson ---
>From my perspective it seems like this got fixed, then came back. In Fedora 35
we were suffering from this; I backported
https://github.com/KDE/kwin/commit/998bbf4eba724a9b94a5bae62182456b85b11383#d
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #24 from Adam Williamson ---
Yeah, confirmed, clicking twice in the same place does not help at all. Neither
with nor without the "mouse hide" operation in between clicks.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #23 from Adam Williamson ---
Oh well, that answers a question I was about to look into, which was "could
this be to do with https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4123 ?"
- it sounds like the answer is 'n
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #20 from Adam Williamson ---
I just checked, and it looks like we've had 5.24.0 in Rawhide for a few days.
Unfortunately the bug is still present :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #18 from Adam Williamson ---
As mentioned above I tried a git snapshot on 2022-01-28. If the fix landed
after that, though, it's a possibility. I'll try in the morning.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #16 from Adam Williamson ---
https://gitlab.gnome.org/GNOME/mutter/-/issues/2117 , and the fix was
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2257 . Definitely not
the same bug as it's mutter and mutter isn't involved
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #13 from Adam Williamson ---
Created attachment 146234
--> https://bugs.kde.org/attachment.cgi?id=146234&action=edit
KWIN_XWAYLAND_DEBUG=1 messages from anaconda
This is /var/log/messages from an openQA failure with KWIN_XWAYLAND_
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #12 from Adam Williamson ---
Yeah, I can give that a shot tomorrow. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #10 from Adam Williamson ---
Um. I think maybe not, because it seems when running as the live installer, we
actually force anaconda to run with the X11 backend:
https://github.com/rhinstaller/anaconda/blob/master/data/liveinst/liveinst
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #6 from Adam Williamson ---
I just realized I didn't mention, so in case it's not obvious - the installer
app in use here is built on GTK+.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #5 from Adam Williamson ---
Sure, here's one of the most recent failures -
https://openqa.fedoraproject.org/tests/1114561 . Logs and video at
https://openqa.fedoraproject.org/tests/1114561#downloads . You should be able
to see fro
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #3 from Adam Williamson ---
Bisecting is turning out to be hard because older commits just don't build
against current (everything else), like kwayland-server :( Can't build anything
before f2b29e35 by the looks of it
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #2 from Adam Williamson ---
I tested a build of current git 5.24 head, same bug. I'll try and bisect back
between 5.23.5 and 5.23.90, though it will take a bit of time to do.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=449273
--- Comment #1 from Adam Williamson ---
Created attachment 146003
--> https://bugs.kde.org/attachment.cgi?id=146003&action=edit
how the screen we're trying to interact with looks
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=449273
Bug ID: 449273
Summary: Mouse clicks from openQA (automated test framework) in
Fedora installer on KDE 5.23.90 stop working shortly
after it starts
Product: kwin
Version
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #15 from Adam Williamson ---
https://invent.kde.org/plasma/discover/-/merge_requests/191 should resolve
this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443583
--- Comment #7 from Adam Williamson ---
Aleix filed https://invent.kde.org/plasma/discover/-/merge_requests/192 that
should address the remaining parts of this. I'll try it out later.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=443583
--- Comment #6 from Adam Williamson ---
OK, so backporting
https://codereview.qt-project.org/c/qt/qtdeclarative/+/372646 does seem to fix
the 'undefined' problem. Now every time I change the state of a PackageKit
repo, the *entire page*
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #14 from Adam Williamson ---
ohhh, wait, I see the problem. We're reusing the `error` pointer from the
`flatpak_installation_list_remote_refs_sync()` call for the
`flatpak_installation_remove_remote()`, but that's not s
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #13 from Adam Williamson ---
oh, that error is from the qml, indicating backend.removeSource returned false:
if (!backend.removeSource(sourceId)) {
console.warn("Failed to remov
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #12 from Adam Williamson ---
I'm not sure that would change it at all, actually. This seems to be a bug in
FlatpakSourcesBackend::removeSource(), but I'm not totally sure what. oddly,
the error we get on the console - "qml: F
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #11 from Adam Williamson ---
I don't think so. It's just a bug in
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443455
Adam Williamson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Summary|Flatpak remotes
https://bugs.kde.org/show_bug.cgi?id=443583
Adam Williamson changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=406295
--- Comment #6 from Adam Williamson ---
huh, another finding which kinda surprised me: if you take out the call to
`sourcesView.model.setData` so that the block just looks like this:
onClicked: {
checked
https://bugs.kde.org/show_bug.cgi?id=406295
--- Comment #5 from Adam Williamson ---
oh, sorry, one more note: if you apply my partial fix for
https://bugs.kde.org/show_bug.cgi?id=443455 so that the checkboxes for flatpak
sources are also clickable, you'll find that they behave exactly the
https://bugs.kde.org/show_bug.cgi?id=406295
--- Comment #4 from Adam Williamson ---
Note I think this code, which was essentially identical at the time, must have
been working back in late 2018, or else it's hard to see how this bug could
have been reported and fixed:
https://bugs.kd
https://bugs.kde.org/show_bug.cgi?id=406295
Adam Williamson changed:
What|Removed |Added
CC||aleix...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406295
--- Comment #3 from Adam Williamson ---
So I've been beating my head against this all day and not getting *that* far,
but I can at least say the problem is caused by our handling of clicks on the
checkbox in discover/qml/SourcesPag
https://bugs.kde.org/show_bug.cgi?id=443583
--- Comment #2 from Adam Williamson ---
Oh, I'm not sure yet why we get the 'other repo names changed to undefined'
behaviour. I suspect possibly the PK backend clearing and re-generating its
entire source list somehow causes that, I&#x
https://bugs.kde.org/show_bug.cgi?id=443583
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #6 from Adam Williamson ---
So I looked into this a bit today. It appears to be basically just flat-out
missing functionality; if you compare the similar FlatpakSourcesBackend.cpp,
FwupdSourcesBackend.cpp and PackageKitSourcesBackend.cpp
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #5 from Adam Williamson ---
Created attachment 142273
--> https://bugs.kde.org/attachment.cgi?id=142273&action=edit
screenshot from Fedora 35 KDE
note how the flatpak remote 'checkboxes' are grey, while the 'Firm
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #4 from Adam Williamson ---
That's not how it looks here. I'll attach a screenshot...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443455
--- Comment #2 from Adam Williamson ---
I'm testing on F35, as is Kamil. Note that removing an *enabled* remote works
fine, it's only removing *disabled* remotes that doesn't work.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=443456
Bug ID: 443456
Summary: Toggling repo in Discover doesn't redraw the checkbox,
confusing users
Product: Discover
Version: 5.23.0
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=443455
Bug ID: 443455
Summary: Flatpak remotes are always shown as enabled and greyed
out, disabled ones can't be successfully removed
Product: Discover
Version: 5.23.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=443357
--- Comment #9 from Adam Williamson ---
Thanks for the check, both of you. I've applied that to our package downstream.
Sounds like no more upstream 5.22 releases are planned, so I won't bother
submitting it for that branch.
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=443357
--- Comment #6 from Adam Williamson ---
Oh, hmm, think I may have managed it myself after all. Does anyone see anything
wrong with this?
diff --git a/src/plugins/platforms/drm/drm_output.cpp
b/src/plugins/platforms/drm/drm_output.cpp
index 917bb857d
https://bugs.kde.org/show_bug.cgi?id=443357
Adam Williamson changed:
What|Removed |Added
CC||butir...@gmail.com
--- Comment #5 from Adam
https://bugs.kde.org/show_bug.cgi?id=443357
Adam Williamson changed:
What|Removed |Added
Version|unspecified |git-stable-Plasma/5.22
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=443357
--- Comment #3 from Adam Williamson ---
jadahl - who dealt with the similar problems on the mutter (GNOME) side -
passes this along:
"one possibility is that kde changed to do what mutter did for a while, which
is to emulate atomic mode setting
https://bugs.kde.org/show_bug.cgi?id=443357
Adam Williamson changed:
What|Removed |Added
Summary|Don't use atomic mode |Real cursor positi
https://bugs.kde.org/show_bug.cgi?id=443357
--- Comment #2 from Adam Williamson ---
Hum, well. Turning off atomic mode setting doesn't actually solve the problem,
for some reason, on Plasma. It does on GNOME, but not Plasma. I thought my
patch wasn't working so I tested with KWIN_DRM_N
https://bugs.kde.org/show_bug.cgi?id=443357
--- Comment #1 from Adam Williamson ---
I'm trying to do a PR for this, but me writing C++ is like the old gag about
dancing bears, so it may take a minute. :D
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443357
Bug ID: 443357
Summary: Don't use atomic mode setting with virtual GPUs
(causes cursor offset)
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=430036
Adam Williamson changed:
What|Removed |Added
CC|ad...@happyassassin.net |
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=430036
--- Comment #31 from Adam Williamson ---
ah, sorry, forgot to explain that - for the F34 branch -2 is effectively a
no-op. -2 was a straight rebuild on the Rawhide branch for the Rawhide mass
rebuild, it did not happen on the F34 branch. But the commit
https://bugs.kde.org/show_bug.cgi?id=430036
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #29 from
https://bugs.kde.org/show_bug.cgi?id=435389
Adam Williamson changed:
What|Removed |Added
CC||ad...@happyassassin.net
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=350039
--- Comment #7 from Adam Williamson ---
no, sorry, I just figured that was the appropriate state to set it back to from
NEEDINFO.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=350039
Adam Williamson changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=411876
--- Comment #2 from Adam Williamson ---
It seems rather misleading to use the same extension and the same general
format as a very widely-recognized specification, but not actually meet that
specification. At the very least it could be specifically
https://bugs.kde.org/show_bug.cgi?id=411876
Bug ID: 411876
Summary: Plasma themes require non-FDO-compliant .desktop files
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Se
https://bugs.kde.org/show_bug.cgi?id=355970
Adam Williamson changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=355970
--- Comment #7 from Adam Williamson ---
https://bugzilla.redhat.com/show_bug.cgi?id=1285666
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355970
--- Comment #6 from Adam Williamson ---
Yeah, F23 Final shows this instead:
(II) AIGLX: Screen 0 is not DRI2 capable
(EE) AIGLX: reverting to software rendering
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: Loaded and initialized swrast
(II
https://bugs.kde.org/show_bug.cgi?id=355970
--- Comment #5 from Adam Williamson ---
I don't believe the qxl driver has changed anything, but it does look like
there's something up with software rendering. We got GNOME nightlies back today
(they'd been failing to compose for un
88 matches
Mail list logo
