Closed maacl closed 3 years ago
Thanks for reporting this issue, I think I fixed something quite similar to this for the edge channel recently so I'll take a look at this when I'm next in front of the computer, that may not be until Tuesday next week but will let you know as soon as I can.
OK, so maybe edge would work?
On Fri, Apr 23, 2021 at 3:45 PM Alex Murray @.***> wrote:
Thanks for reporting this issue, I think I fixed something quite similar to this for the edge channel recently so I'll take a look at this when I'm next in front of the computer, that may not be until Tuesday next week but will let you know as soon as I can.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexmurray/emacs-snap/issues/29#issuecomment-825669444, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPUXBY53A6TP673PXKIODTKF2ZJANCNFSM43ONXINA .
For info I get same error when installing:
sudo snap install emacs --channel=latest/edge --classic
On Fri, Apr 23, 2021 at 4:29 PM Martin Clausen @.***> wrote:
OK, so maybe edge would work?
On Fri, Apr 23, 2021 at 3:45 PM Alex Murray @.***> wrote:
Thanks for reporting this issue, I think I fixed something quite similar to this for the edge channel recently so I'll take a look at this when I'm next in front of the computer, that may not be until Tuesday next week but will let you know as soon as I can.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexmurray/emacs-snap/issues/29#issuecomment-825669444, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPUXBY53A6TP673PXKIODTKF2ZJANCNFSM43ONXINA .
Hmm I can't reproduce this myself on my local Ubuntu 21.04 machine but I will try later in a freshly installed VM to see if I can reproduce it further.
OK, let me know if I can provide further info. This was tested on a clean Hyper V Ubuntu 21.04 vm.
Ok so I can reproduce this and I see these messages printed on startup but it does not appear to have a material impact - we already set GIO_MODULE_DIR
to try and avoid this sort of thing (ie a mismatch between the host gio modules and the ones shipped inside the emacs snap) so I am not sure there is much else to be done here. Can you confirm whether emacs is functioning correctly even when you see these messages?
I can confirm that emacs appears to work correctly despite these messages.
Ok let's leave this issue open for now since I think I would still like to try and find a way to avoid this as it's definitely a bit scary even if it doesn't affect the functionality of emacs.
OK, let me know if you want me to verify any fixes.
On Thu, Apr 29, 2021 at 9:06 AM Alex Murray @.***> wrote:
Ok let's leave this issue open for now since I think I would still like to try and find a way to avoid this as it's definitely a bit scary even if it doesn't affect the functionality of emacs.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexmurray/emacs-snap/issues/29#issuecomment-828991899, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPUXHT2BY34NMO7J7XCG3TLEARBANCNFSM43ONXINA .
This should be fixed by 482b944 on master and ecce32c on snapshot (aka edge) - so once the snap rebuilds in a couple hours then I hope this will be resolved.
Cool I will verify later today.
On Fri, Apr 30, 2021 at 9:09 AM Alex Murray @.***> wrote:
This should be fixed by 482b944 https://github.com/alexmurray/emacs-snap/commit/482b9449d48c4be3af331ae6eb9e751ee4d9e2d6 on master and ecce32c https://github.com/alexmurray/emacs-snap/commit/ecce32c86bf28f2a0426fbce5ecff552ff52a708 on snapshot (aka edge) - so once the snap rebuilds in a couple hours then I hope this will be resolved.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexmurray/emacs-snap/issues/29#issuecomment-829890866, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPUXEPX5RPQBS6BCRJPRDTLJJSLANCNFSM43ONXINA .
It is still giving the same error as of 20 mins. ago.
On Fri, Apr 30, 2021 at 9:23 AM Martin Clausen @.***> wrote:
Cool I will verify later today.
On Fri, Apr 30, 2021 at 9:09 AM Alex Murray @.***> wrote:
This should be fixed by 482b944 https://github.com/alexmurray/emacs-snap/commit/482b9449d48c4be3af331ae6eb9e751ee4d9e2d6 on master and ecce32c https://github.com/alexmurray/emacs-snap/commit/ecce32c86bf28f2a0426fbce5ecff552ff52a708 on snapshot (aka edge) - so once the snap rebuilds in a couple hours then I hope this will be resolved.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexmurray/emacs-snap/issues/29#issuecomment-829890866, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPUXEPX5RPQBS6BCRJPRDTLJJSLANCNFSM43ONXINA .
Yeah I was hoping the new builds would be done by now but they are taking longer than expected - hopefully will be done in another hour or two perhaps
@maacl builds are now done - can you confirm if this is fixed for you via the emacs 27.2 build on the beta channel or the 28.0.50 build on edge?
I can confirm that this now runs cleanly on a fresh Hyper V Ubuntu 20.04 VM. Thanks.
No worries, thanks for reporting the issue in the first place.
Hello @alexmurray , After upgrading Ubuntu from 20.04 to 21.04 I am getting the above message and in some cases, Emacs just freeze on a white screen. I have also removed and installed again Emacs but it remains the same. Any help?
@EvanMath apologies, I had forgotten to promote the fixed builds from the beta to the stable channel - this is now fixed on the stable channel as well.
I've just encountered this error with emacs beta channel on Ubuntu 23.04.
I get the bellow errors when starting emacs after install on Ubuntu 21.04: