The inspector snap shows storage devices and their mount points. The mount-observe plug is needed to observe the mount points. Kindly grant the auto connect.
Thanks, Soumyadeep Ghosh
Hi, based on the functionality of the inspector snap, it makes sense for this snap to read mount table and quota information through mount-observe interface. +1 from me
+1 to mount-observe as the inspector app states that is intended for viewing various information about your system.
+2 for, 0 against. Granting mount-observe auto-connect to inspector snap.
this is now live
Is there any plug to see the output of lspci command? I have checked the interfaces and there seem to be none. @0xnishit
That should be hardware-observe…
This is without hardware-observe
00:00.0 Class 0600: Device 8086:9a36 (rev 05)
00:01.0 Class 0604: Device 8086:9a01 (rev 05)
00:02.0 Class 0300: Device 8086:9a60 (rev 01)
00:06.0 Class 0604: Device 8086:9a0f (rev 05)
00:08.0 Class 0880: Device 8086:9a11 (rev 05)
00:0a.0 Class 1180: Device 8086:9a0d (rev 01)
00:0d.0 Class 0c03: Device 8086:9a17 (rev 05)
00:14.0 Class 0c03: Device 8086:43ed (rev 11)
00:14.2 Class 0500: Device 8086:43ef (rev 11)
00:14.3 Class 0280: Device 8086:43f0 (rev 11)
00:15.0 Class 0c80: Device 8086:43e8 (rev 11)
00:16.0 Class 0780: Device 8086:43e0 (rev 11)
00:17.0 Class 0106: Device 8086:43d3 (rev 11)
00:1d.0 Class 0604: Device 8086:43b4 (rev 11)
00:1f.0 Class 0601: Device 8086:438b (rev 11)
00:1f.3 Class 0401: Device 8086:43c8 (rev 11)
00:1f.4 Class 0c05: Device 8086:43a3 (rev 11)
00:1f.5 Class 0c80: Device 8086:43a4 (rev 11)
01:00.0 Class 0302: Device 10de:25a2 (rev a1)
02:00.0 Class 0108: Device 2646:500d (rev 01)
03:00.0 Class 0200: Device 10ec:8168 (rev 15)
And this is with
00:00.0 Class 0600: Device 8086:9a36 (rev 05)
00:01.0 Class 0604: Device 8086:9a01 (rev 05)
00:02.0 Class 0300: Device 8086:9a60 (rev 01)
00:06.0 Class 0604: Device 8086:9a0f (rev 05)
00:08.0 Class 0880: Device 8086:9a11 (rev 05)
00:0a.0 Class 1180: Device 8086:9a0d (rev 01)
00:0d.0 Class 0c03: Device 8086:9a17 (rev 05)
00:14.0 Class 0c03: Device 8086:43ed (rev 11)
00:14.2 Class 0500: Device 8086:43ef (rev 11)
00:14.3 Class 0280: Device 8086:43f0 (rev 11)
00:15.0 Class 0c80: Device 8086:43e8 (rev 11)
00:16.0 Class 0780: Device 8086:43e0 (rev 11)
00:17.0 Class 0106: Device 8086:43d3 (rev 11)
00:1d.0 Class 0604: Device 8086:43b4 (rev 11)
00:1f.0 Class 0601: Device 8086:438b (rev 11)
00:1f.3 Class 0401: Device 8086:43c8 (rev 11)
00:1f.4 Class 0c05: Device 8086:43a3 (rev 11)
00:1f.5 Class 0c80: Device 8086:43a4 (rev 11)
01:00.0 Class 0302: Device 10de:25a2 (rev a1)
02:00.0 Class 0108: Device 2646:500d (rev 01)
03:00.0 Class 0200: Device 10ec:8168 (rev 15)
It’s the same. Tried with inspector snap on Ubuntu 23.04
Well, it has worked in the snaps where I have used it in the past… you are shipping lspci in your snap proper via a stage package I assume ?
Sure it’s there,
Do you see any denials at runtime when it calls out to lspci ?
Nahhh, snappy-debug is completely silent.
Well, then it is definitely not interface or confinement related
May be due to old lspci?
Since you are using base: core22 I think this is unlikely…