Bug 2405556

Summary:	Ptyxis doesn't list any containers in "New Terminal"'s "Show Profiles and Containers"
Product:	[Fedora] Fedora	Reporter:	Victoria <royal.victoria>
Component:	ptyxis	Assignee:	Nieves <nmontero>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	christopher, gnome-sig, nmontero
Target Milestone:	---	Keywords:	Desktop, Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-10-27 23:58:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Victoria 2025-10-21 22:00:50 UTC

This is what Toolbox reports in the terminal:

```
€ toolbox list
IMAGE ID      IMAGE NAME                                    CREATED
5c3c49125b27  registry.fedoraproject.org/fedora-toolbox:44  16 hours ago

CONTAINER ID  CONTAINER NAME     CREATED         STATUS   IMAGE NAME
1f99f5089508  fedora-toolbox-44  24 minutes ago  running  registry.fedoraproject.org/fedora-toolbox:44
```

Ptyxis 49.1 
GTK: 4.20.1 (Compiled against 4.20.1)
VTE: 0.82.1 (Compiled against 0.82.0)

Toolbox version: 0.3

Clicking on "Show Profiles and Containers" shows only "My Computer"



Reproducible: Always

Steps to Reproduce:
1. toolbox create
2. toolbox enter
3. exit
4. click on "Show Profiles and Containers" (its next to "New Terminal button")
Actual Results:
Container isn't listed there

Expected Results:
fedora-toolbox-44 would be listed there

Comment 1 Victoria 2025-10-21 22:01:56 UTC

Let me know if there is anything else I can share. I don't really know how to troubleshoot this.

Comment 2 Christopher Boni 2025-10-27 13:54:49 UTC

I'm also experiencing this issue and I've raised it upstream: https://gitlab.gnome.org/chergert/ptyxis/-/issues/489

Comment 3 Victoria 2025-10-27 23:58:10 UTC

The issue was fixed upstream