Discord won't open on Linux when an update is available

댓글

댓글 20개

  • !ioan(mynd)² 2 meters away

    the package in the main arch linux repos(that manjaro base its repos on) is currently out of date, wait a few days :P. There are app images and flatpak versions avalible. I went the route of editing the pkgbuild and updating that way

    -4
    댓글 작업 고유 링크
  • taktician

    Thanks for the tip on images / flatpak. It's inconvenient, but it works in this case.

    That said, my point stands. Forcing users to update immediately isn't realistic, for reasons I've already stated.

    To date Discord is the only app I've used that does this.

    6
    댓글 작업 고유 링크
  • Johnanater

    Agreed

    2
    댓글 작업 고유 링크
  • tobyblack

    I totally agree to taktician. It makes using discord for Linux users even worse. It is not user-friendly!
    @Discord: You won't make any friends with something like this! You destroy a part of what makes Linux better than everything else.

    6
    댓글 작업 고유 링크
  • exapsy

    Yes it kind of seems like Linux users are treated as B-Class citizens all over the place. First the Share Screen doesn't work properly on multimonitor but initially it didnt work at all for a few months. Now I cant even open Discord at all because there's an update that I cant skip which isn't even available for me? I mean, let's not use Discord at all, if its going to treat us like that. Because I dont wanna wait on every update "a few days" (quoted from the gentleman above) before I actually use Discord.


    I understand that I may not be fair in my judgement and douchy. But these kind of things make me kind of furious. Everything runs on Linux, yet the support on Linux from applications like Discord is weak and I cant see the reason why. I've been a premium member for like a year or 2 for Discord, if this is how they thank me then I might go to another valley.

    4
    댓글 작업 고유 링크
  • Skalli

    Yeah, this kind of policy sucks. I'm on Arch, so was lucky that the update just popped up. But others might not be so lucky.

    This is really a bad practice.

    0
    댓글 작업 고유 링크
  • Ken S

    well there is always team speak.I'm sure they would like the cash Linux brings to any table.

     

    1
    댓글 작업 고유 링크
  • Ken S

    thr update is now aviliable

    0
    댓글 작업 고유 링크
  • taktician

    I have to give Discord credit - they have one of the best Electron apps I've seen to date. The contrast between Discord and Slack, in terms of quality, is night and day.

    My issue here is that this is unprecedented, hard-coded, app-disabling functionality that serves no real purpose other than to frustrate their Linux userbase - some of which are paying to use it. It can take days if not weeks and even months for updates to propogate across an entire Linux userbase, and there are good reasons for this. A Linux app with an "upgrade now or die lol" policy doesn't make much sense.

    This is an easy fix - I hope they implement it soon. I'd hate for this to become a frequent occurance. I was considering upgrading to Nitro Classic for the HD screen sharing, as that's useful for my work... but I'm going to hold off until Discord can commit to fixing this.

    3
    댓글 작업 고유 링크
  • Blackthorn

    Pop shop doesn't have the new version. Not a great experience.

    0
    댓글 작업 고유 링크
  • MegaShinySnivy

    This issue still isn't resolved on Manjaro, and while I like that they have a tar.gz, manually installing a package is a world of pain. Why not give a .pkg.tar.zst instead? Then pacman should be able to handle an upgrade that way.

    1
    댓글 작업 고유 링크
  • ggoas

    This is not necessarily Discord's fault

    They want all of their users to be on the same release, but they do not control downstream's release schedule. I think there is area for compromise, ie. if discord were to give downstream 1-2 weeks to package the new version before they prevent logins with the prior release. But hey, I'm still waiting for the 2000 character limit to be increased.

    0
    댓글 작업 고유 링크
  • Mikachu

    You can manually bump the version number stored in resource/build_info.json and it will start up fine.

    2
    댓글 작업 고유 링크
  • Blackthorn

    @ggoas yes, that's all I'd want. They should give a bigger timeframe where older clients are allowed to connect. The old client was working just fine, but I wanted to restart my machine.

    Afterwards I spent an hour trying to get connected / trying to get sound working in Firefox so I rejoin my friends in MC. :(

    0
    댓글 작업 고유 링크
  • Blackthorn

    @Mikachu: Thanks! Worked for me. Here is what I did:

    # Find discord directory:

    ls -la `which discord`
    lrwxrwxrwx 1 root root 24 Mar 7 2019 /usr/bin/discord -> ../share/discord/Discord

    # find and update JSON file using sed command

    find /usr/share/discord -name build_info.json -exec sudo sed -i.orig 's/\.9/\.10/' {} \;

    # display both the updated JSON and backup ( original )

    find /usr/share/discord -name build_info.* -ls -exec cat {} \; -exec echo \;
    4325594 4 -rw-r--r-- 1 root root 56 Feb 26 06:54 /usr/share/discord/resources/build_info.json
    {
    "releaseChannel": "stable",
    "version": "0.0.10"
    }
    4325980 4 -rw-r--r-- 1 root root 55 Mar 7 2019 /usr/share/discord/resources/build_info.json.orig
    {
    "releaseChannel": "stable",
    "version": "0.0.9"
    }

     

    # start discord now

    2
    댓글 작업 고유 링크
  • epiK

    How should i edit the file to make it work? and what file.the .orig one or the other one or both

    0
    댓글 작업 고유 링크
  • Blackthorn

    @epiK the orig is the original one, I use sed to make a backup just in case. After you run sed you should have version 0.0.10 in build_info.json and you are done. When the real 10 is available in your package manager of choice it will overwrite this file.

    It should be fine to delete the original, but in case some people have more stuff in their build-info.json I thought it was a good idea to keep a copy.

    0
    댓글 작업 고유 링크
  • J_tech0

    Discord has now been updated in the Arch community package database (less than 15 mins ago as of writing) so it should update to the correct version now, but you might need to tell pacman to sync package databases first.
    I do agree that there should be a longer transition window to allow those using linux package managers to keep up though...

    1
    댓글 작업 고유 링크
  • TLoD_Snake

    Agree. Can't use Discord on my Gentoo anymore, there is no 0.0.10 in Portage yet.

    0
    댓글 작업 고유 링크
  • AntOfThy

    The thing is... I have multiple machines, so while I can't start a Discord on one machine because there is a newer version available.   The discord that is still running on a different machine, continues to run perfectly fine.

    In other words, there is no reason why the old one can run for a period.  Discord just does not let the user run it until they upgrade...   Very anti-social that!

    This is with Fedora 31, system install.  Had to install a second 'personal' one for a few days, until the update became available.  Waste of personal disk space, time, and energy!  When a little slack in allowing the use of older version would have fixed the problem.

    Arrgghhh....   Pull out hair...  Hmm...  What hair!

    Hmmm... Nice alternative to fool the older discord in thinking it is the newer one!

    1
    댓글 작업 고유 링크

댓글을 남기려면 로그인하세요.