SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Have wine/proton installed 2. Have javascript based application using wine/proton(Vampire Survivors, America's Cardroom, Conan Exile's launcher all have the same issue) 3. Launch from desktop shortcut, gui wrapper(such as steam), or sh script.(fails to open) OBSERVED RESULT Plasmashell error: "Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: net.js:329 Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: err = this._handle.open(fd); Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: ^ Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: Error: EINVAL: invalid argument, uv_pipe_open Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at new Socket (net.js:329:26) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at createWritableStdioStream (internal/bootstrap/switches/is_main_thread.js:67:18) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at process.getStdout [as stdout] (internal/bootstrap/switches/is_main_thread.js:122:12) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at Object.<anonymous> (electron/js2c/browser_init.js:185:793) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at Object../lib/browser/init.ts (electron/js2c/browser_init.js:185:3714) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at __webpack_require__ (electron/js2c/browser_init.js:1:128) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at electron/js2c/browser_init.js:1:1200 Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at electron/js2c/browser_init.js:1:1267 Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:277:7) Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:219:10) { Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: errno: -4071, Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: code: 'EINVAL', Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: syscall: 'uv_pipe_open' Sep 16 13:29:58 chazzy-aero15sa plasmashell[125294]: }" Program fails to open, and throws the above error. EXPECTED RESULT Program should launch normally as it did in previous plasma versions without throwing the above error. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro OS(Arch) - Kernel 5.16.65-1-MANJARO(64 bit) (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.15.5 Qt Version: 5.97.0 ADDITIONAL INFORMATION These programs worked in past versions of plasma, and I've had another user on Manjaro report the same issue. The current workaround for this issue is the following. Wine: Launch application from konsole/terminal or launch the application using wineconsole rather than wine. Proton(Steam): Launch the game with "PROTON_LOG=1 %command%" I want to clarify that this is not a wine/proton issue. These applications worked fine under the same wine/proton versions in previous plasma versions. It just so happens to be affecting wine/proton applications using javascript.
> I want to clarify that this is not a wine/proton issue. These applications worked fine under the same wine/proton versions in previous plasma versions. It just so happens to be affecting wine/proton applications using javascript. That alone is not proof that it's an issue with Plasma. The error message itself doesn't indicate anything Plasma-related either Googling for the error message (https://www.google.com/search?q=Error:+EINVAL:+invalid+argument,+uv_pipe_open) brings up a lot of results, but none that suggests it is specific to Plasma either
(In reply to Nicolas Fella from comment #1) > > I want to clarify that this is not a wine/proton issue. These applications worked fine under the same wine/proton versions in previous plasma versions. It just so happens to be affecting wine/proton applications using javascript. > > That alone is not proof that it's an issue with Plasma. The error message > itself doesn't indicate anything Plasma-related either > > Googling for the error message > (https://www.google.com/search?q=Error:+EINVAL:+invalid+argument, > +uv_pipe_open) brings up a lot of results, but none that suggests it is > specific to Plasma either I can provide the full journal log from start to finish of running such an application. Perhaps it will provide some more useful information. https://pastebin.com/YehqhPER Anyways, I isolated plasma by updating only plasma. Before the update, it works, after, it does not work. The package in question would be one of the following plasma packages. " bluedevil, breeze, breeze-gtk, drkonqi, kactivitymanagerd, kde-cli-tools, kde-gtk-config, kdecoration, kdeplasma-addons, kgamma5, khotkeys, kinfocenter, kmenuedit, kscreen, kscreenlocker, ksshaskpass, ksystemstats, kwallet-pam, kwayland-integration, kwin, kwrited, layer-shell-qt, libkscreen, libksysguard, milou, oxygen, oxygen-sounds, plasma-browser-integration, plasma-desktop, plasma-disks, plasma-firewall, plasma-integration, plasma-nm, plasma-pa, plasma-sdk, plasma-systemmonitor, plasma-thunderbolt, plasma-vault, plasma-workspace, plasma-workspace-wallpapers, polkit-kde-agent, powerdevil, sddm-kcm, systemsettings, xdg-desktop-portal-kde " I'm not entirely sure which module is at fault, but I can definitely say plasma is causing the problem here. It could be a bad build on the Manjaro repo, or it could be a legit bug. I'm not 100% sure, but I know other users on Manjaro have reported this, and the same issue persists on my mom's laptop as well(Also Manjaro).
Ok. I did a little more testing. I can say that gnome3 has the same bug present in it, but xfce4 works. I will also say that this bug is present on both X11 and wayland versions of Plasma. Furthmore, drkonqi can be eliminated as a potential cause as it's not even on my other computer which is also affected by this bug.
I'm gonna update my steps to reproduce to include xfce4 as a control since it works. 1. Have an up to date plasma workspace on X11 or wayland. 2. Have an up to date wine-staging. 3. Run America's cardroom for windows(easiest option) 4. Run America's cardroom from plasma-desktop, witness bug occur. 5. Run from xfce4, witness bug not occur.
(In reply to chazzy from comment #4) > I'm gonna update my steps to reproduce to include xfce4 as a control since > it works. > > 1. Have an up to date plasma workspace on X11 or wayland. > 2. Have an up to date wine-staging. > 3. Run America's cardroom for windows(easiest option) > 4. Run America's cardroom from plasma-desktop, witness bug occur. > > 5. Run from xfce4, witness bug not occur. Step 3 is supposed to say install America's cardroom for windows, not run.
If it dies on GNOME too, that rules out anything in our code. At this point I would recommend reporting the issue to the Electron folks, since it's failing in their code.
(In reply to Nate Graham from comment #6) > If it dies on GNOME too, that rules out anything in our code. At this point > I would recommend reporting the issue to the Electron folks, since it's > failing in their code. I mean that's a fair point, except that it does still work in xfce4. Are you sure this isn't a desktop environment issue?
Yep.
(In reply to Nate Graham from comment #8) > Yep. Ok. Well I believe you, but what could be affecting it? It worked before the update, so I'm a bit confused I guess as to why it's not working anymore. Same wine version, same app version before and after the update. I only updated plasma modules as I posted earlier. Some insight would be nice is all.
(In reply to Nate Graham from comment #8) > Yep. It's been a while, and I think this should be revisited. I mean, looking at the context, how could this not be a plasma issue? the wine version didn't change, the application didn't update, it works on the xfce4 desktop environment, and the bug only occurred after updating a select number of plasma packages. It was working in past versions of plasma on the same environment. It seems to me that you dismissed this since it was present in gnome, but that could just simply mean that gnome has the same bug. Could you please shine some light onto why you don't think it's a bug within plasma? I'm not an expert, but given the context, I feel like I can only blame plasma for this.