Ticket #438 (closed defect: fixed)
problem gnome-config->dbus
| Reported by: | TDTwister | Owned by: | spaetz |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Package requests | Version: | SHR-testing |
| Keywords: | Cc: |
Description (last modified by dos) (diff)
Hi!
I discovered that many applications that use gnome config are unable store and retrieve any settings. I traced the problem to the dbus (1.2.1) recipe that does not include the dbus-launch binary to the image. I compiled and install that file manually and it seems that it has resolve the issue. I have also inform the FSO for this problem as the FSO image have identical behavior.
Thank you!
Change History
comment:2 in reply to: ↑ 1 Changed 4 years ago by TDTwister
Replying to dos:
Have you tried installing dbus-x11?
No but shouldn't that file been included in the default image in the first place?
comment:3 follow-up: ↓ 4 Changed 4 years ago by dos
- Description modified (diff)
Please do "opkg install dbus-x11" and check, if it's fixing this issue. If it's fixing, then I'll add dbus-x11 to image.
comment:4 in reply to: ↑ 3 Changed 4 years ago by TDTwister
Replying to dos:
Please do "opkg install dbus-x11" and check, if it's fixing this issue. If it's fixing, then I'll add dbus-x11 to image.
I could not test what you told me as at this time I am using FSO and it seems that it does not have that particular package in the repository. I can't re install SHR to test is as I need the phone with this configuration for a few days.
I have looked at package dbus-x11_1.2.1-r8_armv4t.opk from OM2008.8 repository and it contains the dbus-launch file so I am 99% sure that it will fix the problem.
I also find this bug report http://docs.openmoko.org/trac/ticket/2109 that is relative with the issue. I think that was the reason dbus-launch was removed from the dbus package in the first place.
comment:5 Changed 4 years ago by TDTwister
I will get back to you with what happen after I run the command some time nextweek
comment:6 Changed 4 years ago by dos
- Owner changed from ainulindale to spaetz
- Component changed from SHR Image to package requests
comment:7 Changed 4 years ago by TDTwister
Sorry for the delay. Yes it does solve the problem if you install dbus-x11.
comment:8 Changed 4 years ago by spaetz
According to AInulindale and I agree with that, the correct solution is to have those packages that depend on dbus-launch to include the dependency to "dbus-x11" directly in the recipe rather than unconditionally adding it to the image.
Is there a specific (or several specific applications/recipes) that need dbus-launch? I'll add the dependency directly to them then. Otherwise we'll close this ticket in some time in the future. Hope that approach is ok to you, TDTwister
Have you tried installing dbus-x11?