** Changed in: libgtk
Importance: Unknown = Medium
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: libgtk
Status: Unknown = Fix Released
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package gtk+2.0 - 2.17.3-0ubuntu1
---
gtk+2.0 (2.17.3-0ubuntu1) karmic; urgency=low
* New upstream version:
GtkFileChooser:
- Shows the size column by default now
GtkStatusIcon:
- Has a title property, which can be used by ATs when they
** Package changed: evolution (Ubuntu) = gtk+2.0 (Ubuntu)
** Changed in: gtk+2.0 (Ubuntu)
Status: In Progress = Fix Committed
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs,
Matthias Clasen from Red Hat tackled the underlying gtk+ bug (
http://bugzilla.gnome.org/show_bug.cgi?id=585626 ) and has committed a
patch to gtk+ head that dramatically improves things.
See the gtk+ bug I've linked to for his patch, and some instructions
I've written on easily applying the fix
** Bug watch added: GNOME Bug Tracker #585624
http://bugzilla.gnome.org/show_bug.cgi?id=585624
** Also affects: evolution via
http://bugzilla.gnome.org/show_bug.cgi?id=585624
Importance: Unknown
Status: Unknown
--
Long delay before new/compose window appears
** Changed in: evolution
Status: Unknown = New
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Cloning my comment from the GNOME bug, since I've identified pretty much
exactly what factor controls whether or not this issue happens:
If you enable your local X server to listen on TCP/IP (on most GNOME desktops,
edit /etc/gdm/gdm.conf (may be /etc/X11/gdm/gdm.conf depending on
** Bug watch added: GNOME Bug Tracker #585626
http://bugzilla.gnome.org/show_bug.cgi?id=585626
** Also affects: gtkhtml via
http://bugzilla.gnome.org/show_bug.cgi?id=585626
Importance: Unknown
Status: Unknown
--
Long delay before new/compose window appears
** Changed in: gtkhtml
Status: Unknown = New
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Quick gtkhtml hack/workaround
http://launchpadlibrarian.net/27859768/bug585626.diff
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It's a gtkhtml bug, or possibly a libgtk+ bug.
A workaround is to patch libgtkhtml and rebuild it. Instructions:
$ sudo apt-get install fakeroot build-essential wget
$ sudo apt-get build-dep gtkhtml3.14
$ mkdir $HOME/gtkhtml
$ cd $HOME/gtkhtml
$ apt-get source gtkhtml3.14
$ wget
** Changed in: evolution (Ubuntu)
Status: New = Triaged
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
Usually such bugs are due to tracker or non local or broken bookmarks
but the stacktrace
** Attachment added: libpcap format protocol trace of X11 network comms during
compose window open.
http://launchpadlibrarian.net/27805425/trace.pcap
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a
To examine the libpcap trace, open it with Wireshark, right-click on the
first packet, and choose Decode as. In the window that appears select
the Transport tab, then the X11 protocol in the list. Hit apply,
then close.
You'll now see the decoded X11 traffic. (Note that this traffic is for
the
** Attachment added: tcpdump of x11 traffic for whole X session during compose
window open
http://launchpadlibrarian.net/27805934/trace.pcap
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of
** Attachment added: Repeated grab/pointer query messages
http://launchpadlibrarian.net/27805937/trace_repeated_section.txt
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've attached a better trace now. It contains a full Evolution session
from start to finish, and excludes X11 traffic from the rest of the
desktop. I used `netstat' to see which clients were connected to the
Xephyr server before starting evo, fired up a tcpdump, started evo, did
the testing, used
In the trace attached to the last comment, the new button click is
packet 3664 at 11:37:30.98 . The window appears, as noted, around
11:37:47.
The attached graph and the one in the next comment show I/O in
packets/second and bytes/second during this period.
** Attachment added: I/O, bytes per
** Attachment added: I/O, packets per second, during session (evo traffic
only)
http://launchpadlibrarian.net/27806288/iograph_evoonly_packets.png
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a
As you can see the packets per second graph is rather more interesting.
When we look at what the traffic actually is (note: using view - time
display format - time of day is useful), it's possible to see the same
sequence of packets repeated during the long delay:
(C: client; S: server)
C - S:
** Attachment added: Repeated section, evo only traffic, one repeat (pcap)
http://launchpadlibrarian.net/27806581/trace_repeated_section.pcap
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of
Forgot to mention:
libx11-6
2:1.1.99.2-1ubuntu2
libgtk2.0-0
2.16.1-0ubuntu2
libglib2.0-0
2.20.1-0ubuntu2
running kernel: 2.6.28-11-server
--
Long delay before new/compose window appears
https://bugs.launchpad.net/bugs/386199
You received this bug notification because you are a member of
A sequence of backtraces taken across all threads while waiting for the
compose window to appear.
I can do more specific, or controlled, debugging if someone can offer a
suggestion as to where to start. Right now, I don't know evo's guts well
enough to have much idea, though I haven't yet dug
25 matches
Mail list logo