Bug 703532
| Summary: | im-chooser Version mismatch Unable to communicate to IMSettings services | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | wengxufeng |
| Component: | im-chooser | Assignee: | Akira TAGOH <tagoh> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | i18n-bugs, sunshine1914, tagoh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-07 09:46:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
wengxufeng
2011-05-10 15:35:39 UTC
Assuming you've updated from the older version of imsettings, you have to restart the desktop at least. once you restart your desktop and you don't see this issue again, this is not a bug at all. (In reply to comment #1) > Assuming you've updated from the older version of imsettings, you have to > restart the desktop at least. once you restart your desktop and you don't see > this issue again, this is not a bug at all. I have already rebooted my computer many times. It doesn't work. Can you attach your $HOME/.imsettings.log? Sorry, I can't access my computer now. (In reply to comment #3) > Can you attach your $HOME/.imsettings.log? Here is my ./imsettings.log. imsettings information ========================== Is DBus enabled: yes Is imsettings enabled: yes Is GTK+ supported: no Is Qt supported: no DESKTOP_SESSION: gnome DISABLE_IMSETTINGS: IMSETTINGS_DISABLE_DESKTOP_CHECK: DBUS_SESSION_BUS_ADDRESS: unix:abstract=/tmp/dbus-IzKEOzUsuT,guid=ff5fdf9a6d3c9ffd4aa675e9000000c6 GTK_IM_MODULE: ibus QT_IM_MODULE: xim XMODIFIERS: @im=ibus IMSETTINGS_MODULE: IBus IMSETTINGS_INTEGRATE_DESKTOP: yes (In reply to comment #3) > Can you attach your $HOME/.imsettings.log? Ok, I guess you don't have imsettings-daemon running. what if you run "/usr/libexec/imsettings-daemon --replace" on the terminal and run im-chooser say? "Version mismatch" would be the side effect of failing an access through DBus. it looks weird to me since your desktop certainly is running under the dbus session. I get this error when I run "/usr/libexec/imsettings-daemon --replace" . /usr/libexec/imsettings-daemon: symbol lookup error: /usr/lib64/libnotify.so.4: undefined symbol: gdk_screen_make_display_name Is there any way to make the desktop not run under the dbus session ? (In reply to comment #6) > Ok, I guess you don't have imsettings-daemon running. what if you run > "/usr/libexec/imsettings-daemon --replace" on the terminal and run im-chooser > say? > > "Version mismatch" would be the side effect of failing an access through DBus. > it looks weird to me since your desktop certainly is running under the dbus > session. (In reply to comment #7) > I get this error when I run "/usr/libexec/imsettings-daemon --replace" . > > /usr/libexec/imsettings-daemon: symbol lookup error: /usr/lib64/libnotify.so.4: > undefined symbol: gdk_screen_make_display_name That looks like you broke gtk+. if you have any libraries self-built on /usr/local or such, remove it. otherwise reinstall gtk+. > Is there any way to make the desktop not run under the dbus session ? Nope. Ping? guess you've got resolved this issue with the above. closing this so far. please reopen if you still see this. You can change the Python version for 2.6(Python2.6). wrong bug? no python code in im-chooser nor imsettings though |