Hi Vasily,
The tool is crashing when I open in servers with RealVNC. So, I have tested in servers with TigerVNC and surprisingly it's not crashing. However, the functionality doesn't work:
When I try to open file comparison and select file, the meld is not crashing, but I can see the error in the background:
** (meld:25229): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Traceback (most recent call last):
File "/NFS_share/meld/meld_3_16_0/lib/python2.7/site-packages/meld/sourceview.py", line 154, in __init__
self.on_setting_changed(meldsettings, 'style-scheme')
File "/NFS_share/meld/meld_3_16_0/lib/python2.7/site-packages/meld/sourceview.py", line 180, in on_setting_changed
"meld:current-line-highlight", "background")
File "/NFS_share/meld/meld_3_16_0/lib/python2.7/site-packages/meld/misc.py", line 189, in colour_lookup_with_fallback
style = source_style.get_style(name)
AttributeError: 'NoneType' object has no attribute 'get_style'
As you can see, source_style seems to be a None object.
def colour_lookup_with_fallback(name, attribute):
from meld.settings import meldsettings
source_style = meldsettings.style_scheme
So meldsettings.style_scheme returns None.
The following is the definition (removed unnecessary declarations here):
meldsettings = MeldSettings()
class MeldSettings(GObject.GObject):
def __init__(self):
GObject.GObject.__init__(self)
self.style_scheme = self._style_scheme_from_gsettings()
def _style_scheme_from_gsettings(self):
manager = GtkSource.StyleSchemeManager.get_default()
return manager.get_scheme(settings.get_string('style-scheme'))
I am not much into Python. But as you can see meldsettings=MeldSettings() (there is no argument).
But MeldSettings is expecting an argument GObject.GObject in the definition. How can it be?
Ok, let's say argument is not needed and I have done some debugging and found that get_string used in style_scheme_from_gsettings definition is not defined anywhere.
May be it is due to the warning I am receiving in the beginning:
** (meld:25229): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
I found that in a new python shell:
import meld.settings generates the above error. Is it somehow linked to the get_string method?
I vaguely remember I have fixed the same issue last time or maybe not.
Regards,
Jeevan.
-----Original Message-----
From: Jeevan Behara Patnaik (GIS)
Sent: Wednesday, June 15, 2016 6:25 PM
To: 'Vasily Galkin'; meld-***@gnome.org
Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R (Product Engineering Service)
Subject: RE: Re:meld crashing vnc on starting
Hi,
After installing gsettings-desktop-schemas, meld is not crashing.
Now, the issue is with vnc in both the servers.
I am trying to install the debug package as you have suggested. Issue with repos. Let's see.
Thanks so much.
Regards,
Jeevan.
-----Original Message-----
From: Vasily Galkin [mailto:galkin-***@yandex.ru]
Sent: Tuesday, June 14, 2016 6:20 PM
To: Jeevan Behara Patnaik (GIS)
Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R (Product Engineering Service); meld-***@gnome.org
Subject: Re:meld crashing vnc on starting
** This mail has been sent from an external source **
The org.gnome.desktop.interface.gschema.xml is absent in your current install, and was present in your previous install - this is the reason that meld is crashing now.
Unfortunately I'm not gtk packaging/installation expert, the only thing I know - in debian this file is result of building this source package https://packages.debian.org/source/jessie/gsettings-desktop-schemas
Maybe you can just (fast&unsupported) copy this xml from previous install.
About Xvnc crash during meld start: It looks that your Xvnc binary lacks the debugging information.
What is exact package version it is? I think it can be found via rpm -q --whatprovides /usr/bin/Xvnc
You have somehow to get debuginfo installed for Xvnc binary, maybe this helps after finding pa - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/intro.debuginfo.html
(I think that you need install tigervnc-debuginfo, but i'm not sure) Otherwise, you can try recompiling Xvnc from binaries with debug info and try to reproduce crash on it.
Note: the debugging symbols and the crash information from log must correspond to exactly same binary. So, if you recompile/reinstall binary - you need to get new crash information.
The result of addr2line for correctly found debug symbols expected to be some Xvnc's source filename and line number.
--
Best regards, Vasily
> Hi Vasily,
>
> Thanks for the suggestions.
>
> I have the following in the current schema directory:
> gschema.dtd
> org.gnome.meld.gschema.xml
> org.gtk.exampleapp.gschema.xml
> org.gtk.Settings.Debug.gschema.xml
> gschemas.compiled
> org.gtk.Demo.gschema.xml
> org.gtk.Settings.ColorChooser.gschema.xml
> org.gtk.Settings.FileChooser.gschema.xml
>
> And the following were in the previous installation schemas directory (which was 3 months ago - then I was able to invoke the tool, but the functionality was not working, as I installed the dependencies separately and so linking of some file failed. Hence I had to reinstall it again. And I see org.desktop.* xml files are there, I am not sure how I am missing those this time. Any idea?):
> gschema.dtd org.gnome.desktop.enums.xml
> org.gnome.desktop.thumbnail-cache.gschema.xml
> gschemas.compiled org.gnome.desktop.input-sources.gschema.xml
> org.gnome.desktop.thumbnailers.gschema.xml
> org.gnome.desktop.a11y.applications.gschema.xml
> org.gnome.desktop.interface.gschema.xml
> org.gnome.desktop.wm.keybindings.gschema.xml
> org.gnome.desktop.a11y.gschema.xml
> org.gnome.desktop.lockdown.gschema.xml
> org.gnome.desktop.wm.preferences.gschema.xml
> org.gnome.desktop.a11y.keyboard.gschema.xml
> org.gnome.desktop.media-handling.gschema.xml
> org.gnome.meld.gschema.xml
> org.gnome.desktop.a11y.magnifier.gschema.xml
> org.gnome.desktop.notifications.gschema.xml
> org.gnome.system.locale.gschema.xml
> org.gnome.desktop.a11y.mouse.gschema.xml
> org.gnome.desktop.privacy.gschema.xml
> org.gnome.system.proxy.gschema.xml
> org.gnome.desktop.app-folders.gschema.xml
> org.gnome.desktop.screensaver.gschema.xml org.gtk.Demo.gschema.xml
> org.gnome.desktop.background.gschema.xml
> org.gnome.desktop.search-providers.gschema.xml
> org.gtk.exampleapp.gschema.xml org.gnome.desktop.datetime.gschema.xml
> org.gnome.desktop.session.gschema.xml
> org.gtk.Settings.ColorChooser.gschema.xml
> org.gnome.desktop.default-applications.gschema.xml
> org.gnome.desktop.sound.gschema.xml
> org.gtk.Settings.FileChooser.gschema.xml
>
> Also the following is the output related Xvnc crash. p option, I had to remove, as it shows not recognized option:
> $echo 0x0000000000799561 | addr2line -Cfie /usr/bin/Xvnc ??
> ??:0
>
> Regards,
> Jeevan.
> -----Original Message-----
> From: Vasily Galkin [mailto:galkin-***@yandex.ru]
> Sent: 14 June 2016 16:04
> To: Jeevan Behara Patnaik (GIS)
> Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R
> (Product Engineering Service); meld-***@gnome.org
> Subject: Re:meld crashing vnc on starting
>
> ** This mail has been sent from an external source **
>
> Hi Jeevan.
>
> I'm successfully using recent meld with gtk 3.18 and 3.20.
> I think that 3.18 is the most tested with meld.
>
> About meld crash: now I noticed that dump is created after SIGTRAP (not SIGSEGV), so it's for sure the problem with gsettings schemas: according to glib's gio/gsettings.c absence of schema is non-recoverable error that exits application with SIGTRAP and message like yours GLib-GIO-ERROR **: Settings schema 'org.gnome.desktop.interface' is not installed.
> So dumps are not needed. According to your SO topic http://stackoverflow.com/questions/35784566/meld-glib-gio-error-no-gsettings-schemas-are-installed-on-the-system you have set GSETTINGS_SCHEMA_DIR to some nfs path.
> I think that for meld this directory must contain both
> org.gnome.meld.gschema.xml and org.gnome.desktop.interface.xml
>
> About Xvnc crash during meld start: The instruction of crash is known from Jun 9 09:28:43 oulnxc53 kernel: Xvnc[18978]: segfault at 18 ip 0000000000799561 sp 00007fffdead6e50 error 4 in Xvnc[400000+542000] It seems to be at offset 0x399561 out of 0x542000 code section of Xvnc binary.
>
> To minimally diagnose the issue further the exact code line of Xvnc (compiled/installed with debug symbols) is needed.
> You can try to extract it with echo 0x0000000000799561 | addr2line
> -Cfipe /path/to/Xvnc
>
> --
> Best regards, Vasily
>
>> Hi,
>>
>> I have decided to install meld again - both meld3.14.2 and meld3.16.0 in parallel.
>>
>> Please let me know which gtk+ version, I should install. In the requirements, it is mentioned 3.14.
>> But nowhere it is mentioned if it can support higher.
>>
>> Can I install or 3.14.8 or 3.14.15 or any version higher than 3.14.0?
>>
>> Regards,
>> Jeevan.
>>
>> -----Original Message-----
>> From: Jeevan Behara Patnaik (GIS)
>> Sent: 13 June 2016 17:28
>> To: 'Vasily Galkin'
>> Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R (Product Engineering Service); 'meld-***@gnome.org'
>> Subject: RE: Re:meld crashing vnc on starting
>>
>> Hi Vasily,
>>
>> And besides, any ideas why the vnc was crashing in the other server?
>>
>> Regards,
>> Jeevan.
>>
>> -----Original Message-----
>> From: Jeevan Behara Patnaik (GIS)
>> Sent: 13 June 2016 17:26
>> To: 'Vasily Galkin'
>> Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R
>> (Product Engineering Service); meld-***@gnome.org
>> Subject: RE: Re:meld crashing vnc on starting
>>
>> Hi Vasily,
>>
>> I tried to see the abrt dump.
>>
>> I found the following messages:
>> $cat reason
>> Process /NFS_share/python/python_2_7_11/bin/python2.7 was killed by
>> signal 5 (SIGTRAP)
>>
>> $cat var_log_messages
>> Jun 13 12:28:42 oulnxc54 abrt[28298]: Saved core dump of pid 28276
>> (/NFS_share/python/python_2_7_11/bin/python2.7) to
>> /var/spool/abrt/ccpp-2016-06-13-12:28:42-28276 (11911168 bytes) Jun
>> 13
>> 12:28:42 oulnxc54 abrtd: Executable
>> '/NFS_share/python/python_2_7_11/bin/python2.7' doesn't belong to any
>> package Jun 13 13:51:27 oulnxc54 abrt[5492]: Saved core dump of pid
>> 5491 (/NFS_share/python/python_2_7_11/bin/python2.7) to
>> /var/spool/abrt/ccpp-2016-06-13-13:51:27-5491 (11902976 bytes)
>>
>> Let me know how can I share you the whole ccpp directory. The compressed directory takes 11M.
>>
>> If it is issue with the installation of gsettings-desktop-schemas, it might be due to the fact that I installed it from other machine. I will try to read about it and fix it. But kindly let me know if you already have any ideas.
>>
>> Regards,
>> Jeevan.
>>
>> -----Original Message-----
>> From: Vasily Galkin [mailto:galkin-***@yandex.ru]
>> Sent: 11 June 2016 21:08
>> To: Jeevan Behara Patnaik (GIS)
>> Cc: Amit Kumar Singh (GIS); Shashidhar Basavanahally Shivarama R
>> (Product Engineering Service); meld-***@gnome.org
>> Subject: Re:meld crashing vnc on starting
>>
>> ** This mail has been sent from an external source **
>>
>> As far as I can understand in one case vnc server crashes and in the other meld is crashing.
>>
>> The message previous to "core dumped" says that meld crashing may be related to the problems with absence/bad install of "gsettings-desktop-schemas" package.
>>
>> For both crashes the following information can be helpful:
>> Line from var log messages with basic crash information (like you give it for Xvnc) Exact package versions of crashed module (Xvnc binary for Xvnc crash, some gtk lib for meld crash I think).
>> Core dump that is created for meld.
>>
>>> Hi Team,
>>>
>>> I have installed meld and when I try to invoke the meld binary, my vnc is crashing.
>>>
>>> 1.
>>> First of all, I have installed this on NFS share, including the
>>> dependencies like gtk etc., to be accessed across multiple machines
>>> (having similar configuration)
>>>
>>> OS: Redhat Linux 6.3
>>>
>>> 2.
>>> I have not started the dbus yet (which is also installed on shared
>>> NFS). The pid and lockfiles etc. however, installed locally (will
>>> start it individually in each server to avoid conflict)
>>>
>>> 3.
>>> So, I was starting meld without starting dbus. Could this be the reason for vnc crashing? The following are the errors, I see before the tool got crashing:
>>>
>>> In VNC of server1 (from where I have done all the compilation and installation, the vnc is crashing here and shows the following error before crash):
>>>
>>> * (meld:63603): WARNING **: Error retrieving accessibility bus
>>> address: org.freedesktop.DBus.Error.ServiceUnknown: The name
>>> org.a11y.Bus was not provided by any .service files
>>>
>>> Gtk-Message: Failed to load module "canberra-gtk-module"
>>>
>>> Gtk-Message: Failed to load module "canberra-gtk-module"
>>>
>>> GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
>>>
>>> I see the following messages in /var/log/messages:
>>>
>>> Jun 9 09:28:43 oulnxc53 kernel: Xvnc[18978]: segfault at 18 ip
>>> 0000000000799561 sp 00007fffdead6e50 error 4 in Xvnc[400000+542000]
>>>
>>> Jun 9 09:28:43 oulnxc53 gnome-keyring-daemon[19064]: dbus failure
>>> unregistering from session: Connection is closed
>>>
>>> Jun 9 09:28:43 oulnxc53 gnome-keyring-daemon[19064]: dbus failure
>>> unregistering from session: Connection is closed
>>>
>>> In VNC of server2 (I have not done installation here. It uses shared installation, the vnc is NOT crashing here. But tool unable to start and shows the following error):
>>>
>>> Gtk-Message: Failed to load module "canberra-gtk-module"
>>>
>>> Gtk-Message: Failed to load module "canberra-gtk-module"
>>>
>>> GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
>>>
>>> (meld:1083): GLib-GIO-ERROR **: Settings schema
>>> 'org.gnome.desktop.interface' is not installed
>>>
>>> Trace/breakpoint trap (core dumped)
>>>
>>> The following are the installation directories:
>>>
>>> bin etc include lib lib64 libexec sbin share var
>>>
>>> --
>>>
>>> Thanks and Regards,
>>>
>>> Jeevan Patnaik B
>>> | Project Engineer
>>>
>>> Nokia IT - HEE Platform |
>>> WIPRO Technologies - Hyderabad
>>>
>>> Mob: +91-9000607181
>>> | Off: +91-4030970347.
>>>
>>> The information contained in this electronic message and any
>>> attachments to this message are intended for the exclusive use of
>>> the
>>> addressee(s) and may contain proprietary, confidential or privileged
>>> information. If you are not the intended recipient, you should not
>>> disseminate, distribute or copy this e-mail. Please notify the
>>> sender immediately and destroy all copies of this message and any
>>> attachments. WARNING: Computer viruses can be transmitted via email.
>>> The recipient should check this email and any attachments for the
>>> presence of viruses. The company accepts no liability for any damage
>>> caused by any virus transmitted by this email. www.wipro.com
>>
>> The information contained in this electronic message and any
>> attachments to this message are intended for the exclusive use of the
>> addressee(s) and may contain proprietary, confidential or privileged
>> information. If you are not the intended recipient, you should not
>> disseminate, distribute or copy this e-mail. Please notify the sender
>> immediately and destroy all copies of this message and any
>> attachments. WARNING: Computer viruses can be transmitted via email.
>> The recipient should check this email and any attachments for the
>> presence of viruses. The company accepts no liability for any damage
>> caused by any virus transmitted by this email. www.wipro.com
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any
> attachments. WARNING: Computer viruses can be transmitted via email.
> The recipient should check this email and any attachments for the
> presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this email. www.wipro.com
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com