what's the correct approach for letting the vscode flatpak attach to the host podman to attach to co

O

ott.tar.gzOP•6/30/24, 1:43 PM

I've been using a podman-host script but I was wondering if there was a more... elegant solution.

Oott.tar.gz I've been using a podman-host script but I was wondering if there was a more... ...

J

Jazze (plz ping when reply)•6/30/24, 1:45 PM

Afaik there is a VSCode extension which lets you interact with docker containers from within VSCode. I'm not sure if that works for podman as well

O

ott.tar.gzOP•6/30/24, 1:46 PM

Dev containers, the official one by microsoft? Yeah, that's what i'm using actually

O

ott.tar.gzOP•6/30/24, 1:46 PM

it's sort of a hack to get vscode to think you're actually using docker when you aren't, though

Oott.tar.gz what's the correct approach for letting the vscode flatpak attach to the host po...

J

Jazze (plz ping when reply)•6/30/24, 1:51 PM

Attach through distrobox-enter?

J

Jazze (plz ping when reply)•6/30/24, 1:51 PM

Is a keybind good enough?

J

Jazze (plz ping when reply)•6/30/24, 1:51 PM

You'd need to make a keybind for every new container tho

Oott.tar.gz I've been using a podman-host script but I was wondering if there was a more... ...

H

HikariKnight•6/30/24, 1:56 PM

the "more elegant" solution would be vscode in the container
which is not elegant either

S

Saki•6/30/24, 2:05 PM

Seems like my distrobox-host-exec is not working for various commands? I cannot run brew-installed CLI commands from within the container. What am I doing wrong here?

~> distrobox-host-exec echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> distrobox-host-exec tldr
[127]

~> distrobox-host-exec echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> distrobox-host-exec tldr
[127]

~> distrobox-host-exec echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> distrobox-host-exec tldr
[127]

~> distrobox-host-exec echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> echo $PATH
/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
~> distrobox-host-exec tldr
[127]

O

ott.tar.gzOP•6/30/24, 2:08 PM

I think the podman-host script I'm using might be the most elegant of the choices I have

O

ott.tar.gzOP•6/30/24, 2:08 PM

which is no biggie, I was just curious

Oott.tar.gz I think the podman-host script I'm using might be the most elegant of the choice...

H

HikariKnight•6/30/24, 2:10 PM

that was my conclusion in the end too

O

ott.tar.gzOP•6/30/24, 2:25 PM

I was wondering

O

ott.tar.gzOP•6/30/24, 2:25 PM

how does the Aurora-DX image set that up?

Oott.tar.gz how does the Aurora-DX image set that up?

H

HikariKnight•6/30/24, 2:26 PM

@Niklas

this is your field

O

ott.tar.gzOP•6/30/24, 2:28 PM

Aurora or bluefin or pretty much any ublue image with a dx variant

JJan also, if possible, could you try `udevadm info /sys/devices/pci*/*/*01:00*` ? It...

C

cave monster•6/30/24, 2:32 PM

Absolutely, thanks for checking on my report!

