Date: Mon, 27 Jan 2014 17:30:02 +0400 From: "Marat N.Afanasyev" <amarat@li.ru> To: freebsd-multimedia@FreeBSD.org Cc: freebsd-gnome@freebsd.org Subject: Re: strange behaviour of audacious Message-ID: <52E65F5A.9010500@li.ru> In-Reply-To: <52E39B5C.8000402@li.ru> References: <52E25BF3.5000203@li.ru> <52E39B5C.8000402@li.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Marat N.Afanasyev wrote: > Marat N.Afanasyev wrote: >> Hello! >> >> I have a very strange behaviour of multimedia/audacious that can be >> described as 'one-click-dialog'. After starting audacious it cannot run >> even one dialog completely, opening dialog and clicking on any active >> element leads to all other elements being irresponsible, e.g. opening >> global Preferences and then Output Plugin Preferences gives me totally >> unusable "OSS4 Output Settings" dialog that can be only closed by WM >> close button, and everything is like this. >> >> PS. I don't subscribed to ml yet, so, if you want to answer me, CC: to >> me too >> > It seems that latest transmission has the same kind of problem, in > settings dialog for torrent 'Close' button works if, and only if it was > the first element to click. If I click on somewhere else, I can close > this dialog only using WM's 'Close' button > And more. Both multimedia/audacious and net-p2p/transmission-gtk interfaces ignore key/mouse events after first click, but if I switch workspace there and back again they process next event. I found that something similar to my case was happening in evince3 https://bbs.archlinux.org/viewtopic.php?pid=1305904#p1305904 but there's no solution also. I suppose that this is a very rare and strange problem, so I wonder how can I debug event passing to gtk3 windows to make conditions when this problem is happening as clear as possible. -- SY, Marat [-- Attachment #2 --] 0 *H 010 + 0 *H i0-0m0 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 130829080313Z 140829193716Z0O10U IsC164JG3dq5RPEQ10Uamarat@li.ru10 *H amarat@li.ru0"0 *H 0 OTOZo") Oc3>_m.'buު-a>EF!tln>N6\j}KvIJuyck@I:{iͦ]/:[2'nϫ"k4*&P`R}&\00쇒3訵mj!!H9]IP/b2nka3ZrMrKw&҇7I6gZ5\Kʣ~߮fα 00 U0 0U0U%0++0U,Vay'S#0U#0Sr풜\|~5NԸQ0U0amarat@li.ru0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0 *H ;QewY}qcC<LӐHX~4)b<%83]2>^Ѝq\)Dq?V^^; 4'| m6ϒZDDaJ2 )h{b=i0^J;RPYlY?)Qt)a}^a, 7VZnu.YZ2)9>ye /qXO4Tw[8,Ԍz9^*:@_Ǡ,0{0400 *H 0}10 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o-we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&
