#🖥-vesktop-development
1 messages · Page 24 of 1
yes but we don't need any dependencies
Catalina is no longer supported by Apple and Chromium officially dropped support for it now. 1.5.4 updates to the latest chromium version so as a consequence it also drops Catalina support
https://www.electronjs.org/docs/latest/breaking-changes#removed-macos-1015-support
You should really consider updating your system.
For now, you can keep using 1.5.3 or build from source and downgrade electron to v32: Run...
This is an issue with Ubuntu 24
You can work around it by running sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0. Or try some of the other solutions in this thread
There is nothing to do from our side except wait til electron-builder releases a fix and make a new release
Blame ubuntu (see how many different apps mention the below electron issue lol)
probably an issue with your system. try manually downloading the latest installer from releases and see if that works
if not, try fully reinstalling the app
well I'm pretty sure its the last os for some macs and its not really that commonly used anymore
people can just use opencore legacy patcher to upgrade their macs to newer versions anyway
Personally I wouldn't really care about support unless its for something like the vencord installer
same issue on XFCE with Xorg, also on a Intel iGPU. unsure why it is tagged as a system issue if this doesn't happen on normal discord?
because it is a system issue. the screen capture is just chrome capturer. if it has bugs, it's a you issue. there is nothing we can do. reproduce it in normal chrome and report it to them
I had this issue too, manually downloading the installer from the Github release worked.
Content
Hi, there's a problem with vesktop. I don't know what the issue is, but I have a screenshot below
you have provided zero information. try to reinstall vesktop or repair vencord
if it still happens, use our support channel for help
Discord Account
No response
Motivation
I find it frustrating that Vesktop icons are inconsistent across platforms and as well as between the app and tray. On Mac and Linux, it uses the nice and recognizable "rainbow VC" as the app icon. On Windows the app icon is the "transparent VC" icon. Additionally, on all plat...
wasnt it stated a few days ago in here to NOT mark libunity as a dependency anymore
oh
i see you uhhh #🖥-vesktop-development message