[[

~$ udevadm info /sys/devices/pci*/*/*01:00*
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
M: 0000:01:00.0
R: 0
U: pci
V: nvidia
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0
E: SUBSYSTEM=pci
E: DRIVER=nvidia
E: PCI_CLASS=30200
E: PCI_ID=10DE:1436
E: PCI_SUBSYS_ID=17AA:224D
E: PCI_SLOT_NAME=0000:01:00.0
E: MODALIAS=pci:v000010DEd00001436sv000017AAsd0000224Dbc03sc02i00
E: USEC_INITIALIZED=12205211
E: SYSTEMD_WANTS=nvidia-fallback.service
E: ID_PCI_CLASS_FROM_DATABASE=Display controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=3D controller
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206GLM [Quadro M2200 Mobile]
E: ID_PATH=pci-0000:01:00.0
E: ID_PATH_TAG=pci-0000_01_00_0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/pci0000:00/0000:00:01.0/0000:01:00.1
M: 0000:01:00.1
R: 1
U: pci
V: snd_hda_intel
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.1
E: SUBSYSTEM=pci
E: DRIVER=snd_hda_intel
E: PCI_CLASS=40300
E: PCI_ID=10DE:0FBA
E: PCI_SUBSYS_ID=0000:0000
E: PCI_SLOT_NAME=0000:01:00.1
E: MODALIAS=pci:v000010DEd00000FBAsv00000000sd00000000bc04sc03i00
E: USEC_INITIALIZED=12205785
E: ID_PCI_CLASS_FROM_DATABASE=Multimedia controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Audio device
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206 High Definition Audio Controller
E: ID_PATH=pci-0000:01:00.1
E: ID_PATH_TAG=pci-0000_01_00_1

~$ udevadm info /sys/devices/pci*/*/*01:00*
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
M: 0000:01:00.0
R: 0
U: pci
V: nvidia
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0
E: SUBSYSTEM=pci
E: DRIVER=nvidia
E: PCI_CLASS=30200
E: PCI_ID=10DE:1436
E: PCI_SUBSYS_ID=17AA:224D
E: PCI_SLOT_NAME=0000:01:00.0
E: MODALIAS=pci:v000010DEd00001436sv000017AAsd0000224Dbc03sc02i00
E: USEC_INITIALIZED=12205211
E: SYSTEMD_WANTS=nvidia-fallback.service
E: ID_PCI_CLASS_FROM_DATABASE=Display controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=3D controller
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206GLM [Quadro M2200 Mobile]
E: ID_PATH=pci-0000:01:00.0
E: ID_PATH_TAG=pci-0000_01_00_0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/pci0000:00/0000:00:01.0/0000:01:00.1
M: 0000:01:00.1
R: 1
U: pci
V: snd_hda_intel
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.1
E: SUBSYSTEM=pci
E: DRIVER=snd_hda_intel
E: PCI_CLASS=40300
E: PCI_ID=10DE:0FBA
E: PCI_SUBSYS_ID=0000:0000
E: PCI_SLOT_NAME=0000:01:00.1
E: MODALIAS=pci:v000010DEd00000FBAsv00000000sd00000000bc04sc03i00
E: USEC_INITIALIZED=12205785
E: ID_PCI_CLASS_FROM_DATABASE=Multimedia controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Audio device
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206 High Definition Audio Controller
E: ID_PATH=pci-0000:01:00.1
E: ID_PATH_TAG=pci-0000_01_00_1

~$ udevadm info /sys/devices/pci*/*/*01:00*
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
M: 0000:01:00.0
R: 0
U: pci
V: nvidia
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0
E: SUBSYSTEM=pci
E: DRIVER=nvidia
E: PCI_CLASS=30200
E: PCI_ID=10DE:1436
E: PCI_SUBSYS_ID=17AA:224D
E: PCI_SLOT_NAME=0000:01:00.0
E: MODALIAS=pci:v000010DEd00001436sv000017AAsd0000224Dbc03sc02i00
E: USEC_INITIALIZED=12205211
E: SYSTEMD_WANTS=nvidia-fallback.service
E: ID_PCI_CLASS_FROM_DATABASE=Display controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=3D controller
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206GLM [Quadro M2200 Mobile]
E: ID_PATH=pci-0000:01:00.0
E: ID_PATH_TAG=pci-0000_01_00_0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/pci0000:00/0000:00:01.0/0000:01:00.1
M: 0000:01:00.1
R: 1
U: pci
V: snd_hda_intel
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.1
E: SUBSYSTEM=pci
E: DRIVER=snd_hda_intel
E: PCI_CLASS=40300
E: PCI_ID=10DE:0FBA
E: PCI_SUBSYS_ID=0000:0000
E: PCI_SLOT_NAME=0000:01:00.1
E: MODALIAS=pci:v000010DEd00000FBAsv00000000sd00000000bc04sc03i00
E: USEC_INITIALIZED=12205785
E: ID_PCI_CLASS_FROM_DATABASE=Multimedia controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Audio device
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206 High Definition Audio Controller
E: ID_PATH=pci-0000:01:00.1
E: ID_PATH_TAG=pci-0000_01_00_1

~$ udevadm info /sys/devices/pci*/*/*01:00*
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
M: 0000:01:00.0
R: 0
U: pci
V: nvidia
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0
E: SUBSYSTEM=pci
E: DRIVER=nvidia
E: PCI_CLASS=30200
E: PCI_ID=10DE:1436
E: PCI_SUBSYS_ID=17AA:224D
E: PCI_SLOT_NAME=0000:01:00.0
E: MODALIAS=pci:v000010DEd00001436sv000017AAsd0000224Dbc03sc02i00
E: USEC_INITIALIZED=12205211
E: SYSTEMD_WANTS=nvidia-fallback.service
E: ID_PCI_CLASS_FROM_DATABASE=Display controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=3D controller
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206GLM [Quadro M2200 Mobile]
E: ID_PATH=pci-0000:01:00.0
E: ID_PATH_TAG=pci-0000_01_00_0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/pci0000:00/0000:00:01.0/0000:01:00.1
M: 0000:01:00.1
R: 1
U: pci
V: snd_hda_intel
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.1
E: SUBSYSTEM=pci
E: DRIVER=snd_hda_intel
E: PCI_CLASS=40300
E: PCI_ID=10DE:0FBA
E: PCI_SUBSYS_ID=0000:0000
E: PCI_SLOT_NAME=0000:01:00.1
E: MODALIAS=pci:v000010DEd00000FBAsv00000000sd00000000bc04sc03i00
E: USEC_INITIALIZED=12205785
E: ID_PCI_CLASS_FROM_DATABASE=Multimedia controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Audio device
E: ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
E: ID_MODEL_FROM_DATABASE=GM206 High Definition Audio Controller
E: ID_PATH=pci-0000:01:00.1
E: ID_PATH_TAG=pci-0000_01_00_1

]]

HHikariKnight @Niklas ⚡ this is your field 😅

N

Niklas ⚡•6/30/24, 2:33 PM

Since it ought to be same as bluefin, I’m not sure

N

Niklas ⚡•6/30/24, 2:34 PM

But in the DX image VS code is installed directly on the host

N

Niklas ⚡•6/30/24, 2:35 PM

And docker is preinstalled as well

E

Ellis•6/30/24, 2:37 PM

hai niklas

N

Niklas ⚡•6/30/24, 2:38 PM

Hi

NNiklas ⚡Since it ought to be same as bluefin, I’m not sure

H

HikariKnight•6/30/24, 2:39 PM

yeah but i almost never touch the bluefin stuff, hence the ping

H

HikariKnight•6/30/24, 2:39 PM

also hi yes hello Niklas

R

Robotta•6/30/24, 2:55 PM

is it normal for software to consistently crash everytime i install an app?

R

Robotta•6/30/24, 2:55 PM

it crashes always upon starting to download it

T

tryhardsoccermomswag•6/30/24, 2:55 PM

no

R

Robotta•6/30/24, 2:55 PM

on terminal it works fine however

R

Robotta•6/30/24, 2:56 PM

it used to happen for me too in kde with discover

R

Robotta•6/30/24, 2:56 PM

so this graphical stores hate me for some reason

J

JesterOnMeds•6/30/24, 2:56 PM

Just another day

Ttryhardsoccermomswag no

R

Robotta•6/30/24, 2:58 PM

i know its vague but any possible reason for this?

R

Robotta•6/30/24, 2:58 PM

another casualty of rebasing probably

J

JesterOnMeds•6/30/24, 2:58 PM

Hello Robotta ^^

R

Robotta•6/30/24, 2:58 PM

maybe i should remove my kde conf

R

Robotta•6/30/24, 2:58 PM

it may be conflicting somehow with my gnome

J

JesterOnMeds•6/30/24, 2:59 PM

Hope you are doing alright today.

R

Robotta•6/30/24, 3:00 PM

Thanks

R

Robotta•6/30/24, 3:00 PM

same to you

J

JesterOnMeds•6/30/24, 3:00 PM

Np

J

JesterOnMeds•6/30/24, 3:00 PM

Yep ty.

Ccave monster Absolutely, thanks for checking on my report! [[``` ~$ udevadm info /sys/device...

J

Jan•6/30/24, 3:00 PM

This makes this even stranger
udev clearly has the tags

ID_VENDOR_FROM_DATABASE

ID_VENDOR_FROM_DATABASE

ID_VENDOR_FROM_DATABASE

ID_VENDOR_FROM_DATABASE and

ID_MODEL_FROM_DATABASE

ID_MODEL_FROM_DATABASE

ID_MODEL_FROM_DATABASE

ID_MODEL_FROM_DATABASE yet switcheroo-control can't find either
but it can see what driver is loaded?
But the udev rule for discrete checks fails to detect it?