according to the website this would fall under kio
so frameworks and libraries > kio-admin > general
is where i would put it.
1 Like
I have reported this problem to bugs.kde.org/show_bug.cgi?id=518466.
For the future, I’ve created a script that allows one to search for such components:
-
#!/usr/bin/env sh
curl -s 'https://bugs.kde.org/rest/product?type=accessible&include_fields=name,components.name' \
| jq '[.products[]
| {product: .name,
components: [.components[].name | select(test("trash"; "i"))]}
| select(.components | length > 0)]' \
| yq -P
-
- product: plasma4
components:
- widget-trashcan
- product: kio-extras
components:
- Trash KCM
- product: digikam
components:
- Albums-Trash
- Database-Trash
- product: frameworks-kio
components:
- Trash
- product: kicker
components:
- trashapplet
- product: kio
components:
- trash
- product: plasmashell
components:
- Trash widget
Otherwise, I’ll ask a million of these questions, and they’ll be outdated each time someone reorganises Bugzilla.
I wonder whether someone should file an upstream FR for providing a component-equivalent to _all, exposed in the Bugzilla GUI. However, I’m satisfied with polling the REST API, if it’s not too computationally expensive for you! It certainly appears quicker than the website does, so I’m hoping that the opposite is true.
just for my edification, what is the purpose of the last pipe?
i had to install yq but neither yq or jq have a -P option so it throws an error
if i leave it off, i get your same output but including all the [ and ] formatting.
@skyfishgoo, YAML is easier to read than JSON:
| YAML |
JSON |
- product: frameworks-kio
components:
- Trash
- product: plasma4
components:
- widget-trashcan
- product: digikam
components:
- Albums-Trash
- Database-Trash
- product: kicker
components:
- trashapplet
- product: plasmashell
components:
- Trash widget
- product: kio
components:
- trash
- product: kio-extras
components:
- Trash KCM
|
[
{
"product": "kio",
"components": [
"trash"
]
},
{
"product": "kicker",
"components": [
"trashapplet"
]
},
{
"product": "digikam",
"components": [
"Albums-Trash",
"Database-Trash"
]
},
{
"product": "frameworks-kio",
"components": [
"Trash"
]
},
{
"product": "plasmashell",
"components": [
"Trash widget"
]
},
{
"product": "plasma4",
"components": [
"widget-trashcan"
]
},
{
"product": "kio-extras",
"components": [
"Trash KCM"
]
}
]
|
You’re probably using a different implementation, considering that at least two are prominent. For me, it’s:
-
#!/usr/bin/env sh
rpm -qf $(command -v yq) \
--queryformat "$(
cat <<'EOF'
Name: %{NAME}
Version: %{VERSION}
Release: %{RELEASE}
Architecture: %{ARCH}
Install Date: %{INSTALLTIME:date}
Size: %{SIZE}
Signature: %{SIGPGP:pgpsig}
Source RPM: %{SOURCERPM}
Build Date: %{BUILDTIME:date}
Build Host: %{BUILDHOST}
Packager: %{PACKAGER}
Vendor: %{VENDOR}
URL: %{URL}
EOF
)"$'\n' | yq -P
-
Name: yq
Version: 4.47.1
Release: 2.fc43
Architecture: x86_64
Install Date: Thu 30 Oct 2025 20:54:35 GMT
Size: 11798908
Signature: (none)
Source RPM: yq-4.47.1-2.fc43.src.rpm
Build Date: Fri 29 Aug 2025 15:33:43 BST
Build Host: buildvm-x86-27.rdu3.fedoraproject.org
Packager: Fedora Project
Vendor: Fedora Project
URL: https://github.com/mikefarah/yq
1 Like
yeah,
yq --version
yq 0.0.0
not much use.
apt list yp
at least gives
yq/noble,noble,now 3.1.0-3 all [installed]
which would indicate v3.1.0
so uninstalled that, and installed the snap version v4.49.2
now i see the output correctly.
thanks for the push.
changing the search string from "trash" to ‘\"$1\"’ lets me pass the shell variable to the script so i can now search for whatever component i want.
way faster than navigating the website.
1 Like
also just discovered that the argument accepts regular expressions
so searching for .*clock.* will return any component with “clock” in the name.
handy… so i built that into the script by using '\".*$1.*\"'
1 Like
