It's Dell's issue and they are on it https://www.dell.com/community/Linux-General/Dell-xps-13-9370-Webcam-support/td-p/6032049/page/10

Same behavior for Dell XPS 13 9370 and my previous work machine Dell XPS 15 9560.

I second this as I recently installed Solus on my brand new Dell XPS 13 9370 and I didn't have wifi at all due to old linux-firmware shipped in the ISO. Upon updating everything my wifi worked correctly but it was a bit of a pain since no tethered connection was possible at the time of the installation

I am not the OP but I am having the same problem with Killer wifi, same happens even if I tether internet from my phone via USB

Your edit wasn't there when I wrote my suggestion, sorry about that :D

Smth went south with snap update so just do

Yea hence the correction, I saw the first link to kotlin lang and figured you missed the inclusion :) my mistake.

NVM, I thought you were looking for kotlin, not kotlin-native ?

Yea that worked! Message is gone.

I had to uninstall solus and switch to ubuntu due to this, I mentioned it this morning on IRC, nobody replied for the first 3 hours so I had to nuke Solus. Would be nice to get this fixed.

Very much so. Only affects latest current kernel.

A problem for me for example in Chrome when I download a file, right click on the filename in chrome window (that download toolbar underneath with downloaded files) and open in files, quite often I need to do so twice before it actually opens the window. Sometimes it works straight away.

@sunnyflunk never ran yarn with sudo but reinstall fixed it. Odd but cheers.

Duplicate of https://dev.solus-project.com/T5860

I think he means vscode @JoshStrobl since git is actually required for VSCode. I never had git missing on Solus box but when I installed VSCode on Windows machine the first thing that popped was "Install git for git integration to work" or smth like that.

Running pure Budgie flavor, no non-default Window Managers or anything.

Running it on Dell XPS 15 9560 with Intel driver. (Nvidia off)

@ikey any chance to make nvidia-drm.modeset work at all? With xorg 1.19 and latest Nvidia drivers enabling that + few other parameters get rid of the screen tearing when using always-on Nvidia graphics card.

Any chance for an update? I currently have a spare Glaive Corsair mouse lying around but can't use it since ckb doesn't support it and building ckb-next from source gives me an error about libudev.h missing

@JoshStrobl it's probably showing Node used by the Electron framework not the one you are building it with? checks out with current electron https://electron.atom.io/

Freaking a yes!

@JoshStrobl Good idea to mention that the snap you linked is not official. VSCode is still finalizing ownership transition.

I am sorry for bringing up the financial support twice, that is childish of me. My main reasoning was to simply make an emphasis I try to support however I can, not to make it sound like someone owes me something. I am not forced to pay for Solus so I am supporting it purely because I want the project to be successful.

@DataDrake I want to personally thank you for a very rational response. I really liked it and appreciate the effort. I didn't want to list all the features requiring an update as many people have different opinions. For me, it would be mostly typescript integrations like function extraction, fixes to module imports etc but for some those are a non-feature.

VSCode will support snap most likely next release officially anyway in 1-2 month https://github.com/Microsoft/vscode/issues/5458

I don't understand the hostility to the situation either, but if you want to use the admin power to lower the priority sure. @JoshStrobl I guess, I try to support Solus financially and technically whenever possible but this attitude of yours just kills all the passion. It's your stance, you made it clear and I respect that but I don't see you doing the same.

@tristan957 I think it's perfectly valid for people to voice their opinions. While I understand your stand, please be respectful of the right to share an opinion and do not shut people down. If you are tired or annoyed by comments, simply do not reply. We are all using the same distro and want nothing but for it to be perfect.

No worries I am just as frustrated with them. I just wish someone would fine a suitable workaround in the meantime. Not my rules btw. I simply state my own opinion on the matter which is just as valid as yours, upstream issue is upstreams.

In my opinion it's just as crucial to provide latest software. I respect yours but you can just the whole world to bend around your rules. I believe user convenience should go first. I will of course keep running binaries but I might as well run everything from binaries.

It's pointless to ship severely outdated software, that's my main point. What's going to happen next time smth breaks for half a year? It's been 2 month now, we don't know when they are going to support npm 5, there seems to be no traction on the issue tracker.

I think for now you could ship .tar.gz instead of compiling from source. I understand you are seeking to build them from source on your build server but usability suffers. I've been manually downloading and replacing vscode and adding commands to path for the last few releases. Not a super hassle by any means but since the version in repos exist, might as well remove it entirely or update it to not supply outdated application.

@ikey no success xD getting this now

It's a classic snap. When I tried to install atom via

sudo snap install atom

it complained that it needs

--classic

It's just to prevent comments why use Atom from snaps when Solus has it in repo. Main issue here is missing libkeyutils.so.1