After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 783990 - Meld takes a long time to start
Meld takes a long time to start
Status: RESOLVED OBSOLETE
Product: meld
Classification: Other
Component: general
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2017-06-20 11:47 UTC by Jayesh Badwaik
Modified: 2017-12-13 19:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Excerpt of output of python2 -mtrace --trace /usr/bin/meld. (Full file cannot be attached as it was very big.) (5.43 KB, text/plain)
2017-06-20 11:47 UTC, Jayesh Badwaik
Details

Description Jayesh Badwaik 2017-06-20 11:47:01 UTC
Created attachment 354093 [details]
Excerpt of output of python2 -mtrace --trace /usr/bin/meld. (Full file cannot be attached as it was very big.)

I am using the following system:
1. OS: Archlinux
2. Plasma Display Manager (5.10.2)
3. Kwin Window Manager (5.10.2)
4. GTK2 2.24.31 

The meld application takes around than 25 seconds to show the window after entering the command on the command line. 

$ meld
(wait 25 seconds)
(see window)

I tried this command:

python2 -mtrace --trace /usr/bin/meld > output.txt

and I have attached the output.txt. The whole 25 seconds are spent waiting at the line 225187

__init__.py(39):         return getattr(self._introspection_module, name)


I would be happy to provide more information if needed. What else should I do to determine the problem?
Comment 1 Jayesh Badwaik 2017-06-20 11:50:18 UTC
I want to add that the problem even occurs on a fresh configuration of Plasma Display Manager but does not occur when using GNOME Display Manager.
Comment 2 Kai Willadsen 2017-06-23 21:18:35 UTC
I don't use KDE, so you'll have to help me out here. When you say "Plasma Display Manager" is that SDDM? or KDM?

Also, are they launching different sessions? I'm wondering whether this is an X11 vs Wayland issue.

Is there anything useful in the system journal? Specifically I'm looking for dbus errors or something like that.

If it sounds like I'm making wild guesses, it's because I am. I have no idea what's going on here, sorry.
Comment 3 Jayesh Badwaik 2017-07-19 16:20:21 UTC
Okay, so I cannot even reproduce this bug on my other computer, and it persists on first computer  inspite of both having ArchLinux and having installed exactly the same packages. So, I am completely confused as what can be the issue. 

In any case, the details are 
Display Manager: SDDM
Display Server: X11
Session: Plasma (X11)

What do you mean when you say different sessions? It is not a different session for sure. In any case, this problem looks completely non reproducible, so for now, I do not see any way to proceed on this. 

Thank you for your reply.
Comment 4 GNOME Infrastructure Team 2017-12-13 19:26:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/meld/issues/136.