You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distribuzione predefinita: Ubuntu-24.04
Versione predefinita: 2
uname -r shows 5.15.167.4 as kernel version
Did the problem occur during installation?
Yes
What happened?
launching Evolution on 24.04.1 I get the following error (that I didn'receive on 24.04.0)
(evolution:382): Gdk-WARNING **: 13:33:38.216: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 168 error_code 2 request_code 148 (GLX) minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
What was expected?
as in 22.04 and in 24.04.0 was, I'm expecting evolution to start without problems
Steps to reproduce
install Noble 24.04.1 (both from MS Store or directly from PWSH is the same)
run it and add
export LIBGL_ALWAYS_INDIRECT=1
sudo /etc/init.d/dbus start &> /dev/null
to .bashrc
create /etc/sudoers.d/dbus with the line: ALL = (root) NOPASSWD: /etc/init.d/dbus
install evolution and evolution-ews
from PWSH shutdown wsl then restart Ubuntu
launch evolution
Additional information
No response
The text was updated successfully, but these errors were encountered:
Partially solved by deleting export LIBGL_ALWAYS_INDIRECT=1 from .bashrc: now evolution starts without problems and I'm able to get access to IMAP mail; about ews mail (office365), I get
Failed to obtain access token from address “https://login.microsoftonline.com/[MSTenant here]/oauth2/v2.0/token”: Object does not exist at path “/org/freedesktop/secrets/collection/login”
Running seahorse, is clearly missing Login keyring and if I try to add it I get
Couldn't add keyring - no such secret collection at path /
exported Ubuntu-24.04 from a machine on which evolution worked w/o problems and run it with same results: no way to have it working.
It seems that with recent wsl updates something went wrong with Ubuntu keyring that's locked and on which is impossible doing anything (ssh and gpg are worlìking while is missing "Login" keyring and is impossible to create it)
Notice that wsl update on working machine and windows release are different from those on "buggy" machine; here working machine details
cmd /c ver
Microsoft Windows [Versione 10.0.22631.4460]
wsl --status
Distribuzione predefinita: Ubuntu-24.04
Versione predefinita: 2
Il sottosistema Windows per Linux è stato aggiornato l'ultima volta il 28/07/2024
(Windows Subsystem for Linux has been updated on 2024/07/28)
uname -r shows 5.10.16.3 as kernel version
cmd /c ver
Microsoft Windows [Versione 10.0.26100.2314]
wsl --status
Distribuzione predefinita: Ubuntu-24.04
Versione predefinita: 2
uname -r shows 5.15.167.4 as kernel version
Did the problem occur during installation?
What happened?
launching Evolution on 24.04.1 I get the following error (that I didn'receive on 24.04.0)
(evolution:382): Gdk-WARNING **: 13:33:38.216: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 168 error_code 2 request_code 148 (GLX) minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
What was expected?
as in 22.04 and in 24.04.0 was, I'm expecting evolution to start without problems
Steps to reproduce
export LIBGL_ALWAYS_INDIRECT=1
sudo /etc/init.d/dbus start &> /dev/null
to .bashrc
Additional information
No response
The text was updated successfully, but these errors were encountered: