SUMMARY When configuring discord to autostart it creates a systemd unit, when pinning discord to task manager it also generates a systemd unit when starting. autostart launches under systemd, task manager under plasmashell, if discord was autostarted and main window is closed (running on system tray), opening it again from a pinned task manager icon will generate a new systemd unit and start a new/separate instance of discord instead of re-opening the window of the existing instance. I don't know who's bug this is so reporting it here as a start. STEPS TO REPRODUCE 1. Enable auto start on discord 2. Allow systemd to autostart discord 3. Close the main window 4. Attempt to open discord again from pinned discord on taskbar OBSERVED RESULT A second discord instance is opened instead of the already running instance EXPECTED RESULT It should re-open the window of the existing discord instance SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux Unstable Branch (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.107.0 ADDITIONAL INFORMATION
Are you enabling Discord to autostart in its own settings page, or in System Settings > Startup and Shutdown > Autostart?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #1) > Are you enabling Discord to autostart in its own settings page, or in System > Settings > Startup and Shutdown > Autostart? issue can still happen without auto start, that said saw people reporting it on ubuntu and I've been able to reproduce it by launching from the command line, so something in discord process "breaks" after a while that makes it's existing instance detection code no longer work so doesn't seem to be a plasma specific bug. https://www.reddit.com/r/discordapp/comments/12ibosm/discord_is_opening_a_new_instance_instead_of_an/
Is that the case in Plasma 6 as well? If so, are the steps to reproduce identical to what was written in the original problem description? If not, can you write new ones? Thanks a lot!
(In reply to Nate Graham from comment #5) > Is that the case in Plasma 6 as well? Currently on plasma 6 and still happens Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF > If so, are the steps to reproduce identical to what was written in the > original problem description? > If not, can you write new ones? Initially i thought it was due to one being started under systemd and another from plasmashell with different paths but since then I've managed to get double instances under plasmashell. Not sure how consistent this is as I already trained myself to never close discord to avoid the bug. Reproducing: 1. Ensure discord is fully closed 2. Launch discord from task manager panel 3. Close main window and confirm tray icon still running 4. Wait around 6 minutes without using discord (but using the browser and other apps) 5. Launch discord again, a second instance should now start
I can't reproduce that at all. Is Discord even capable of opening two instances? Mine isn't. How are you making that happen?
(In reply to Nate Graham from comment #7) > I can't reproduce that at all. Is Discord even capable of opening two > instances? Mine isn't. How are you making that happen? I reproduce it the way i mentioned I open discord and if I close the main window, eventually it will happen. I've had times were I went hours without it happening and others were it will happen right away. At this point I just never close discord window and work around it like that.