glib2: revert latest changes to get back to working version 2.74.0#23459
glib2: revert latest changes to get back to working version 2.74.0#23459feckert merged 4 commits intoopenwrt:masterfrom
Conversation
This is must also get revert to get back to working glib2 version 2.74.0 Signed-off-by: Florian Eckert <fe@dev.tdt.de> This reverts commit 9f57ef2.
So that we have a working ModemManager again and can look at the problem revert the update to version 2.78.4 for now. Signed-off-by: Florian Eckert <fe@dev.tdt.de> This reverts commit 08c7b0d.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
feckert
force-pushed
the
pr/20240216-glib2
branch
from
f2c4d20 to
5618854
Compare
|
Is version 2.80.0 better in this regard? |
|
@yegorich Difficult to say. I haven't tried it yet. In principle, we should update. But if, for example, the modem manager no longer works, as this was the case on last update try, then we could not update the glib2. |
|
@feckert I have the same issue with MM not being able to register DBus profile with 2.80.x :-( |
|
@yegorich thanks for the testing the upgrade to the latest glib2. |
|
I opened the related issue: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/849 |
|
@feckert could you test my PR: #23951 Looks like the problem is the default runtime_dir introduced in https://gitlab.gnome.org/GNOME/glib/-/commit/30995f9dd7c24314c362a3e30102b89196bcef84 |
2 participants
Maintainer: @neheb
Compile tested: lantiq_xrx200 and x86_64
Run tested: x86_64, APU3 with modemmanager
Description: