ZVNexus
commented
5 months ago What version of Fedora is this, and what hardware are you running?
Closed gogi983 closed 5 months ago
ZVNexus
commented
5 months ago What version of Fedora is this, and what hardware are you running?
gogi983
commented
5 months ago What version of Fedora is this, and what hardware are you running?
I'm sorry we already talked together on FlatHub about this issue, it's the same me and the same issue.
ZVNexus
commented
5 months ago What version of Fedora is this, and what hardware are you running?
I'm sorry we already talked together on FlatHub about this issue, it's the same me and the same issue.
Yes but you didn't specify the version of Fedora that you're running. This is important for reproducibility.
gogi983
commented
5 months ago Yes but you didn't specify the version of Fedora that you're running. This is important for reproducibility.
You probably misread. I'm running a Fedora Workstation .
gogi@fedora:~$ neofetch
.',;::::;,'. gogi@fedora
.';:cccccccccccc:;,. -----------
.;cccccccccccccccccccccc;. OS: Fedora Linux 39 (Workstation Edition) x86_64
.:cccccccccccccccccccccccccc:. Host: VPCF13E1E C606PNBV
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 6.6.11-200.fc39.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 3 hours, 44 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Packages: 2004 (rpm), 26 (flatpak)
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Shell: bash 5.2.21
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 1600x900
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: DE: GNOME 45.3
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; WM: Mutter
ccccc:XM0';cccc;MMM.;cccccccccccccccc' WM Theme: Adwaita
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Theme: Adwaita-dark [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Icons: WhiteSur-dark [GTK2/3]
cccccc;dNMWXXXWM0::cccccccccccccc:, Terminal: gnome-terminal
cccccccc;.:odl:.;cccccccccccccc:,. CPU: Intel i5 M 460 (4) @ 2.534GHz
:cccccccccccccccccccccccccccc:'. GPU: NVIDIA GeForce GT 425M
.:cccccccccccccccccccccc:;,.. Memory: 4562MiB / 7919MiB
'::cccccccccccccc::;,.
razzeee
commented
5 months ago As it might be helpful and I'm already here. Slack still works for me, via the icon
╰─ neofetch ─╯
.',;::::;,'. razze@fedora-desktop
.';:cccccccccccc:;,. --------------------
.;cccccccccccccccccccccc;. OS: Fedora Linux 39 (Workstation Edition) x86_64
.:cccccccccccccccccccccccccc:. Host: MS-7A32 1.0
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 6.6.11-200.fc39.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 4 hours, 50 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Packages: 2797 (rpm), 102 (flatpak)
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Shell: zsh 5.9
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 3840x2160
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: DE: GNOME 45.3
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; WM: Mutter
ccccc:XM0';cccc;MMM.;cccccccccccccccc' WM Theme: Adwaita
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Theme: Adwaita [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Icons: Adwaita [GTK2/3]
cccccc;dNMWXXXWM0::cccccccccccccc:, Terminal: gnome-terminal
cccccccc;.:odl:.;cccccccccccccc:,. CPU: AMD Ryzen 5 2600 (12) @ 3.400GHz
:cccccccccccccccccccccccccccc:'. GPU: AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT
.:cccccccccccccccccccccc:;,.. Memory: 7813MiB / 15931MiB
'::cccccccccccccc::;,.
wondering if it's the nvidia gpu had to patch this some time ago https://github.com/flathub/im.riot.Riot/commit/2b9214a466669c8a84cbfc7b87ecff2f1cfe8db4
you might want to look at the latest version of that tho https://github.com/flathub/im.riot.Riot/blob/master/element.sh
gogi983
commented
5 months ago wondering if it's the nvidia gpu had to patch this some time ago flathub/im.riot.Riot@2b9214a
you might want to look at the latest version of that tho https://github.com/flathub/im.riot.Riot/blob/master/element.sh
@razzeee Are you addressing me or @ZVNexus ?
ZVNexus
commented
5 months ago wondering if it's the nvidia gpu had to patch this some time ago flathub/im.riot.Riot@2b9214a
you might want to look at the latest version of that tho https://github.com/flathub/im.riot.Riot/blob/master/element.sh
FYI that flag broke launching Discord on the RTX 4080 for me, don't know if it'll be the same case here but I can't reproduce anymore since I sold mine for a better card (RX 7900 XTX).
ZVNexus
commented
5 months ago @gogi983 Try installing this test build with the --disable-gpu-sandbox flag: flatpak install --user https://dl.flathub.org/build-repo/77384/com.slack.Slack.flatpakref
gogi983
commented
5 months ago @gogi983 Try installing this test build with the --disable-gpu-sandbox flag: flatpak install --user https://dl.flathub.org/build-repo/77384/com.slack.Slack.flatpakref
Tried, but didn't work...
gogi983
commented
5 months ago Ok so I did my own investigation as this started to f**k my brain since last evening... :D And the problem is... SOLVED :D
So what was the origin of the issue? Well, a couple of days ago, I was looking how to disable these kinf of apps from keeping running in background even when closed. Along with "Slack" I also use "Discord", "Viber", "Telegram", ... and all of these bundles (except Slack, but I discovered the option later in the app preferences...) do not have an implemented option that allows one to disable background-running when app is closed.
So, as I'm using Fedora Workstation with Gnome DE, I went to :
Parameters > Applications > "App"and there I disabled "Allow running in background" for every app mentionned above, so that did the maths... Of course at this point I didn't notice that this will make Slack crash because I didn't run it for a couple of days until yesterday.
Then happened what happened yesterday and I told myself it was impossible that there may be some code issue as the app was running fine through web-browser redirection and CLI but crashing on launching by icon-click gesture. So I found the correspondent ".desktop" file :
/home/gogi/.local/share/flatpak/app/com.slack.Slack/x86_64/stable/fc76716747627dda818e1a14562248cc653d4f18ea75d655fb88eddb2d2849de/export/share/applications/com.slack.Slack.desktopand started tweaking the "Exec=" line but without succes. And there I found a line that lead me to the origin of the issue :
StartupNotify=trueThere was the issue :
case 1 --> StartupNotify = true && Paramteres>Applications>Slack>Running in background = disabled
---> makes the app crash on starting by clicking on the iconcase 2 --> StartupNotify = false && Paramteres>Applications>Slack>Running in background = disabled
---> doesn't make the app crashcase 3 --> StartupNotify = true && Paramteres>Applications>Slack>Running in background = enabled
---> doesn't make the app crashI didn't try the last option with
StartupNotify = true && Paramteres>Applications>Slack>Running in background = enabledbecause it was useless in my case.
So the solution is either to change
StartupNotify = trueto "false" or remove it from the desktop file (which I would advise if you agree with the commit) in further update, or use the option implemented in Slack Preferences that allows to diable running in backgrpound when the app is closed.
I personnally prefer the first option, because I had a look in the ".desktop" file of the other apps (Viber, Discord, Telegram, ...), they don't have this option and still run smootly.
Anyway, the issue is solved and that's what matters the most. Feel free if you have any questions.
ZVNexus
commented
5 months ago Looked into this a bit more, it doesn't seem like Slack itself is crashing. It looks like xdg-desktop-portal is killing it when I was using opensnoop.
Similar issue here: https://github.com/flatpak/xdg-desktop-portal/issues/1010
For now I'll just mark this as an upstream bug.
gogi983
commented
5 months ago Looked into this a bit more, it doesn't seem like Slack itself is crashing. It looks like xdg-desktop-portal is killing it when I was using opensnoop.
You're right, my bad. I use to use the verb "crash" because it's the first term that occurs to my mind regarding to what happens, but the conflict probably takes its source in "xdg" stuff... Would be useful if someone using some other Desktop Environment could make some tests.
nathan-weinberg
commented
5 months ago I am experiencing this issue as well - running Fedora 38 kernel 6.6.11-100.fc38.x86_64
gogi983
commented
5 months ago I am experiencing this issue as well - running Fedora 38 kernel
6.6.11-100.fc38.x86_64
Which desktop environment and did you do any manips to get to the issue?
franklookyou
commented
5 months ago Seeing this myself. I believe it broke for me somewhere between the 17th and the 22nd.
Stock Fedora 38. No overrides set.
slack.txt (I think this includes everything. Let me know if attaching something else would helpful.)
gogi983
commented
5 months ago Seeing this myself. I believe it broke for me somewhere between the 17th and the 22nd.
Stock Fedora 38. No overrides set.
slack.txt (I think this includes everything. Let me know if attaching something else would helpful.)
@franklookyou
You can attach the output of :
$journalctl -xe | grep slack
You can also give it a try by opening this path (depending on you installed the app on user side or system side) :
user side -->
/home/$USER/.local/share/flatpak/app/com.slack.Slack/x86_64/stable/9fe6c491146158433624731ba33de69a8ee5c093753229352112c2212945f5a2/export/share/applications/com.slack.Slack.desktopsystem side --->
/var/lib/flatpak/app/com.slack.Slack/x86_64/stable/9fe6c491146158433624731ba33de69a8ee5c093753229352112c2212945f5a2/export/share/applications/com.slack.Slack.desktopand edit this file by commenting the following way :
[Desktop Entry]
Name=Slack
StartupWMClass=Slack
Comment=Slack Desktop
GenericName=Slack Client for Linux
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=com.slack.Slack --file-forwarding com.slack.Slack @@u %U @@
Icon=com.slack.Slack
Type=Application
#StartupNotify=true
Categories=GNOME;GTK;Network;InstantMessaging;
MimeType=x-scheme-handler/slack;
X-Desktop-File-Install-Version=0.27
X-Flatpak-RenamedFrom=slack.desktop
X-Flatpak=com.slack.SlackSo you should comment the line about "StartupNotify". Then log out and log in again and give it a try opening the app by clicking on the icon. If everything is fine then the issue is the same as above, and the commit is already merged for a future upgrade.
franklookyou
commented
5 months ago After a bit more investigation of the desktop files, I realized I had (years ago) created an overriding "com.slack.Slack.desktop" that was "extra" breaking things.
I removed that extra desktop file, did another purge/reinstall of "com.slack.Slack", and things were working again. (interestingly, with no need to manually comment StartupNotify)
So, problem was between chair and keyboard. Sorry about that and thanks for your help.
nathan-weinberg
commented
5 months ago I am experiencing this issue as well - running Fedora 38 kernel
6.6.11-100.fc38.x86_64Which desktop environment and did you do any manips to get to the issue?
I'm on GNOME 44.8 - no manips, I have found as a workaround I can run the flatpak directly from the command line as a background process and I don't see the same crashing
gogi983
commented
5 months ago I am experiencing this issue as well - running Fedora 38 kernel
6.6.11-100.fc38.x86_64Which desktop environment and did you do any manips to get to the issue?
I'm on GNOME 44.8 - no manips, I have found as a workaround I can run the flatpak directly from the command line as a background process and I don't see the same crashing
You can try to temporarily edit the ".desktop" file as I mentionned in a post above and see if it solves the problem.
ZVNexus
commented
5 months ago @gogi983 @nathan-weinberg Please test this build: flatpak install --user https://dl.flathub.org/build-repo/78235/com.slack.Slack.flatpakref
gogi983
commented
5 months ago @gogi983 @nathan-weinberg Please test this build: flatpak install --user https://dl.flathub.org/build-repo/78235/com.slack.Slack.flatpakref
@ZVNexus
Works for me in both cases :
enabled "Running in background" in
Gnome Settings >> Applications >> Slackdisabled "Running in background" in the same...
Of course you removed "StartupNotify" from the .desktop file in this build.
nathan-weinberg
commented
5 months ago I am experiencing this issue as well - running Fedora 38 kernel
6.6.11-100.fc38.x86_64Which desktop environment and did you do any manips to get to the issue?
I'm on GNOME 44.8 - no manips, I have found as a workaround I can run the flatpak directly from the command line as a background process and I don't see the same crashing
You can try to temporarily edit the ".desktop" file as I mentionned in a post above and see if it solves the problem.
This seems to have fixed the issue!
Hi everyone,
Today I started having an issue with Slack Flatpak app. Indeed, it started crashing when trying to open it by clicking on the icon. Starting the app through web-browser redirection or from CLI is working instead…
I already tried to clear cache eventually, but that didn’t help. Tried to uninstall/re-install, didn't help either. I also had a look at the log, after trying to open the app the three ways I mentioned before, the log output is exactly the same for all three ways. No difference that could lead me to a point unfortunately.
Here is it :
I’m running a Fedora Workstation up-to-date.
So I have no idea what the issue can possibly be and I request some help from contributors please. Feel free to ask for more informations or necessary logs.