Description of problem: Just launching meld gives this error. I tried both normally on the command line, and with "rpmconf -a --frontend=meld". Version-Release number of selected component: meld-1.7.0-6.fc18 Additional info: cmdline: python /usr/bin/meld /etc/tor/torrc /etc/tor/torrc.rpmnew executable: /usr/bin/meld kernel: 3.8.1-201.fc18.x86_64 uid: 0 Truncated backtrace: prefs.py:93:__init__:GError: Nessun demone D-BUS in esecuzione Traceback (most recent call last): File "/usr/bin/meld", line 154, in <module> main() File "/usr/bin/meld", line 136, in main import meld.meldapp File "/usr/share/meld/meld/meldapp.py", line 216, in <module> app = MeldApp() File "/usr/share/meld/meld/meldapp.py", line 113, in __init__ self.prefs = preferences.MeldPreferences() File "/usr/share/meld/meld/preferences.py", line 259, in __init__ super(MeldPreferences, self).__init__("/apps/meld", self.defaults) File "/usr/share/meld/meld/util/prefs.py", line 93, in __init__ self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE) GError: Nessun demone D-BUS in esecuzione Local variables in innermost frame: rootkey: '/apps/meld' initial: {'use_custom_font': <meld.util.prefs.Value object at 0xef4a70>, 'statusbar_visible': <meld.util.prefs.Value object at 0xf8e1b8>, 'custom_font': <meld.util.prefs.Value object at 0xef4560>, 'use_syntax_highlighting': <meld.util.prefs.Value object at 0xef4ef0>, 'text_codecs': <meld.util.prefs.Value object at 0xf85c68>, 'filters': <meld.util.prefs.Value object at 0xf85e18>, 'show_line_numbers': <meld.util.prefs.Value object at 0xef4e60>, 'spaces_instead_of_tabs': <meld.util.prefs.Value object at 0xef4e18>, 'edit_command_custom': <meld.util.prefs.Value object at 0xef4fc8>, 'regexes': <meld.util.prefs.Value object at 0xf85dd0>, 'tab_size': <meld.util.prefs.Value object at 0xef4dd0>, 'show_whitespace': <meld.util.prefs.Value object at 0xef4ea8>, 'edit_wrap_lines': <meld.util.prefs.Value object at 0xef4f38>, 'ignore_blank_lines': <meld.util.prefs.Value object at 0xf8e128>, 'window_size_x': <meld.util.prefs.Value object at 0xef0050>, 'window_size_y': <meld.util.prefs.Value object at 0xef43b0>, 'vc_status_filters': <meld.util.prefs.Value object at 0xf8e248>, 'edit_command_type': <meld.util.prefs.Value object at 0xef4f80>, 'toolbar_visible': <meld.util.prefs.Value object at 0xf8e170>, 'dir_status_filters': <meld.util.prefs.Value object at 0xf8e200>, 'ignore_symlinks': <meld.util.prefs.Value object at 0xf85c20>, 'vc_console_visible': <meld.util.prefs.Value object at 0xf85cf8>} self: <meld.preferences.MeldPreferences object at 0xda3cd0>
Created attachment 705994 [details] File: backtrace
Created attachment 705995 [details] File: core_backtrace
Created attachment 705996 [details] File: environ
Created attachment 705997 [details] File: smolt_data
I should say that this is a problem because I am trying to run meld in a terminal, after doing "su" and becoming root.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.