Mailing List Archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [tlug] Weird problem with xine and KDE



>>>>> "Godwin" == Godwin Stewart <gstewart@example.com> writes:

    Godwin> If you hit "G" while xine is active it'll hide/show the
    Godwin> GUI. Hide the GUI and the CPU usage goes down to
    Godwin> normal. Show it again and CPU usage climbs back up to
    Godwin> 100%. The output window remains visible while I'm doing
    Godwin> this.  Hiding/showing the output window has no effect.

Well, now you have a workaround.  One point for the good guys.

Do the ConfigureNotify events stop when you hide the GUI?

    >> One thing this could be is an argument between xine and the
    >> "window manager" about the geometry of the xine window.  What
    >> is your general window manager?

    Godwin> I'm just using the KDE desktop (although I'm also
    Godwin> considering using something a little more lightweight).

Unfortunately I know more about KDE's licensing than I do about its
internals, but I can't imagine that it doesn't use a separate process
for window management.

    >> Does xine display a cool dynamic icon (such as an oscilloscope)
    >> in the kicker taskbar?

    Godwin> No, just a static icon.

Hm.  I wonder what kicker has to do with all this.  If it's not the
window manager, I don't see why it would care about one of xine's
toplevel windows.  (Jumping to conclusions here, but since hiding the
GUI makes kicker cool off, I think the connection is pretty strong.)

    >> Do you know which window it is,

    Godwin> Do I know which window /what/ is?

The one getting all the ConfigureNotify events.  Looks like it must be
the GUI, but it's worth confirming.  You can check that with xwininfo,
which gives the window id.  Could you give me a few more of those
events, in sequence?  Alternatively, if they're all identical except
for serial number, I think we can conclude that there's a knockdown
dragout brawl over window configuration going on for some reason.
Also, can you see a flicker or anything like that in the GUI?  Does
the GUI have a dynamic display in it?

At this point, I have to think that kicker or the kde library
functions that handle window geometry are buggy.

What seems to be going on here (GNOME has similar problems) is that
the desktop environment developers design (or maybe it's simply a
subset of Xt) their own protocols for session and window management
rather implement the full Xt protocol exactly.  This results in
programs written with a different toolkit getting screwed, because
they don't use exactly the protocol that the desktop expects.

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.


Home | Main Index | Thread Index

Home Page Mailing List Linux and Japan TLUG Members Links