[Bug 2029361] Re: evolution does not start

2023-08-29 Thread Christian Adam
Hi all, I'm also affected on both a 22.04 desktop upgraded ever since and a 22.04 laptop with an inital install of 22.04. My ~./bashrc and ~./profile were never changed, renaming them or copying the version from /etc/skel did not solve the issue for me. Strangely, only my user profile with

[Bug 2029361] Re: evolution does not start

2023-08-29 Thread Christian Adam
Hi all, unfortunately, I have the same problem with that update, but renaming ~/.profile and ~/.bashrc does not help. Anyway, I never did custom changes to these files. The problem occurs both on my desktop (upgraded ever since) and my laptop (clean install of 22.04). I did not post earlier as

[Bug 2029361] Re: evolution does not start

2023-08-02 Thread Marc Deslauriers
I'm glad you figured it out, thanks for updating the bug! I'll close it now since this looks like a configuration issue. ** Changed in: evolution (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 2029361] Re: evolution does not start

2023-08-02 Thread Axel G. Rossberg
The problem was caused by a line export LD_LIBRARY_PATH=".:$LD_LIBRARY_PATH" in my ~/.profile file. Oddly, when I then used ldd to compare the dynamic libraries used by /usr/bin/evolution in the case where evolution works with the case where evolution fails, they are exactly the same.

[Bug 2029361] Re: evolution does not start

2023-08-02 Thread Axel G. Rossberg
I did as you suggested, but this did not fix the problem. However, then I tried renaming my "~/.profile" and "~/.bashrc" files and this solved the problem. Should I be able to figure our which environmental variable interfered with evolution, I'll report back. -- You received this bug

[Bug 2029361] Re: evolution does not start

2023-08-02 Thread Marc Deslauriers
Hi, Thanks for reporting this issue. I can't seem to reproduce this issue on Ubuntu 22.04. I do see the "WEBKIT_FORCE_SANDBOX no longer allows disabling the sandbox." message, which is normal since that workaround is no longer required, but evolution starts fine and works as expected. Could you