Bug#753471: konqueror: Black picture when trying to play youtube videos using html5

2018-01-26 Thread Pali Rohár

Hi!

I fixed same problem on Debian Stretch by installing gstreamer1.0-libav and 
phonon-backend-gstreamer packages followed by system reboot.


It looks like there is a problem in KDE4/Qt4 version of Phonon to play mp4 
video contrainer and only gstreamer with libav plugin (libgstlibav.so) is 
able to do that for Phonon.


--
Pali Rohár
pali.ro...@gmail.com



Bug#866807: kopete: Can not connect due to missing auth-mechanism

2017-12-30 Thread Pali Rohár
On Sat, 01 Jul 2017 23:44:58 +0200 "Daniel 'DaB.' Baur" 
 wrote:

Package: kopete
Version: 4:16.08.1-3
Severity: important

Dear Maintainer,

I updated today from Debian Jessie to Debian Stretch. Unfortunantly now kopete 
is not long able to connect to my XMPP-accout at jabber.ccc.de :-(.

It worked perfectly before the update, and I did not changed my config – in 
fact: pidgig is still able to connect on my laptop (which was not updated yet).

Upon start, kopete tells me that “no appropriate authentication mechanism [is] 
avaible”. The XML-console tells me that PLAIN, X-OAUTH2 and SCRAM-SHA1 would be 
possible (see below).


http://jabber.org/protocol/caps"; node="http://www.process-one.net/en/ejabberd/"; 
ver="8TBgyHso9WGvSCtDfDqtKZKKD8E=" hash="sha-1"/>
http://jabber.org/features/iq-register"/>
http://jabber.org/features/compress";>
zlib


PLAIN
X-OAUTH2
SCRAM-SHA-1



I have the feeling that I miss a libary or something, but I could not find 
which. I also tried to start with a clean config, but it changed nothing.

Please tell me if I did something wrong, or you need more infos. 


Sincerely,
DaB.


Hi! Can you try *removing* QCA cyrus SASL plugin library and (re)start 
Kopete?


On 64bit system is it stored there:
/usr/lib/x86_64-linux-gnu/qca/crypto/libqca-cyrus-sasl.so

--
Pali Rohár
pali.ro...@gmail.com



Re: kopete+otr send messages unencrypted without notice

2016-12-19 Thread Pali Rohár
On Sat, 11 Jun 2016 17:43:14 +0200 Francois Gerin  
wrote:
> Subject: kopete+otr send messages unencrypted without notice
> Package: kopete
> Version: 4:4.14.1-2
> Justification: user security hole
> Severity: grave
> Tags: security upstream
> 
> Dear Maintainer,
> 
> Using kopete with OTR plugin lead to messages sent unencrypted without 
> notice. (I discovered this 
after sending sensitive credentials while helping some people remotely...)
> 
> After checking that OTR encryption was working ("private session started" 
> notice), I was helping 
people remotely while feeling secure. After a first restart of the other end 
computer, I saw a 
notification saying that OTR session was refreshed (which is normal$
> Later on, I detected that, in fact, the people at the other end were getting 
> all my messages 
unencrypted... despite of the notification I got on my end.
> First detection was done with "Opportunistic" policy on both sides. Then I 
> tested again with a 
full restart at both ends + "Always" policy for OTR plugin. Same result: when 
the other end restarts 
and I keep my session opened, I get the "OTR session refreshed"$
> 
> Several accounts credentials were sent in clear, among which for a root 
> account.
> 
> When I pay attention for the "OTR session refreshed" message, and especially 
> when "Always" policy 
is used on both sides, I would expect to be alerted that some internal issue 
canceled the 
encryption, no matters what's the reason.
> The notifications are not reliable, and we're talking about a secure 
> messaging system here 
(OTR)... This forced me to uninstall kopete, since I cannot rely on it for 
secure messaging.
> 
> Remarks:
>  - Two bugs already mention this in the bug tracking of kopete at 
https://bugs.kde.org/show_bug.cgi?id=274099 and 
https://bugs.kde.org/show_bug.cgi?id=362535
>  - While the kopete team cannot solve this (old) issue, I cannot believe 
> debian can go on 
propagating this dangerous thing and the heavy security consequences to the 
community, among which 
are key journalists.
>  - Until it is fixed, the OTR plugin should be disabled for kopete, or the 
> kopete UI should at 
least alert about its experimental support status in red uppercases.
> 
> Thanks a lot in advance for any action, to disable it or fix it!
> 
> 
> 
> 
> -- System Information:
> Debian Release: 8.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages kopete depends on:
> ii  kde-runtime 4:4.14.2-2
> ii  kdepim-runtime  4:4.14.2-3
> ii  libc6   2.19-18+deb8u4
> ii  libexpat1   2.1.0-6+deb8u3
> ii  libgadu31:1.12.0-5
> ii  libgif4 4.1.6-11+deb8u1
> ii  libglib2.0-02.42.1-1+b1
> ii  libidn111.29-1+deb8u1
> ii  libjasper1  1.900.1-debian1-2.4+deb8u1
> ii  libkabc44:4.14.2-2+b1
> ii  libkcmutils44:4.14.2-5
> ii  libkde3support4 4:4.14.2-5
> ii  libkdecore5 4:4.14.2-5
> ii  libkdeui5   4:4.14.2-5
> ii  libkdnssd4  4:4.14.2-5
> ii  libkemoticons4  4:4.14.2-5
> ii  libkhtml5   4:4.14.2-5
> ii  libkio5 4:4.14.2-5

Hi! This problem is fixed in Kopete 16.12.

Debian KDE team now needs to update Kopete package...

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.


Bug#657191: kopete: multiple crashes in the wlm protocol code

2013-07-13 Thread Pali Rohár
Patches from Debian bug #657191 was commited to Kopete master git 
repository and they will part of KDE 4.11 release. So this bug 
can be closed as fixed in upstream.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.


Bug#657191: kopete: multiple crashes in the wlm protocol code

2013-06-02 Thread Pali Rohár
On Friday 31 May 2013 16:56:23 Raphael Geissert wrote:
> Hi,
> 
> On 31 May 2013 14:58, Pali Rohár  wrote:
> > Hello Raphael,
> > 
> > are these wlm patches on debian bug #657191 still valid? Btw
> > in future, please send kopete patches to kopete-devel
> > mailinglist or to kde reviewboard.
> 
> Last I checked the bugs were not yet fixed, so I guess they
> are still valid.
> 

Ok, can you check if bugs are still valid? If yes, I can commit 
them to kopete svn repository.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.


Bug#657191: kopete: multiple crashes in the wlm protocol code

2013-05-31 Thread Pali Rohár
Hello Raphael,

are these wlm patches on debian bug #657191 still valid? Btw in 
future, please send kopete patches to kopete-devel mailinglist or 
to kde reviewboard.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.