using the same icon for the tray is bad UX/design. The tray is substantially smaller than any case the app icon will be in.
once a 'proper' icon is merged/finalized discussion can be had on a simplified tray design.
@vernal lintel what's happening with the icon pr 😭😭
Same issue, Arch Linux with Hyprland, Vencord is just a white screen
I love not posting logs
I'd also like to say I have this issue, and I'm running an effectively unmodified Linux Mint Xfce installation. The only thing I could have messed up should be my graphics drivers, but the issue existed before that muck-up.
Using Vesktop without noise suppression, same as Discord, makes my microphone sound terrible to all the people I talk to. Turning on noise suppression brings it close to the original non-suppressed quality of the regular Discord client. Let me know what information I ca...
you have provided zero information. try to reinstall vesktop or repair vencord
if it still happens, use our support channel for help
I did reinstall Vesktop, but it's still the same thing
if it still happens, use our support channel for help
Better yet, rather than fully disabling this safety feature, it can be toggled only for Vesktop.
In order to do that, one only needs to create a opt.Vektop.vesktop file under /etc/apparmor.d/, include the following:
abi <abi/4.0>,
include <tunables/global>
/opt/Vesktop/vesktop flags=(default_allow) {
userns,
include if exists <local/opt.Vesktop.vesktop>
}
A reboot should apply the changes, but also running `apparmor_parser -r /etc/apparmor.d/opt.Vesktop.ves...
If you're going to add onto this thread, please also try to post logs. Press CTRL+SHIFT+i on the white screen, then click console and take a screenshot of that. Thank you!
Funnily enough, i went to double-check the logs to make sure the issue still persists, but this time they are different, no longer throwing the "Uncaught DOMException", as outlined in the original post on this issue. Anyway here they are, hope this helps somehow
Uncaught SecurityError: Failed to read the 'localStorage' property from 'Window': Access is denied for this document.
at VencordDesk...
This still doesn't address the platform inconsistency this issue raises. On Windows Vesktop does same icon is used for the app and the tray, which you indicate is bad UX/design.
Putting aside the tray issue for the moment, is there an intended reason for Windows using a different app icon from Mac and Linux?
Is there a reason this patch does not use the new Vesktop icon as the Windows app icon?
it does what 😭😭😭😭
Is there a reason this patch does not use the new Vesktop icon as the Windows app icon?
it does.
Discord Account
skeletonek
Operating System
Arch Linux
Linux Only ~ Desktop Environment
KDE Plasma 6.2
Package Type
AppImage
What happens when the bug or crash occurs?
Users on official discord client are seing weird color artifacts and a very low stream quality
Screenshot from my friend when I (on Vesktop) was streaming Serious Sam: Siberian Mayhem to him
Comparison...
Discord Account
coroa42
Motivation
I use a couple of programming and modelling related servers, where screen sharing is used to stare together at slides and vscode windows. On those servers, and for me even in general, i don't care about frame rates but always about a high resolution.
Solution
The default discord client (at least on X11) introduced a "Better Text Readability" stream quality setting that is also available without Nitro (see image below). They then use a 5 ...
same problem on OpenSUSE TUmbleweed
Discord Account
sphirye
Operating System
Fedora 41
Linux Only ~ Desktop Environment
Gnome on Wayland
Package Type
RPM
What happens when the bug or crash occurs?
It doesn't load my previous session, i have to login each time i open Vesktop.
What is the expected behaviour?
I expect Vesktop to remember my discord session and automatically login as usual.
How do you recreate this bug or crash?
- Restart or just log out from gnome WHILE having Vesktop open...
Discord Account
ryleu
Operating System
Fedora Workstation 41
Linux Only ~ Desktop Environment
Sway
Package Type
Flatpak
What happens when the bug or crash occurs?
The crash occurs when I cancel the screen picker with esc after pressing go live.
What is the expected behaviour?
It should gracefully handle not getting an output to go live from.
How do you recreate this bug or crash?
- Use sway with slurp as your screen picker
- Press the go live butt...
Discord Account
korbosoft
Operating System
Windows 7
Linux Only ~ Desktop Environment
No response
Package Type
Installer
What happens when the bug or crash occurs?
Despite Vesktop requiring Windows 10+, the installer asks for Windows 7+ instead.
What is the expected behaviour?
Vesktop's installer should probably check for Windows 10 and up, to match with Vesktop's requirements (so you can't install Vesktop on a version too old for it to even run)
How ...
of course im the one to find this issue
Same issue on Archlinux with amd GPU on hyprland. doesn't seem to be an issue with my encoding though as im able to stream to the web client, official discord linux client, and vesktop on windows just fine, only the official windows client has artifacting when receiving the stream. probably still upstream but seems to be an issue with the receiving client, not the stream itself
I also have this issue on bazzite w/ nvidia. Not sure what the repo conditions are but I'll update if I can get it happening on purpose
@Covkie What is it a duplicate of? Simply closing it is not particularly helpful. I searched through the existing issues and couldn't find one with the same problem.
Discord Account
No response
Motivation
I was hoping to type this up real quickly, So. Base chromium has features to use smooth scrolling with any app toggling the flag itself, So I was thinking maybe a toggle in vesktop itself would be possible to add.
Solution
Have electron launch with smooth scrolling enabled for the client! Or make it a toggle that turns on next launch and every launch after.
Alternatives
Just, Not add the change.
But i was really hoping to be ...
middle click scroll and smooth scrolling are two different things
duplicate of https://github.com/Vencord/Vesktop/issues/171
Discord Account
No response
Operating System
Fedora 40
Linux Only ~ Desktop Environment
Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
App just never starts
What is the expected behaviour?
Run
How do you recreate this bug or crash?
flatpak run dev.vencord.Vesktop- crash
Debug Logs
djkato@worktop ~/> flatpak run dev.vencord.Vesktop
Wayland socket is available, running natively on Wayland.
To disable, remov...
middle click scroll and smooth scrolling are two different things
duplicate of https://github.com/Vencord/Vesktop/issues/171
so it's coming natively on the next update 🤔
fair enough honestly
no. you can enable it with the command line flag
Discord Account
No response
Operating System
Linux
Linux Only ~ Desktop Environment
Sway
Package Type
pipewire wireplumber xdg-desktop-wlr xdg-desktop-portal mesa
What happens when the bug or crash occurs?
Stream is unviewable
What is the expected behaviour?
I expect discord to stream and be viewable for others.
Actual result:
Others see an infinite loading screen, or the stream is garbled mess of black and white with some visible screen elements.
O...
Also having this exact same issue, I've been having it for nearly a week now. On Arch / KDE Plasma.
Have the same issue as you but my has been closed (https://github.com/Vencord/Vesktop/issues/997)
I am having the same error in console regarding va-api drivers on my Arch Linux system (Mesa 24.3.1)
I've checked running Vesktop 1.5.4 Appimage through distrobox running Ubuntu Noble with Mesa 24.0.9 and the stream seems to be working properly there. Running natively on arch is causing the stream to be super dark for the viewers of official discord client
no. you can enable it with the command line flag
I'm on kde plasma, How do I do that?
If they plan to close this one similarly, it'd be nice to have an explanation further than marking the issue with tags and then just closing it. If it's not fixable by Vesktop and it's an issue with something else, it'd be great to know where to post an issue up about it.
Discord Account
thatgreenpie
Operating System
Windows 11
Linux Only ~ Desktop Environment
No response
Package Type
Setup.exe
What happens when the bug or crash occurs?
Everytime I turn on or restart my computer, I get logged out of discord and vesktop then requests a security key/passkey despite never having used or set one.
What is the expected behaviour?
I expect Vesktop to not log me out everytime I boot my PC
How do you recreate this bug or crash?...
omg when will NoDevtoolsWarning just be enabled by default on vesktop
Not just vesktop it can happen on the regular client too
There’s also just a few plug-ins that should be enabled by default
It shouldn't happen on a native client
but it probably does
also I want to know what plugins those are
I mean, the ones right off the top of my head is ThemeAttributes, or ForceOwnerCrown,
One of those makes sense, the other does not.
fair enough, on the second one, but I’ll stand by the first one
that's reasonable
even if it was decided it should not be marked as required, maybe a special "you should enable this" could be shown when trying to add custom CSS
Discord Account
No response
Operating System
Manjaro Linux
Linux Only ~ Desktop Environment
Gnome on Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
After I open the app, I can't resize it anymore, I can only maximize it and umaximize it with the header/title bar.
This issue appeared after updating to the latest version.
See video of the issue:
https://github.com/user-attachments/assets/a71ea32e-df23-4f55-9605-d0fb8b37b056
#...
Getting the same error and it seems to not matter whether the reciever is using Vesktop or the official Discord client (on Windows too). I'm using Vesktop on Linux and whenever I try screensharing it infinitely loads for the reciever. And like you explained in the repro steps I asked her to disable hardware acceleration and after that she could view the stream.
If it's not fixable by Vesktop and it's an issue with something else, it'd be great to know where to post an issue up about it.
I don't know. It could be Chromium, Electron, Discord, your system, etc
It works flawlessly for me (rpm package on Fedora + Gnome (Wayland)) so it's definitely an issue specific to your systems
this is like the 10th duplicate. Please search existing issues
vesktop xdg portals when
@grizzled hemlock make it happen
i hate gtk file picker so mmuch
electron went insane and bumped to an unreleased portal version (v4)
34 has that change reverted
but 34 is still in beta sooo
fix
build your vesktop on 34 beta bwaa
true
Narrowing it down further it seems to be an issue with Vesktop and X11. Since that's what I use. I switched to another discord client and screensharing worked just fine there.
I'm using wayland and the issue is present there so it's not only X11
I'm wondering if this is connected to the mesa driver / va-api version.
Arch
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 24.3.1-arch1.3 for AMD Radeon RX 6600 (radeonsi, navi23, LLVM 18.1.8, DRM 3.59, 6.12.4-arch1-1)
Ubuntu Noble via Distrobox
vainfo: VA-API version: 1.20 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 24.0.9-0ubuntu0.3 for AMD...
Interesting observation though the 2.22.0 version of libva was released back in July and this issue didn't start until a few days ago for me. (should note that i also use Arch which does line up with the issue being persistent on mostly Arch systems). Either way like I said I tried a different discord client (GoofCord) and screensharing seemed to work fine so maybe that's a clue. Could do more poking around tomorrow with different scenarios if no one has any more clues by then
The issue should be fixed in Vesktop version 1.5.4 with
libunitypackage installed.
I am not seeing the fix from Linux Mint.
@yllekz I don't know the specifics of that package, but I think it only works with the (now deprecated) Unity desktop environment and KDE Plasma.
https://repology.org/project/libunity/information says "Library for integrating with Unity and Plasma".
Linux Mint uses Cinnamon, which is based on GNOME, so it probably doesn't work there.
I don't know if it works on upstream GNOME with libunity installed.
does libunity work on normal GNOME?
yes gnome has badges
🤔
if it works on normal GNOME, it should also work on Linux Mint
weird
oh
they are using the flatpak version
hmm
probably libunity needs to exist inside the freekdestop platform libraries?
the flatpak would need the correct dbus points enabled for it
@yllekz It seems libunity needs to be present in the Flatpak build itself, so it doesn't pull from the system. That's probably why you are not seeing the unread badges.
libunity doesnt need to be in the flatpak
to fix the issue the flatpak manifest would have to be changed
just the dbus points
"--talk-name=com.canonical.AppMenu.Registrar",
"--talk-name=com.canonical.indicator.application",
"--talk-name=com.canonical.Unity",
hmm, are you sure about that?
yes
test it before you pr
sure
we can add the libunity paackage to the flatpak so we guarantee that
yes, there isn't
but we can download the .tar.gz file and extract it
see https://github.com/flathub/org.gnome.Geary/pull/14/files for an example
that is an insane thing to do for system badges
the proper solution is to emit the dbus signal
yep I know that
Electron team = 💤
I will only have a look at the permissions
so it satisfies for now
or just have vee do #686
change of plans, discord won't allow me to create an alt account to test it
so I'll let the flatpak explode
If it's not fixable by Vesktop and it's an issue with something else, it'd be great to know where to post an issue up about it.
I don't know. It could be Chromium, Electron, Discord, your system, etc
It works flawlessly for me (rpm package on Fedora + Gnome (Wayland)) so it's definitely an issue specific to your systems
This is understandable. Thanks for the clarification nonetheless. My only guess is it's VA-API related since that's the error we're seeing popup. But yeah...
It is not just happening on there systems I'm also getting it on fully up to date CachyOS system which is (Arch) based
From what I checked VaapiVideoEncoder doesn't seem to work when checking chrome://gpu, it keeps saying Video Encode: Software only. Hardware acceleration disabled. But if you use AcceleratedVideoEncoder it does say Video Encode: Hardware accelerated.
I tried verifying if this actually does something, and when using nvtop it does show activity on the ENC section when using AcceleratedVideoEncoder but it doesn't when using VaapiVideoEncoder.
For debugging purposes I leave my...
I want to also specify that I wasn't able to make --enable-features work on Vesktop, I'm not even sure that they are passed to Chromium.
But the feature I suggest to use does work when using Discord Web on Chromium
AcceleratedVideoEncoder is a flag change in chromium 131
electron 33 is chromium 130
they are insane
i did not check, my problem is that currently Vesktop for me is not hardware accelerated on encoding
but chromium is
do you have hardware accel enabled in vesktop settings
Yes
btw where is this stuff documented, may i know?
for me chromium flags are a black box, its much more easy to find firefox stuff than chromium on stuff about linux
The 'Vaapi' -> 'Accelerated' flag change is for a later version of chromium than electron33 currently runs. This change will need to be made when we bump to 34 or later.
is someone actually watching your stream
Yeah they were
I can make a recording, but sadly this is no longer development but support
we can move if u want
just play with the flags passed to vesktop.
no sorry i dont really have the time rn to deal with chromium flag shit
i agree its a pain
the least of chromium's priorities are linux support
i have a question, is it possible to open a new webview on vesktop to chrome://gpu? I tried location.href but it didnt like it and it crashed 
its much better than debugging with streams
I'm like 90% sure those pages are disabled in electron
funnily enough, they are not apparently
well it says hardware acceleration is working 
yup
so i guess its a me issue or an older chromium issue
u said it was 130, right?
(well it says right there)
130 is relatively new
i agree
there is still a chance that its an issue with my setup but why does it work on chromium then 
what flags did you pass to raw chromium
its 131 and i only did chromium --enable-features=AcceleratedVideoEncoder
$ chromium --version Chromium 131.0.6778.85
Fun
my only reason for cam recording was to not make the enc on nvtop show lol
i also had to use multi pc setup as decoding shows as ENC also 
seems as though the vast majority of people experiencing this use Arch Linux. like Łukasz said, it might be related to a regression in the new version of some driver
You could also try downgrading Vesktop to 1.5.3 and 1.5.2 to see if it was a regression in electron / chromium. Both of those releases upgraded the major version of electron. Do not go lower than those versions...
yeah this works fine
i was thinking about adding some sort of developer tools to vesktop to open those windows
they didnt change the other two flags
ERROR:vaapi_video_decoder.cc(1225)] failed Initialize()ing the frame pool is a very common log from chromium/electron on linux and verrry likely has nothing to do with this.
I am on latest arch kde plasma and can stream from vesktop just fine. Maybe others need to play around with flags like --disable-gpu-driver-bug-workarounds or --ignore-gpu-blocklist
can do, do i use the simple one or the zero copy one?
idk if the zero copy one fallbacks to simple on x11 environments or if it breaks stuff
sounds useful ngl
please do
actually this seems like the kind of thing that could be done relatively easily
seems as though the vast majority of people experiencing this use Arch Linux. like Łukasz said, it might be related to a regression in the new version of some driver
You could also try downgrading Vesktop to 1.5.3 and 1.5.2 to see if it was a regression in electron / chromium. Both of those releases upgraded the major version of electron. Do not go lower than those ve...
yes
where should the entry point(s) be?
then it's an electron / chromium regression. you should try creating a minimal electron reproduction app and report it to electron
vesktop settings?
about window?
window menu?
tray icon menu?
Discord Account
No response
Operating System
Fedora Linux 41 (Workstation Edition)
Linux Only ~ Desktop Environment
Gnome on Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
The crash occurs when starting Vesktop
What is the expected behaviour?
Should start Vesktop
How do you recreate this bug or crash?
See this issue also: https://github.com/flathub/dev.vencord.Vesktop/issues/40
- OS Name: Fedora Linux 41 (Workstation Editi...
Vanilla discord client is also not sandboxed btw
it's likely impossible for discord to enable sandboxing for their renderer.
@Vendicated on what platform the rendered is 100% confirmed to be sandboxed (i.e. running without --no-sandbox flag)?
Appimage? Debian? Fedora? aur?
I can confirm that it was really due to the system configuration. More precisely, the integrated GPU. My CPU (i7-12700k) contains a graphics unit...
This led to this error. The error message was somewhat misleading.
Specifically, I had to change the following in the UEFI at MSI:
Disable IGD Multi-Monitor!
 {
let diff = performance.now() - last;
if (diff < 40) {
console.log("<40ms since last frame");
} else {
let date = new Date();
console.log(diff + "ms since last frame at " + date.toLocaleString("en-US"));
}
last = performance.now();
if (measure) {
window.requestAnimationFr...
system issue. try to disable hardware acceleration. nothing vesktop can fix
I am not too sure about the system issue part. As I said, I am able to reproduce this on 3 different OSes, 2 of which are fresh installs, even using different desktops.
However, I am on your side that it may not have anything to do with Vesktop. I'll open issues on the electron and arRPC repos.
Thanks and happy holidays!
do you have any discord themes / css? if yes, disable them and see if it's fixed
before reporting it anywhere, you should first see if you can reproduce this issue in normal chrome browser visiting discord.com/app
if yes, it's most likely something wrong with your system. you could file an issue in the chromium repo, but I don't really know anyone who has similar issues so it's likely not on their side
its probably not arrpc. if you want to check, you can disable rich presence in ves...
Thanks for the recommendations. As stated in my post above, I have already tried that, and yes, it does make a difference. It's arrpc. At this point, it's out of question that it's arrpc-related. And thus, it is not reproducable by just visiting discord.com/app.
I can try out using aarpc externally and disabling Vesktop's internal arrpc. This way, I could find out if it's arrpc or Vesktop's integration of arrpc.
Discord Account
No response
Operating System
Arch Linux
Linux Only ~ Desktop Environment
KDE Plasma 6.2.4 Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
Vesktop shows a GTK file picker (restricted to the Flatpak sandbox) instead of an XDG Portal file picker.
I believe this is not a system issue because other Flatpak programs show the correct file picker, as do non-Flatpak programs configured to use the portal. Downgrading Vesktop to t...
@vernal lintel i might be able to do this myself, (depending if "wontfix" means "i will not fix" or "will not ever be fixed")
installer.nsh:
!macro preInit
SetRegView 64
WriteRegExpandStr HKLM "${INSTALL_REGISTRY_KEY}" InstallLocation "$LocalAppData\vesktop"
WriteRegExpandStr HKCU "${INSTALL_REGISTRY_KEY}" InstallLocation "$LocalAppData\vesktop"
SetRegView 32
WriteRegExpandStr HKLM "${INSTALL_REGISTRY_KEY}" InstallLocation "$LocalAppData\vesktop"
WriteRegExpandStr HKCU "${INSTALL_REGISTRY_KEY}" InstallLocation "$LocalAppData\vesktop"
!macroend
electron regression. Will be fixed whenever there's a new electron version and we upgrade to it
it's irrelevant
no one should be using windows 7 anymore
it's not supported
Adds a few lines to installer.nsh to check for at least Windows 10. fixes #1001. nin0 said I should PR anyways
im not adding support for it
im making it more clear it doesn't support it
probably a bad idea
some people patch their win7 to support new chromium
idk if it would make them unable to install it
probably would
it's fine in its current state
if anything we could just add a note to the readme
usually those people also use a program to spoof their version
just have soft warning then?
or nothing at all
I can confirm the problem with Ubuntu 24.04 and Flatpack installation
will this work ??
const { ipcRenderer } = require('electron');
// When the stream starts
function onStreamStart() {
ipcRenderer.invoke('stream-started').then((id) => {
console.log('Stream started. Power saver blocker active.');
});
}
// When the stream stops
function onStreamStop() {
ipcRenderer.invoke('stream-stopped').then(() => {
console.log('Stream stopped. Power saver blocker deactivated.');
});
}
// Example usage with a video element
const videoElem...
maybe
does this not work with args? for example jumping to a message or opening invites
if not then it's possible to achieve the same thing using registry keys on windows and some commands on linux (and the args are not working for me)
what is this ai slop
once again someone is thinking this is implemented for existing sessions
This is NOT for an existing instance. At most it focuses the window like youre experiencing. This is for launching Vesktop from a closed state (not to tray!!!). Discord desktop had this identical behaviour.
arRPC handles existing instances via websockets. I'm assuming you have arrpc disabled since vesktop is not handling invites like you implied. I guess because of that case existing session support can be implemented?
@vernal lintel what do you think
there are deeplinks that allow you to jump to a message that work on the normal discord app, but since arguments don't seem to be supported here they wont work
i think they look something like this: discord://-/channels/<server-id>/<channel-id>/<message-id>
did guy not understand what I said
I think this is a pretty good PR, not sure why this isn't merged honestly 🤷♂️
so what do I do? I can't resize Vesktop from any source I install it from, both flatpak and aur packages have this issue
Discord Account
.syrent
Operating System
6.12.4-arch1-1
Linux Only ~ Desktop Environment
Hyprland on Wayland
Package Type
installed from aur
What happens when the bug or crash occurs?
vesktop was working fine until i updated some packages. the day after that my friends couldn't see my screenshare anymore. after some troubleshooting, i noticed if i start the screenshare in Prefer Clarity type the screenshare does load, but it takes about 5 minutes to appear. and if...
This doesn't seem to be specific to hyprland, I can reproduce this issue on KDE Plasma and Gnome as well. Both X11 and Wayland.
This doesn't seem to be specific to hyprland, I can reproduce this issue on KDE Plasma and Gnome as well. Both X11 and Wayland.
edit: I'm also on Arch, and only noticed this after doing a system wide upgrade about a week ago, perhaps that is the culprit?
I was having the same problem until i switched to the flatpak version. In a different issue someone said downgrading Vesktop to 1.5.3 also worked. I'm on EndeavourOS + KDE btw, if that helps.
^ something else to note about screenshares, ppl have been reporting to me at least, that my screenshares often like to "corrupt" or just have all of the colors get really messed up
sometimes the colors show negatives, sometimes it's nearly all black, etc.
This is either an issue with your system or a regression in electron. Try building from source and switching to electron 32 by running pnpm i electron@32 after the pnpm i call
If that fixes it, you should report it to electron instead. You will have to create a minimal electron reproduction example for that, see the instructions in their issue template for more info
^ same thing applies
o 
jus wanted to make sure incase it was something i didnt know was a known problem or anything :3
ty :D
Thanks a lot for the feedback and guidance. Tried both, unfortunately neither seemed to solve the issue for me. It's quite awkward because it seems to work eventually, it just takes several minutes for it to show up.
Would I be correct in assuming this is most likely a driver issue on my end?
well your console output has a lot of errors that probably aren't normal. I would suggest googling them and maybe you'll find something relevant!
I googled Failed to record frame: Error creating EGLImage - EGL_BAD_MATCH and found a hyprland issue so maybe it's an issue with that for you? Perhaps try running a different WM/DE to see if it works normally there
it really sucks that the majority of issues are something in electron we can't do anything about
I love having to tell people I have no clue how to fix it ten times a day
it's so much nicer if it's actually something in your codebase so you can actually fix it / tell people how to fix it instead of being as clueless as they are
i suspect most of these issues aren't even electron itself and are chromium issues 
maybe
but reporting bugs to chromium is insane
they have such a weird bug tracker
so i tell people to report it to electron cause then it's electron's problem and not our problem 
idk why google thinks people want to use a google account for that
i’ve tested other programs like OBS, and they seem to work fine. However, when someone tries to watch my screenshare, it takes a few minutes for the stream to appear. if they close and reopen the screenshare, the delay happens again. it’s as if something on their end is preventing them from viewing the stream properly.
initially i thought it was an issue on their side, but i’ve tried it with multiple people, and they all experience the same problem.
not sure if this is helpful, but they a...
i love seeing this being shared around half a year after it was made
happened to a friend of mine on current latest bazzite, from the discover package manager
Discord Account
No response
Operating System
Arch 6.12.4-arch1-1
Linux Only ~ Desktop Environment
Gnome on Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
These bugs only seem to occur when the Vencord setting "Disable the window frame" is off (Default) and using the system window frame. I believe it only started happening within the last few days.
- Can no longer use mouse dragging at window edges to resize the window. The mouse c...
@4A8 can you explain in detail what about this PR isn't working as expected and how youre testing it. Executing vesktop [#announcements message](/guild/1015060230222131221/channel/1024351821873037462/) works just fine for me and opens vesktop on the channel with its message highlighted.
y u p
I mostly even brought up the streaming issues because I was hoping it was something I could fix but NOPE. 
I'm trying to downgrade, but the AppImage seems to be forcing the latest version when I run it. I do not have auto-update enabled in my settings.
Discord Account
lucasdaweb95
Operating System
manjaro 24
Linux Only ~ Desktop Environment
kde on x11
Package Type
flatpak
What happens when the bug or crash occurs?
the app uses my cpu for the encoding as oposed to my gpu via nvenc.
What is the expected behaviour?
for it to use my gpu for video encoding
How do you recreate this bug or crash?
stream a game
Debug Logs
[3:1...
Update: I’m not sure how, but the original issue seems to be resolved now. However, I noticed that the screen preview inside the share menu is much smaller than the blue frame around it, as you can see in the screenshot. It would be great if the preview could be properly scaled to fit the blue border
basically, doing exactly what you just did simply opens the vesktop window and does not highlight anything, i even tried with a link of my own
Okay, I ended up successfully downgrading to 1.5.2, but the issue persisted for me.
I spent a lot of time trying to solve this issue and tested many solutions, but nothing worked until now. To save others some time, here's a list of what I tried:
- Downgrading the system's Electron from version 33 to 32 – no luck.
- Building Vesktop from source with Electron 32 – still didn't work.
- Tried every possible combination of
xdg-desktop-portal– none of them helped. - Switching Vesktop to Canary or PTB – also failed.
- Downgrading PipeWire to 1.2.4 – no impro...
Discord Account
hypeedev
Operating System
Arch Linux
Linux Only ~ Desktop Environment
Hyprland, Wayland
Package Type
AppImage 1.5.4
What happens when the bug or crash occurs?
The application gets stuck at the "Loading Vesktop..." screen. This occurs only if the module format in $HOME/package.json is set to "module", regardless of whether the app is launched through the app launcher or the terminal.
What is the expected behaviour?
The application starts nor...
I was going to add that my appimage kept updating too. Trying to downgrade the Flatpak also didn't work either. Doesn't seem too easy to downgrade.
This implements deep links from web so message links and the like work over just invites work.
Depends on OpenAsar/arrpc/pull/128
I noticed we didn't implement this after double checking what I said in a #813 comment
don't create that file it screws up all nodejs scripts in your entire home directory
Apologies for that screwup. I thought I was just going to quickly file a bug so it wouldn't be a problem that my hands are injured, then I screwed up and needed to re-file, the new github templates are all segmented which means I can't just copypaste the whole thing, and then there was another bug, and I had to re-file that too, it all just turned out to be a way bigger job than I had estimated, and I knew I had to throw in the towel when my right-click finger popped out of its socket :D "I'l...
when my right click finger popped out of its socket
what 😭
also omg why didnt they just use voice input haha
instead as the audio share is made mono on discords server side anyways
does this occur on stock desktop client
No, they use a windows only native module for sharing which also handles audio
With pipewire screen capture we could try and make a replacement module for it
I'm a little sparse on time lately but I might find the time to make such a module eventually
they added native audio to the linux app
recently
linux app now has working audio + wayland support
Ah nice, does that audio also get mixed down to mono?
idk
i didnt try
probably doesnt
considering their desktop app uses the udp protocol which doesnt have the downmixing
I'd reckon if they don't use a native module but the chromium thingy
i dont think they do? how would they support audio
If they use a native module we could include it in vesktop
Or I can figure out how it works an make Venmic work with that
naaaah we can't lol
copyright infringement
Make the user copy it :P
unless you wanna like make people install discord and load it from their files
but that's insane 😭
Then this would be the way to go I guess?
If I find the time to look at it I can check how their module works and just pump venmic audio through it
well we would have to use their udp protocol
it's quite complex
and has encryption too
people have been working on remakes
in c++ and rust
it definitely wouldn't be worth it to remake imo cause at that point you should just use the normal app
Aids
but if you want a fun project sure xD
Yeah fair point
Def worth a shot and would be interested but I'll have to finish some other things first xd
Will keep it on my to-dos though
so what do I do? I can't resize Vesktop from any source I install it from, both flatpak and aur packages have this issue
They won't bother replying... I have the same issue for more than a week but hey they'll keep closing issues without proper solutions like always... and flag as duplicate any other.
Good luck that's all... Maybe if discord gets less annoying I'll move back to the official client. I use Vesktop only cause it had better Linux support but seems that it will not be the ...
I don't have a solution. It's your system, not mine. Rendering and window management are done by Electron / Chromium and resizing itself is done by your window manager. Vesktop has 0 control over any of this behaviour. I have no clue what is wrong or how to fix it
I really don't know what you expect me to do. Yes, i will keep closing system / upstream issues like this without comment because I simply do not have anything to comment. I know as little as you, do your own research. Look it up...
You could have used that time you spent typing that unnecessary comment googling your issue instead. Seriously quit being so entitled and cocky
https://bbs.archlinux.org/viewtopic.php?id=300635
https://github.com/electron/electron/issues/44543
LMAO
so what do I do? I can't resize Vesktop from any source I install it from, both flatpak and aur packages have this issue
They won't bother replying... I have the same issue for more than a week but hey they'll keep closing issues without proper solutions like always... and flag as duplicate any other.
Good luck that's all... Maybe if discord gets less annoying I'll move back to the official client. I use Vesktop only cause it had better Linux support but seems that it will n...
the worms in my head making me type a billion words of complaint instead of 4 words into google.com and clicking the top result
You could have used that time you spent typing that unnecessary comment googling your issue instead. Seriously quit being so entitled and cocky
You know me and him as average users and not developers, we use your app, we see that something is broken in your app and we report the issue, but since we don't know the specifics of what's going on because we are not developers, since we saw the issue on your app we report it the github of your app, it's that simple.
Instead of closing issue...
tbf what keeps me using vesktop is that it has a less deranged dev experience
“i can’t read!”
nevermind it still doesnt pickup nvenc after enabling hardware settings and drivers properly
awesome work, was looking for this, any progress on this
this still doesn't work.. it still only switches to the window when i open a discord:// link that is supposed to jump to a message, but when i open a message link in the browser and then press open in discord it doesnt do anything
You obviously misunderstand how to test this PR and the URI one.
Firstly this PR has nothing to do with the uri discord:// so I'm confused as to why youre attempting it here. It will NOT do ANYTHING when running a build from this branch.
Secondly pressing open in web will not do anything if you didnt build and run from this branch. I will not be providing support for such things as youre expected to be able to do so yourself when testing in development features.
look at this idiot yapping
Same deal here
I'm running Linux Mint 22 x86_64 with Cinnamon 6.2.9
Performance tanks greatly when streaming except in games i run in 300+ fps or so (like TF2), and even so they fall to like 200fps. Not a thing that happened in windows. I highly suspect it's the CPU usage.
Update the patch for OpenAsar/arrpc/pull/130
Discord Account
No response
Motivation
I like everything in an app's UI to be just so, especially if I use the app for hours every day. Discord's official zoom levels are satisfying to me in terms of the list of servers fitting neatly in the available space, such that there are no partial server icons. Discord does this by defining zoom levels. Vesktop doesn't have the zoom levels defined in the settings UI or internally. So when you zoom in or out, it appears to go by 10% every ...
Any Response?
@Vendicated
Read the issue I linked and you will know
this wouldn't be too hard to implement would it
This code is really bad, so I expect many change request. However its working fine.
This adds a zoom slider to the Vesktop settings page as well as rebinds ctrl+/- to use these zoom controls instea...

i still don't get why vesktop wants to reimplement a lot of discord settings in its own page though
i think i tried to port some of them to stock settings locations at one point
less patches that might break
good point
Discord Account
shithad
Operating System
Windows 10
Linux Only ~ Desktop Environment
No response
Package Type
Setup exe
What happens when the bug or crash occurs?
Loading Vesktop just gives a box with a white screen. There is no tray icon either. Have tried restarting PC and reinstalling Vesktop.
What is the expected behaviour?
For Vesktop to load and open to my ho...
I can't open Vesktop for logs at all since it just gives the white box
I spent a lot of time trying to solve this issue and tested many solutions, but nothing worked until now. To save others some time, here's a list of what I tried:
- Downgrading the system's Electron from version 33 to 32 – no luck.
- Building Vesktop from source with Electron 32 – still didn't work.
- Tried every possible combination of
xdg-desktop-portal– none of them helped.- Switching Vesktop to Canary or PTB – also failed.
- Downgrading PipeWire to 1.2.4 – no...
Same deal here I'm running Linux Mint 22 x86_64 with Cinnamon 6.2.9 Performance tanks greatly when streaming except in games i run in 300+ fps or so (like TF2), and even so they fall to like 200fps. Not a thing that happened in windows. I highly suspect it's the CPU usage.
my pcs older so it suffers even more when streaming tf2 has constants stutters
Discord Account
wxagames
Operating System
Nobara 40
Linux Only ~ Desktop Environment
Plasma on Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
When Vesktop starts, it defaults to my primary screen, even though I've moved it to my other monitor. This was not an issue with vanilla Discord, BetterDiscord or Vencord.
What is the expected behaviour?
I expect Vesktop to boot on the same monitor it was closed on.
How do you recreate thi...
electron on wayland issue. launch with XWayland instead of Wayland and it will work fine
What a convenience lol. Was gonna ask if I could PR a good temporary fix for this. Could still do it if it is wanted but not required/needed
whats the fix
isnt the problerm that wayland doesnt give u control
Oh didnt think about that
Seems like that's the case. Seems like the only thing that can rly be done is request full screening on a specific screen
I mean a temporary somewhat of a fix could be just place it in full screen on the monitor it was closed at the last time
with this merged https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264 you can spawn a full screen invisible window the spawn relative to that :ppp
horrible??
How so?
forcing spawning as full screen is terrible
you want it spawned in a specific location not full screen
If the user had it closed as fullscreen on my second monitor I would want it to start it as that. So was thinking of it more as "if the user has specified as fullscreen"
that already works?
eww gitlab
yeah thats how wayland works
you can't request the monitor
use a window rule for that
https://github.com/libsdl-org/SDL/issues/7197#issuecomment-1409707012 found this comment left on SDL though
I am guessing display and monitor is the same
Only problem is I can't find any api references for this in the Wayland API
oh interesting
mpv --player-operation-mode=pseudo-gui --fs --fs-screen=2
works
so ig it is a thing?
That could be used for a solution to have it be on a specific monitor on start up
If the API for it can be figured out lol
I'll do it tomorrow
The second more scuffed solution is using like a xdotool for Wayland and run some stuff that does keyboard shortcuts to fullscreen it on the right screen if it can't be figured out how other does it
despair
Scuffed for a reason
leave it for electron to figure out 😭
I have 0 patience :trol:
the 5 first results on Google: is broken on KDE, great
I'll check tomorrow and see it. Never heard it before
Otherwise I'll do a PR or maintain a fork until electron has figured it out 👍
or just run xwayland 💀
No fun with that /hj
actually just a wayland issue because wayland doesn't let windows control their own position. thus not sure if this will ever be fixed upstream
@vernal lintel it's a Wayland issue in the way that is "Wayland is not made this way"
Wayland was made for windows to only be able to interact with anything inside of itself and nothing outside of itself. So according to a lot of people this will never be resolved as Wayland was simply not made for it or smth along those lines
So you can probably p confidentially say it will not be fixed upstream cause it just isn't wayland (tho don't take my words for this)
.
vesktop maintaining its own electron fork when
vesktopOS
Can confirm that this issue is occurring (in some form) on Arch with both Hyprland and Xfce (X11), with the aur packages vesktop-bin, vesktop-electron, and the flatpak package.
It seems to manifest as streams taking ages to load for viewers (but thumbnails load with no problem?), and when they do load they are usually just a black screen, or have very strange colours (example below).
Discord Account
ryzm
Operating System
Macos 15.2
Linux Only ~ Desktop Environment
No response
Package Type
DMG
What happens when the bug or crash occurs?
What is the expected behaviour?
It Should just open like normal.
How do you recreate this bug or crash?
I dont really know i just downloaded it and then it wont load so i checked t...
delete ~/package.json
actually just a wayland issue because wayland doesn't let windows control their own position. thus not sure if this will ever be fixed upstream
Doesn't seem like it though, since the aforementioned versions worked perfectly fine, so shouldn't be a problem from Wayland or Electron.
launch with XWayland instead of Wayland and it will work fine
I'm on Linux but I've got the same issue. I've removed all three flags but still no luck. There aren't any logs in the console or anything.
i mean in the past week i've considered adding a plugin to vencord to show my public transport card balance as a joke
Hey, I've also built with this since my notification badge doesn't work without this PR. I've also ran into @RealSweetPanda's problem (and I'm on Plasma), in which one of my dbus-broker processes reaches its max file descriptor limit (1024) then it crashes and so does everything on my pc. It seems every single call to dbus.sessionBus() opens a connection that's never closed.
I think I managed to fix it on my machine (didn't test for too long, but seems to work and not leave too many conn...
Discord Account
No response
Operating System
Arch
Linux Only ~ Desktop Environment
hyprland
Package Type
Flatpak/and i tried yay
What happens when the bug or crash occurs?
when i press on share screen button
What is the expected behaviour?
.
How do you recreate this bug or crash?
- open vesktop 2.join voice chat 3.press on "Share Your Screen" 4.crash
Debug Logs
➜ ~ flatpak run dev.vencord.Vesktop
Using NVIDIA on Wayland,...
This is an issue with your system, not Vesktop! Your system seems to have broken portals. I advise googling some of the error messages and I'm sure you'll find solutions
This is an issue with your system, not Vesktop! Your system seems to have broken portals. I advise googling some of the error messages and I'm sure you'll find solutions
Thank you so much! helping me find the problem
I just installed xdg-desktop-portal-hyprland
It works well now :3
why is that not a dependency of hyprland 
it should be?
insanity thats why
its not even optional
lmao
Discord Account
No response
Operating System
Windows 11
Linux Only ~ Desktop Environment
No response
Package Type
exe
What happens when the bug or crash occurs?
no crash, but around 2-3 weeks i have the issue - No one input output devices detecked by the app
sometimes i just wait for some time (devices are randomly detected)
tried official app, there is fine
tried reinstall app completely, reset all settings, nothing work

If you're curious how I went about checking, I got the pid of the main vesktop process pgrep vestkop -a (or electron), then checked the pid of every dbus-broker pgrep dbus-broker for vesktop opened files sudo lsof -p <pid_dbus> | grep <pid_vesktop>. And when I found the one that has opened files I message my discord account to trigger a notification badge update and che...
vestkop
Please merge this. I can't open vesktop in public places until this gets merged.
Please merge this. I can't open vesktop in public places until this gets merged.
just use equibop
because the PR author still hasnt tested
im not going to keep chasing them up, i asked for a test status and if they havent given a result i cant do anything with it
i will chase them up one last time because im aware this is wanted but if i get no response i cant merge it
Has this been Flatpak tested?
@ading2210 I still need an update on this. This isn't mergeable if it doesn't work in Flatpak.
Please merge this. I can't open vesktop in public places until this gets merged.
it's a dancing pixelated anime girl, you're acting like it's nsfw
I wonder if it would be possible to change it with the option that applies themes to that window
no
only thing this does is take background color and save it
the theme itself isn’t really applied
instead of all that bloat in that pr just have it pull from a css var a URL or file path then load that 
dev is malding rn and hiding comments he doesnt like
im glad equibop is an alternative, i refuse to use vesktop for this reason. juvenile dev
for transparency i have blocked them for 1 day from the org, many people receive emails for these comments and posting them is useless. they're being hidden because they add nothing to the PR, and the promotion of a fork is not productive. this isn't about being juvenile or hiding things that we don't like, this is us trying to actually work, and we're still waiting for the PR author to confirm things. behave yourselves.
you are free to use equibop or any other forks of vencord/vesktop, but please stop bringing them up here and promoting them because we, the developers of the base software, cannot support it
1 day 
you wanna bump it up?
yes. i blocked them permanently
ah
why are you being nice to trolls and assholes lol
it's obvious they're just here to be a cunt and never gonna contribute anything productive
fair enough
you are an idiot!
quoting equicord’s own rules channel:
Vanilla client supports sharing screen in 4k.
and thats the one rule we heavily inforce and follow because of stuff like this
it makes me mad because no matter how much we say and try to drill it into their heads they still do stuff like this
Discord Account
mazeymoos0022
Operating System
Windows 11
Linux Only ~ Desktop Environment
No response
Package Type
Setup EXE (Installer)
What happens when the bug or crash occurs?
Title explains it all, I click the app, not opening. Just get this white box. Using version 1.5.4 (latest). Tried reinstalling and also restarting my machine... Still no luck. Been working fine on v1.5.3

- something broke with screenshare (probably chromium if not probably venmic issue instead)
- i dont like rainbow icon (and it's always because it's rainbow and not because of an actual complaint in which case just edit the desktop file)
Nevermind Uppdating Vesktop via the devtools console resolved the issue
Can you tell me how to do this via devtools console?
vee should merge all prs with no review so actual bug reports are made
Discord Account
No response
Operating System
Arch Linux
Linux Only ~ Desktop Environment
KDE on Wayland
Package Type
AppImage (official) and RPM (from AUR)
What happens when the bug or crash occurs?
When screensharing, the CPU usage of electron increases during the stream
It takes like 8h for me to reach 100% CPU usage but it does exist.
I suspect this to be an electron upstream issue but I can't be sure.
I have an AMD 7800XT and this happens with or with...
This is most likely indeed an electron or even chromium issue. I don't think there is much we can do unfortunately :(
I advise you to try to reproduce this in Chrome (visit discord.com/app in chrome) and electron (this is gonna be a bit hard especially if you're not a programmer) and then report it to the one that's at fault
Thank you for your advice, I will do that!
And thank you for developing Vesktop :rocket:
fixed it anyway. it didn't like my pipewire default.clock.rate being higher than 48000
@demanuPL According to Issue #669 : In the Developer Console (Ctrl+Shift+I), type
await Vencord.Updater.checkForUpdates()
await Vencord.Updater.update()
VesktopNative.app.relaunch()
@upper pine is this expected?
awesome, glad you figured it out! will investigate further
48000 is the default for pipewire so prob some bad assumption in a library somewhere

I don't make any assumptions just links, meaning that if the clock rate is different and it doesn't work it's discords / the applications fault
I can't know what sample rate other programs have so I also can't downsample it to the expected rate
Just a bad idea to change the sample rate if you don't know that the applications on your systems can handle it
hmm
Can't confirm that
Used flatpak version
Experiencing the same issue, Bazzite / KDE / Wayland / NVIDIA. Running games in windowed mode does work, but neither of the potential solutions given by @benjamin051000 had any effect.
Supposedly the log output will be fixed once Chromium 131 hits Electron (currently using Electron 33 / Chromium 130), though I don't know if that will fix this issue.
@winstxnhdw using flatpack version, starting discord with this works:
flatpak run dev.vencord.Vesktop --proxy-server=socks5://192.168.0.1:39441
i suggest reopening this issue.
despite the region being set to automatic i still have the exact same issue with vesktop, this doesn't happen with any other client not the web client
Discord Account
lis314
Motivation
Currently you can pass --proxy-server=\ to tell electron to use socks5/http proxy on linux, however this breaks WebRTC, preventing you from joining any voice channels. This prevents using discord in countries where it's blocked, for example Russia.
Solution
There are implementations of passing WebRTC through proxy for windows client of Discord (Pascal/c++, [c++](https://github.com/runetfreedom/disc...
i suggest reopening this issue. despite the region being set to automatic i still have the exact same issue with vesktop, this doesn't happen with any other client not the web client
I have exactly the same issue, this seems to be set to US for me at any given time somehow. Changing my region settings in DM calls fix it, but on servers I cannot do anything.
like i stated previously, this is not a vesktop issue. this behaviour is controlled completely by discord (web) and not affected by vesktop in any way
Experiencing the same problem, flags do nothing. Could we get a fix/change so the flags do sth without changing the source code?
hop on irc
hop on nin0chat
nin0chat has terrible uptime I'm selling all my stock in nin0corp
Related issue: #997 , and yes indeed it does happen. Usually after we turned on screen sharing / camera. In my case, sometimes it have some sort of "black" overlay and sometimes the entire camera/screenshare have a "green" overlay on them
Arch, KDE Wayland
I just had this issue after restarting my PC from a crash. The only logs I could find were in %appdata%/vesktop/sessionData/Session Storage. The 000003.log file contained this:
namespace-©&f
And the LOG file contained this:
2024/12/31-11:28:57.897 2134 Reusing MANIFEST C:\Users\Kamil\AppData\Roaming\vesktop\sessionData\Session Storage/MANIFEST-000001
That's it. I renamed the "vesktop" folder to "_vesktop", relaunched Ves...
Also have this issue in Arch Linux with Hyprland and KDE Plasma.
Went back to commit b09f035 , built with electron 32, now works as intended.
i hate how every new electron version not only improves 5 things but also adds 3 more bugs and linux issues 😭
Hi. Does the discord's game sdk's RPC work for you on Vesktop linux?
Upon starting my program on linux, which works on macos with vesktop just fine, it says that f.kio.core: "/var/home/neo/.local/share/flatpak/exports/share/applications/com.discordapp.Discord.desktop" contains supported protocols but doesn't use %u or %U in its Exec line! This is inconsistent.
it works with the official discord client opened, but does not with vesktop.
It was mentioned in another channel that vesktop does not support RPC, tbh I am not sure how does the Discord GameSDK work precisely, but why would it work on macos and not on linux, then?
Well the issue could be that since I am using discord's proprietary libraries it tries to indentify whether or not there is discord's official client RPC server listening. There is not, because Vesktop uses arRPC (obviously) and immidiatelly terminates with this error. It is one of the possibilities, but doesn't explain why it works on macos - it could be that the SDK for mac (aarch64) and linux (x86_64) differs in this specific case. Which would be strange, but if it would not terminate the arRPC server would capture even the proprietary discord RPC (I believe)
your program is trying to xdg-open the discord protocol and when it throws that error its exiting
the error is pretty self explanatory
idk if flatpak is shipping a broken desktop file or something modified it but yeah
contains supported protocols but doesn't use %u or %U in its Exec line! This is inconsistent. isn't clear to me
the desktop file has an x-scheme-handler defined but doesnf have %u in the exec line
%u is a placeholder that would contain the data from the scheme
https://github.com/flathub/com.discordapp.Discord/pull/391
looks like they added the scheme to the desktop file without adding %U in the exec line
open an issue there
The issue happens with Vesktop, though, not discord's client
it works from the browser because they only look for the scheme handler and do their own magic
vesktop doesnt support discord protocol yet tho
yes but your error is happening because of that
Do you see activity on my profile rn? If so, game sdk RPC works with vesktop on macos, which I find strange.
vesktop supports game rpc
vesktop supports rpc via websocket or unix socket via arrpc
your program is calling xdg-open and is exiting cause of that error
but thats different from launching protocol
why r u even calling protocl is that even part of discord_rpc

nop
I am just executing the sdk's functions https://github.com/ZirixCZ/cmus-rpc-c/blob/master/main.c#L115
main.c: Line 115
activity_manager->update_activity(activity_manager, &activity, NULL,
¯_(ツ)_/¯
fix the .desktop by adding the %u or remove the scheme handler entry so it silently fails
I guess it's calling that so the client automatically opens or something??
vesktop is built on top of [...]
what?
It was just a misunderstanding from my side 😅
Why did you suggest creating an issue there. Did you interpret that the issue is with the flatpak discord and not with vesktop at that time?
that error log you see is with the discord Flatpak
the file path is the flatpak's desktop
either way I assume youre doing something wrong initializing the SDK as every other implementation ive seen use it doesnt have this behaviour
https://discord.com/developers/docs/developer-tools/game-sdk#activities
i followed the official docs on activity management
perhaps they used discord-rpc https://github.com/discord/discord-rpc
i know that some projects use it, but it has been deprecated
Happy new year guys!!
happy new year
https://github.com/user-attachments/assets/c32c1d14-6f3f-46c4-8cb1-4fb1ec69d64f
As you can see, the first test is from Vesktop (vesktop-bin AUR, 1.5.4-2) and as you can see on my phone (official discord client from play store), it has some weird color artifact.
This issue doesn't seem to happen at all when screensharing from Firefox (133.0.3-2, pacman).
The same issue occur when using a camera.
this started happening to me too as of today i can not launch the app whatsoever
About our yesterdays convo - this fixed it, you were right.: https://github.com/flathub/com.discordapp.Discord/commit/d118c0b57b5497ec6138a35a2b6125424f17e31f
Discord Account
No response
Operating System
Debian 12
Linux Only ~ Desktop Environment
Gnome on Wayland
Package Type
deb
What happens when the bug or crash occurs?
After downloading your app, I noticed something wrong - there is an LGBT flag on the app icon. I hope you'll fix it.
What is the expected behaviour?
Just normal icon
How do you recreate this bug or crash?
- Install application
Debug Logs
Replace this text with your crash-log. ...
ah what a great way to start the new year
please provide logs
Just adding my file from C:\Users\MIKI\AppData\Roaming\vesktop\sessionData\Session Storage (Windows 11)
000004.log
For other logs, can you please verify the location of where these are stored? I can find them, I just need to know where they are saved to. Also to add I have Vencord on the canary branch of Discord if this is somehow interfearing. (extra info, might not be needed but may be useful, idk)
you get logs by running vesktop from the command like
Discord Account
barrsan
Operating System
Arch Linux
Linux Only ~ Desktop Environment
KDE Wayland
Package Type
Flatpak, and AUR (Extracted from RPM)
What happens when the bug or crash occurs?
I noticed this when I turn on my camera and also screen sharing, and one of my friend said why it have those weird color and it's blurry. Then I started to investigate further.
The weird color artifact only occur when screensharing 1440p / 2k resolution with "Prefer Smoothn...
Discord Account
No response
Motivation
I think it would be useful if changes to the stream settings were persistent. By default, the resolution is 720p, the frame rate is 30fps, and the content type is 'prefer smoothness'. Also the audio stream is set to None. I basically always change these settings and I have to change them everytime a new stream is started. For extra info, I am running the linux client.

delete state.json from your vesktop folder (in
%APPDATA%,~/.configor Application Support)
the error is gone, but the app is still just a white square. left it open for like 30 min nothing happened. the log just talks about the update, same thing as last time.
not only arch is affected but also OpenSUSE TW since a few weeks
screensharing is unusable, it would be nice to have a dedicated thread for all the users experiencing this problem, hunting for non-locked issues on github will make it hard for everyone to find a solution.
Discord Account
No response
Operating System
Ultramarine Linux 41
Linux Only ~ Desktop Environment
KDE Plasma 6.2.5 Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
closing vesktop via normal means, like pressing the close window control or using my window manager's close window shortcut, doesn't allow vesktop to reopen at all. running it from the terminal spits out Vesktop is already running. Quitting..., which is not true. there is no ...
if you close vesktop with the close button or Alt+F4, it only hides the window but still remains running in the background. if you want to fully close it, use Ctrl+Q
Alternatively, if you don't want the background behaviour at all, disable it in the Vesktop settings.
Alternatively, if you don't want the background behaviour at all, disable it in the Vesktop settings.
which i already did, months ago. i've always had the tray icon disabled. vesktop is completely closed, as i said in the issue. there is no tray icon, no running process, and logging out of my entire system and logging back in still does not allow vesktop to open. this is a bug, and it's only recently started happening.
Discord Account
No response
Operating System
Ultramarine Linux 41
Linux Only ~ Desktop Environment
KDE Plasma 6.2.5 Wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
i'm making a whole new issue with the same contents as my previous one because the bug was immediately swept under the rug as intentional behaviour, which is incredibly frustrating and offensive because it obviously isn't. i repeat myself, *vesktop is not running in any way sha...
to clarify even further, i have "minimise to tray" turned off and have for months. there is no tray icon, there is no running process, and logging out of my system's user account and ending my session does not fix the problem. the only solution i've found is completely rebooting my system.
what the hell is ultramarine linux
your error [3:0105/154138.148852:ERROR:process_singleton_posix.cc(1138)] Failed to create socket directory. means Electron failed to create the file:
// Create the socket file somewhere in /tmp which is usually mounted as a
// normal filesystem. Some network filesystems (notably AFS) are screwy and
// do not support Unix domain sockets.
if (!socket_dir_.CreateUniqueTempDir()) {
LOG(ERROR) << "Failed to create socket directory.";
return false;
}
try to completely remove vesktop and reinstall it. specifically, delete ~/.config/vesktop
do not deliberately create duplicate issues or you will be blocked.
i can actually replicate this in my vms (win 11 and 10)
something is exploding with the intro settings select
yeah it works for me too (linux)
@humble mortar have you ever encountered a vesktop bug where datastore / indexeddb just hangs
nup
do u launch multiple instances
never
guh only errors that happen are the same
except the linux one errors but doesnt implode
maybe platform difference guhh
am i gonna have to add logging with notepad on windows
what if i smb share
ok
it seems to be a platform implementation difference on how electron figures out conflicting window settings
firstLaunch.ts: Lines 29-36
const win = new BrowserWindow({
...SplashProps,
frame: true,
autoHideMenuBar: true,
height: 470,
width: 550,
icon: ICON_PATH
});
removing frame: true or adding transparent: false fixes it
SplashProps has frame: false and transparent: true
Can someone who is experiencing this try to build and run with either frame: true removed or add transparent: false https://github.com/Vencord/Vesktop/blob/6c4ecc0d64a843ec942b4fa645c0bfe617b21257/src/main/firstLaunch.ts#L29-L36
this started to happen to me a couple days ago aswell
holy "why isn't NoDevToolsWarning enabled by default" again
Discord Account
No response
Motivation
I think discord may detect that user have modded client. They sent it in init event in web socket.
The function they use to detect right now:
function i() {
return false;
let e = window;
return null != e.jQuery || null != e.$ || null != e.BetterDiscord || null != e.BdApi || null != e.rambox
}
Solution
use less global variables, logging and etc. make the detection of a mod client less poss...
wait until he finds out discord has been detecting client mods since ages
did bro forget about the notrack change recently
noTrack.ts: Lines 64-72
find: ".BetterDiscord||null!=",
replacement: {
// Make hasClientMods return false
match: /(?=let \i=window;)/,
replace: "return false;"
}
}
],
I've been having issues with screensharing for the last month or two (I'm guessing since the release of v1.5.4?), but rolling back to previous commits, it seems like I need to go all the way back to df05d12fb26a97c63323a7b9fdfb103ec580433c (from April) to get properly working screenshare on Linux. I've been using Vesktop since around September, and I've always had issues with streams being initially low resolution then switching to the correct resolution, but the issues have got particularly ...
Discord has had this for years and it doesn't even detect Vencord. But if they wanted to detect Vencord it would be incredibly easy and there would be no way for us to prevent it. It really doesn't matter, they don't care about mods.
It's been a while since I posted on this issue, so here's my update
Screensharing works perfectly for me on Linux. Here's the output from inxi -Fxz as a reference for my system setup
I have a friend on a very similar setup to me, same distro, same DE, same audio setup, etc, except they're using an AMD gpu, and both screensharing and camera feeds are partially broken for them. Specifically, the screenshare or camer...
I'm gonna lose it
archwiki has a very good chromium hardware accel entry
explains everything and how to trouble shoot
exploodee
then comment :p
I just switched from EndeavorOS (arch) to Bazzite (atomic fedora) and came upon this issue myself.
The native Discord flatpak has no problem picking up my mic without cutoffs. Any other client (goofcord as well) has this problem.
Someone recommended putting --disable-features=WebRtcAllowInputVolumeAdjustment into the launch options of the flatpak but that doesn't seem to work for me.
discord desktop doesnt use chromium's webrtc right
Discord Account
Szentigrade
Operating System
PikaOS Linux
Linux Only ~ Desktop Environment
KDE on Wayland
Package Type
Deb
What happens when the bug or crash occurs?
i will start to stream and the fps ingame will drop to 1-2fps
What is the expected behaviour?
i expect to stream in full fps
How do you recreate this bug or crash?
start the stream
Debug Logs
loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
[...
ok ive done some testing and it seems as soon as electron starts encoding with gpu the stream explodes
perfectly describes the behaviour theyre mentioning
is this a chromium regression or something
can't stream to older clients with hardware acceleration
I can stream hardware accelerated just fine to myself from vesktop to latest chromium
but older and it explodes
My system:
OS: Arch Linux
Kernel version: Linux 6.12.8-zen1-1-zen
Desktop: Gnome (wayland) 47.2
Vesktop Version: 1.5.3 flatpak
CPU: AMD Ryzen 7 6800HS
GPU: AMD Radeon 680M
All the streams I have done are in "720p 30 fps" with "prefer clarity" option enabled.
Regarding the infinite loop loading, I have the same issue on Arch Linux.
I tried doing some testing and found out that if the other user tries to connect to my live stream using an Android device or the web client (for examp...
Discord Account
tranvlnh
Operating System
fedora 41
Linux Only ~ Desktop Environment
Gnome on wayland
Package Type
Flatpak
What happens when the bug or crash occurs?
rich presence not working
What is the expected behaviour?
rich presence working
How do you recreate this bug or crash?
not crash
Debug Logs
not crash
Request Agreement
- [X] I have searched the existing issues and found no similar issue
- [X] I am using the latest Vesktop and...
my grandma could file a more informative issue than this. please use our support channel
AYOOOOOO
For now, if anybody wants this resolved, add this argument to your .desktop file of Vesktop:
--disable-features=WebRtcAllowInputVolumeAdjustment
This partially works, you will get pop-up errors whenever it tries to adjust the gain.
🇷🇴
this is brilliant 
I have a friend on a very similar setup to me, same distro, same DE, same audio setup, etc, except they're using an AMD gpu, and both screensharing and camera feeds are partially broken for them. Specifically, the screenshare or camera output often will flash green, then completely freeze and stop updating for many users. For me, I see the green glitching, as well as some tearing, but their screenshare is still fully functional afterwards
I also reported the issue on #1031, but got marke...
@scenic hollow enjoy https://github.com/tuxinal/venbind/pull/2 https://github.com/tuxinal/Vesktop/pull/1
I also had some auxiliary questions:
- Why use node-bindgen instead of napi-rs, which is significantly better documented and has a lot more usage? Notably, it would also solve the Electron headache, as support is builtin
- Is anything blocking https://github.com/tuxinal/venbind/pull/1, which is pretty much the only blocker for good Windows/Linux support after my PR?
Same for me, but I only use one account and it only happens when the PC is turned off.
EndavourOS AUR.
Hello, first time trying to use Vesktop, im getting the same issues, after Loading Besktop I just get a big white screen. Shame, was really looking forwards to using this app
hi thank you for the pr!!
i don't remember exactly why i chose node-bindgen i think it was easier to make the functions on the rust side be async with node-bindgen than napi-rs (although i think i didn't even end up using async because i didn't know how to make the dispatch_proc function yield properly or smth like)
the main issue with xdg rn was that there is basically nowhere we can test things properly cause something is broken either with kde's portal implementation or ashpd's way of handling sessions. otherwise the pr is basically ready to merge
quite honestly i completely forgot about this lmao
oh also i haven't chosen a license for venbind yet i thought it might be a better idea to do that before merging stuff
I am using cosmic-os (wayland). I tried either to remove frame: true or to add transparent: false, but it doesn't change situation. After playing for about an hour, I managed to make it render.
After running pnpm start, I got:
APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
(node:61852) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/viliusp/.config/vesktop/...
What is cosmic-os? The cosmic DE by system76? If so that DE is still highly in alpha and is likely the cause of YOUR specific issue.
Everyone else in here is a windows user and I can replicate this in both 10 & 11 vms just fine. The fix I mentioned earlier consistently fixed the white screen issue so I'm just waiting for someone on baremetal windows to replicate.
we love alpha distros
bwaa
Can someone who is experiencing this try to build and run with either
frame: trueremoved or addtransparent: false
worked for me
i will use github editor to make pr
well actually
Clicking on the reset Vencord option in the tray menu, than selecting canary in the installer fixed the issue for me.
first launch tour overrides frame to true
is the splash not its own window
god I had fun trying to use breakpoints in the dispatch proc before
it was such a bad idea I swapped to println
it is
anyway trans and frame should work together
only resizable doesnt work
try adding resizable: false instead
what happens with testing w/xdg that's broken also
actually it should already be set
only kde fully implements it and theres some awkwardness there
making me turn on my laptop
insaane
specifically global shortcuts api?
is this related maybe https://github.com/electron/electron/issues/41063
Preflight Checklist I have read the Contributing Guidelines for this project. I agree to follow the Code of Conduct that this project adheres to. I have searched the issue tracker for a bug report ...
arch wiki would have me believe hyprland xdg portal has fine global shortcut support
global shortcuts portal "yes" on arch wiki unless they don't actually have it and you have to use separate protocol?
surely not
link me
make a comment on the pr and ill test when i have a chance
ok seems youre right https://wiki.hyprland.org/Configuring/Binds/#dbus-global-shortcuts
must be new
this is actually good
Discord Account
voidptr_t
Operating System
Arch Linux. Kernel: 6.12.8-arch1-1 (64-bit). Pipewire
Linux Only ~ Desktop Environment
KDE Plasma 6 (wayland) / Hyprland / Sway
Package Type
AUR/Flatpak/AppImage/Build from source
What happens when the bug or crash occurs?
Audio from bot is in mono
What is the expected behaviour?
Audio from bot should be in stereo
How do you recreate this bug or crash?
- Ask any music bot to play music with stereo effects (ht...
Same. I've been meaning to write about this as well, glad someone already did it for me
This is a Discord limitation and not realistically possible to fix.
Their Desktop app uses a different screenshare implementation than their web app (which is what Browser Discord and Vesktop use). Their web app implementation forcefully downmixes everything to mono
The only way to fix it would be to reimplement their desktop implementation from scratch but we're not doing that
This is a Discord limitation and not realistically possible to fix.
Their Desktop app uses a different screenshare implementation than their web app (which is what Browser Discord and Vesktop use). Their web app implementation forcefully downmixes everything to mono on their server (so we can't stop it)
The only way to fix it would be to reimplement their desktop implementation from scratch but we're not doing that
It`s not an screenshare issue
It's not about screenshare, it's about voice transmission. Try to play any stereo music in any discord bot, and you'll notice that sound from them is in mono
same thing, it affects all voice chat audio streams
try on a chromium browser too
for anyone wandering out here, there's currently as of writing an discord outage:
https://discordstatus.com/incidents/41xtl5znmt2h
@scenic hollow do u know what the preferred_trigger syntax is
1 About #File Name: shortcuts-spec.xmlID: about The purpose of this specification is to specify how shortcuts can be specified between components. Be it for global shortcuts in the XDG portals or to specify how we need an application to get started, we need shared means to communicate these triggers…
Ah i was doing Ctrl+
its CTRL
its returned as a string of Ctrl
truely the best api ever
i have a working demo app in python now
i think it works fine if it's all lowercase also?? pretty sure that's what i did at some point
its def ashpd
with a consistent session token?
yep
handle_token is what changes
but it can be consistent too
as long as you dont create new interfaces without closing the previous
/org/freedesktop/portal/desktop/request/1_295/demo_1
Session created: /org/freedesktop/portal/desktop/session/1_295/vesktop
/org/freedesktop/portal/desktop/request/1_295/demo_2
dbus.Dictionary({dbus.String('shortcuts'): dbus.Array([dbus.Struct((dbus.String('shortcut2'), dbus.Dictionary({dbus.String('description'): dbus.String('Demo Shortcut 2', variant_level=1), dbus.String('trigger_description'): dbus.String('', variant_level=1)}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.String('shortcut1'), dbus.Dictionary({dbus.String('description'): dbus.String('Demo Shortcut 1', variant_level=1), dbus.String('trigger_description'): dbus.String('Ctrl+1', variant_level=1)}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(sa{sv})'), variant_level=1)}, signature=dbus.Signature('sv'))
Shortcuts bound successfully:
shortcut2:
Description: Demo Shortcut 2
Trigger:
shortcut1:
Description: Demo Shortcut 1
Trigger: Ctrl+1```
demo_1 registers everything and creates the session which has the app name
demo_2 listens for the shortcuts and changes
i've just emailed the guy responsible for the kde impl again about whether it's supposed to be consistent or not just to make sure
oh those are different 
session_handle_token is the app id
vesktop or dev.vencord.Vesktop (dev_vencord_Vesktop)
wdym it's the app id? you mean it gets appended to the app id?
cause that's not what i'm seeing
we went over this at some point didn't we
its what kde uses for the name and app icon in the settings menu
OHH
i see yeah
thats a flawed implementation yeah
it pulls the icon from the desktop file of the same name
but since you need to replace . with _ it doesnt find a demo_app.desktop when it should be looking for demo.app.desktop
so thats a bug but other than that it works
also it returns the bound trigger as the preferred trigger irregardless if it conflicts with an existing bind
i guess calling listshortcuts intsead of relying on what it returns would fix that
can i have your python script perhaps
yeah let me clean it up
@humble mortar can i also have your .desktop file
so what confused me here was that i thought the app id is taken from the .desktop file but apparently not???
https://github.com/Vencord/Vesktop/issues/500#issuecomment-2094367152
This actually helped me and resolved for both appimage and flatpak installations. Can flatpak recipe be possibly changed to fix host somehow? Or leave notices in this repository about sound server? Because I have PulseAudio on Debian by default. It took some time to research and reading logs like
[2025-01-08 22:14:51.456] [venmic] [warning] [patchbay] (get) pipewire was not detected as main audio server
[2025-0...
why?
theres nothing specific about it
anyway since its def a client implementation issue not KDE maybe close that issue
the icon thing tho def needs an issue
all flatpak apps won't have an icon
:p
also in an actual implementation make sure shortcut ids are prefixed and overly specific to prevent any sort of clash
As an update for anyone with the PR watched: further work on Venbind has begun to support Windows and Wayland (through xdg-desktop-portal DBus), and is underway.
I can take over the XDG PR if that guy is inactive by the way
i am keenly interested in getting this into vesktop and have free time
i don't think there is anything else to be done on the xdg pr itself
just testing?
i still doubt that. i think you are using the session handle token wrongly. even if it is consistent it definitely isn't supposed to be the app id.
the app id is supposed to be inferred from elsewhere (i assumed it would be the .desktop file but idk about that anymore) and then used in this componentName function: https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/blob/master/src/session.h?ref_type=heads#L188 which is used for figuring out the name used in KCM. and here you'll see it's the session handle token appended to the appId. the way you have it set up there is no appId and the session handle token alone just happens to match the .desktop file and so it even fetches the correct icon.
i think we should figure out where the app id is supposed to come from and make a pr to the kde portal
session.h: Line 188
return m_appId + m_token;
yeah kinda that's kinda blocked by the whole xdg thing
whats the issue though
this in short https://bugs.kde.org/show_bug.cgi?id=492992
cant i just go test it on my hyprland on my framework laptop
lmaoo
surely xdg-desktop-portal-hyprland is fine
yeah you could try that
also this suggests it Works its just KDE's settings panel being busted
yeah that's what i'm assuming but cowokie says that it's supposed to be that the session is consistent so kde doesn't make a new item for every run
the rust library we use doesn't really support setting the session directly tho
and i've asked the ashpd people about it and they say you aren't supposed to do that https://github.com/bilelmoussaoui/ashpd/issues/231
how is a consistent session possible
you're not supposed to keep a consistent session across several runs no?
thats why its a "session"
yeah that would make sense too idk
the kde one or the ashpd one?
if i have 2 instances of a program open then I would think the shortcuts would conflict
kde one
except sessions aren't instances. i wouldn't really want it to reset my shortcuts after i restart vesktop
You save the shortcuts in the discord settings
they get reregistered
If you want to edit the shortcut keys from kde control panel then the changes wont be reflected in discord settings without special work and you'll have a conflict
Unless the issue is that it stays there even after the session is closed
which looking at your bug report it seems like you close the session
yeah basically that
they get reregistered under a different name. you can't modify the existing old ones. and the one from last session sticks around so every time you start a new session and vesktop registers shortcuts you get conflicts and you have to delete the old one and make sure the new one has all the shortcuts active.
You're going to have to add IPC for key changes right
so that discord settings change to match
(thats another issue)
looks like receive_shortcuts_changed exists in ashpd
oh yeah maybe that's another issue tho not too concerned about that rn
So do the shortcuts physically not work
or just a control panel display issue
yeah they are conflicting they don't fully register
Does literally no one use this api how has this never popped up before
YEAH I GENUINELY DON'T KNOW
maybe no one has used it through ashpd and everyone just keeps supplying a static session token
I guess REALLY no one does because kde devs have let the bug report sit there for 4 months
Either that or no one uses ashpd global shortcuts
probably that
why the hell does ashpd not provide options in create_session
apparently you aren't supposed to changed it yourself
Not even true
Part of it is yeah
the TOKEN bit
where is the SENDER unique name from
dbus stuff
idk exactly where but dbus handles that
still tho i think it's more of a kde issue than an ashpd issue
Yeah i checked the bus implementation handles it
ashpd zero fault here
Spec conforming!!
Now i really don't know how this hasn't been reported before you
again people probably just used a consistent session handle token to get around it
i've emailed the guy responsible for the kde impl about this i think just removing m_token from here should fix it. i've also asked about if the session token is supposed to be consistent or not let's see what he says
What an anticlimactic fix
YEAH TOOK ONLY LIKE 4 MONTHS
I wonder if no one follows the spec and thats why its gone unnoticed
Because its clear as day
Unique and unguessable
Literally put a random number in there
That is what the spec says
ok but idk if it's supposed to be random per session maybe just a random number for one time is enough
That is dumb and makes no sense
which is the same as having it be static i guess
The SENDER unique name should be the thing that is static
That's what identifies the app
The TOKEN is a session identifier per-session
Why should client apps have to save a random token number somewhere to be able to run dbus sessions properly
Or hardcode one
which the spec says not to do
i think the sender is actually just another random per session thingy
I wonder if that's in the spec for security reasons given the "unguessable" bit
how does kde identify the app then
by appId
does dbus give the app id over
this would seem to be true
not sure why the xdg spec is so unclear
I have looked into it and you are not insane
inputcapture.c: Line 350
g_variant_builder_add (options, "{sv}", "handle_token", g_variant_new_string (token));
ok then why has no one reported this!!!!
its definitely a kde issue
xdg_desktop_portal_client.dart: Lines 145-153
String _generateToken() {
final random = Random();
String token;
do {
token = 'dart${random.nextInt(1 << 32)}';
} while (_usedTokens.contains(token));
_usedTokens.add(token);
return token;
}
Used for handle_token and session_handle_token
Every single xdg dbus implementation uses a random string
Just like the spec says
Either every implementation is wrong or kde is broken
I am not inclined to believe the former
handle_token.rs: Lines 39-49
impl Default for HandleToken {
fn default() -> Self {
let mut rng = thread_rng();
let token: String = (&mut rng)
.sample_iter(Alphanumeric)
.take(10)
.map(char::from)
.collect();
format!("ashpd_{token}").parse().unwrap()
}
}
ashpd is similarly correct
omfg guess what the guy responsible for the kde implementation is doing https://github.com/aleixpol/mumble/blob/work/xdp-support/src/mumble/GlobalShortcut_xdp.cpp#L65
GlobalShortcut_xdp.cpp: Line 65
{ QLatin1String("session_handle_token"), "Mumble" },
Okay well not only that I am staring at the hyprland implementation and I am thinking it probably also wont work correctly
I havent tested it yet but
m_vSessions.emplace_back(std::make_unique<SSession>(appID, requestHandle, sessionHandle)).get();
I figure nothing removes it from m_vSessions whenever the session is closed
The stuff inside the SSession is freed at least
But the SSession lives forever in this vector
i don't think it's supposed to be removed it should just reuse the old one and not make a new one every time
It doesnt reuse the old one
is the issue
it just emplaces back a new one every time
even if it has the same app id
So this would cause same issue as KDE
You can't even circumvent with the same session handle
because any new session with the same app id would do it
you'd have to change the app id every time
which you can't do
guhh could you perhaps test that and make sure
Okay actually I think it should still work
actually it wont getShortcutById will find a dead shortcut
Very unfortunate
I can give it a shot ig
This API is such a mess and it has been a part of the xdg spec since September 2022
linux desktop development actually doomed
also of course this guy is using a const string
even better part hes using a const string where the spec explicitly says it should be random
I didnt boot into arch for like a week so my sddm is broken and cant login to hyprland through uwsm
and it refuses to login by fingerprint
True peak
Time to fix allat
and that's why i use nixos
(i am miserable)
Apparently it was a rogue monitor in my hyprland config
from when I had another monitor plugged in
Apparently that managed to fry sddm to the point of fully hanging at shutdown and forcing power off
gg
I for one am impressed
I have a ryzen 5 3600 on my main pc and a ryzen 9 7940hs on the framework laptop
aka double the speed
and 2 more cores
I am now very sad that I was not working on venbind on it instead of the main pc because it compiled all of the dependencies in 6 seconds
you can also get this might be slightly easier to set up https://github.com/tuxinal/kde_xdp_bugreport
totally forgot i was just gonna compile this
whoops
compiled in 16 seconds
let me compare with main pc
The session doesnt even work
Which i find hilarious
Oh
The appid is fucking empty
no wonder its breaking
i need a .desktop file for this or whatever
it comes with one!
the app id is still empty
unless gtk-launch doesnt work with this
I hate xdg desktop portal so bad
This is one of the worst documented apis i've ever worked with
Have to just go dig through the c files to figure out whats going on
yeah idk how youre supposed to specify the app id i used to think it was a .desktop file (maybe it actually was???) but that doesn't work anymore


