[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

Pali Rohár  changed:

   What|Removed |Added

Version|unspecified |4.14.0
Summary|Kopete crashes after|kdelibs upgrade - Kopete
   |closing a window|crashes after closing a
   ||window
Product|kopete  |kdelibs
   Priority|NOR |VHI
   Assignee|kopete-bugs-n...@kde.org|kdelibs-b...@kde.org
  Component|general |general

--- Comment #22 from Pali Rohár  ---
Moving to kdelibs product and chaning priority as this is very critical. Now we
know that Kopete start crashing after upgrading kdelibs, so this is kdelibs
problem.

@Alex Merry: Do you have idea how to fix it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356734] crash on window closing

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356734

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---


*** This bug has been marked as a duplicate of bug 355275 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #38 from Pali Rohár  ---
Ok, Alex do you have idea how to fix this problem in Kopete? Kopete is on its
way in porting to KF5 and so KF5 Kopete version must be fixed...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356201] Send file operation fails due to Socks5 proxy protocol error

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356201

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Pali Rohár  ---
Hi Lukasz! Kopete jabber code uses external libiris library for XMPP support.
Due to compilation problems Kopete has unmodified copy of libiris in
git/tarball.

If there are any problems with libiris library, please report bugs to libiris
project at https://github.com/psi-im/iris

PSI jabber client uses same library, so please check PSI if has same problem as
Kopete to determinate if problem is in library libiris or application.

Also libiris library has xmpptest application for testing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

Pali Rohár  changed:

   What|Removed |Added

 CC||bugs...@les-charles.net

--- Comment #39 from Pali Rohár  ---
*** Bug 356734 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #33 from Pali Rohár  ---
Alex, change was not obviously correct because it totally broke Kopete.
And from my side such commit should be reverted as ASAP because it broke
existing SW which use it.

Non-working Kopete with new kdelibs (which is not breaking API/ABI) is a
big problem.

It new version of kdelibs is ABI incompatible with old one, it should
increase soversion in library.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #35 from Pali Rohár  ---
>From Kopete point of view, this was something like API change. As it
does not work with new kdelibs.

We can name it different (not API change) if you do not want, but it is
something which prevent upgrading kdelibs to new version when Kopete is
installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #46 from Pali Rohár  ---
(In reply to szymon.p...@gmail.com from comment #45)
> kdelibs 4.14.15-1
> 
> Not fixed!

See description - it will be fixed in 4.14.16.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #47 from Pali Rohár  ---
On Wednesday 18 May 2016 09:27:25 Ben Cooksley via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
> 
> --- Comment #46 from Ben Cooksley  ---
> This will be my very final correspondence on this issue.
> 
> In regards to email standards, they're not relevant here. What
> commonly used email providers dictate as being required is relevant,
> as what people care about is getting their email in a readable form.
> The RFCs and other material are just a guideline towards that. Oh,
> and DMARC is an RFC, so it's part of the standards. GMail, followed
> by Yahoo are our top destinations for email delivery. So they set
> the rules.

Your words basically means: "I do not care about anybody except Gmail & 
Yahoo providers which set and dictate rules how emails could work". 
Sorry, but in open community and for free & open source projects, I 
cannot accept this statement.

If you are doing such thing, please explicitly write to KDE webpages:
We are not supporting email service and appreciate standards anymore. We 
only supports Gmail & Yahoo services and due to our limits we ignore all 
requests for supporting standard email service. Our users are restricted 
to use Gmail or Yahoo otherwise our service will not work correctly.

If you are *not* doing such thing, you cannot mark this report as 
INVALID. As INVALID means "we do not care about non Gmail users".

So I really would like to know what is current state. I really cannot 
accept community which declare themselves as free & open source 
software, but follow big corporations which "set the rules".

> In regards to the solutions you proposed, they either:
> a) Impacted upon the reliability of Bugzilla service; or
> b) Significantly increased the maintenance burden Sysadmin would face
> to maintain Bugzilla. And we have enough maintenance workload as it
> stands. Plus we'd have to author the change in the first place, and
> Bugzilla is written in Perl.

If you need I can help with Perl, this is something which I know.

I proposed solutions, because nobody else proposed anything. And I 
wanted to see this bug fixed. So I did everything which I could.

> And in case you are wondering - every other bug tracking system out
> there, including vanilla Bugzilla, follows the behaviour we follow
> now. Our previous behaviour was a hack, added in many, many years
> ago, and which is not able to be continued with, due to the issues
> noted previously.
> 
> This issue is far from being ignored. It has been looked into and
> discussed here for a very long time. The behaviour the system now
> follows is known, and is the desired and correct behaviour.
> 
> I have no idea why your workflow requires / demands filtering based
> on commenter/reporter email address (in which case, may I suggest
> headers in the email which Bugzilla includes), but it is no longer
> something we can accommodate using the From field in an email.

Reason is quite obvious. Every and I'm sure every one email client show 
3 important headers to user: From, To and Subject. Lot of email clients 
(and those web based too) have some index view, where is list of emails, 
e.g. clickable one email per line and on that line show again only 
From/To and Subject (sometimes also Date). And based on this information 
user open/select email.

Email headers From and To are there for 20+ years and they are not going 
to be changed. All existing email software is based on them and once you 
start rewriting them or mangling, you just broke email support...

And I'm using this information in From, To and Subject headers to 
quickly filter emails and mark what is important and what not. Also for 
searching for comments from specific people, etc...



And problem via total nonsense in From header

"From: via KDE Bugzilla "

is still there and did not hear anybody how and when to fix it. In 
comment 10 you wrote that this is when somebody does entered name at 
all. Should I interpret your last comment, that you are ignoring also 
this problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 362663] Plasma notifications about new messages persistent

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362663

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---
I do not see this problem on KDE4 desktop. So it is probably KF5 plasma
problem. Maybe move it into plasma project so plasma devs can look at it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 361732] Carbons support

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361732

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||pali.ro...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Pali Rohár  ---
Patches for such feature are really welcome!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 363053] Building kopete-16.04.0 with GCC-6.1.0 fails with "error: could not convert 'false' from 'bool' to 'const Kopete::MetaContact*'"

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363053

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||16.04.2
  Latest Commit||http://commits.kde.org/kope
   ||te/9f994ba6950117cbbeefc602
   ||7fa0a52ce74932e2

--- Comment #5 from Pali Rohár  ---
Git commit 9f994ba6950117cbbeefc6027fa0a52ce74932e2 by Pali Rohár, on behalf of
Peter Levine.
Committed on 31/05/2016 at 15:40.
Pushed by pali into branch 'Applications/16.04'.

Fix compilation with GCC 6

REVIEW: 128006
FIXED-IN: 16.04.2

M  +1-1plugins/history2/history2logger.h

http://commits.kde.org/kopete/9f994ba6950117cbbeefc6027fa0a52ce74932e2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 362535] Kopete 1.9.0 somtimes won't encrypt even though the GUI says otherwise

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362535

Pali Rohár  changed:

   What|Removed |Added

 CC||mzane...@kde.org,
   ||pali.ro...@gmail.com

--- Comment #2 from Pali Rohár  ---
Michael, can you look at this bug?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 351420] ICQ password length limit was changed from 8 to 16 chars

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=351420

Pali Rohár  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

--- Comment #5 from Pali Rohár  ---
*** Bug 363317 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 363317] Login or password incorrect when password len greter 8 chars

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=363317

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Pali Rohár  ---
It is probably duplicate of bug #351420. Please verify it. In that bug is also
proposed  fix which needs to be tested first before including it into kopete
git repository. If you can please do that. Thanks!

*** This bug has been marked as a duplicate of bug 351420 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail] [Bug 166653] Index files recreated on startup and mail check

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=166653

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356102] Wrong URL for Jabber server list

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356102

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Pali Rohár  ---
Hm.. right, that URL does not work anymore. Do you know replacement?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 358744] Kopete crashes on closing message tab

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358744

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 CC||pali.ro...@gmail.com
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Pali Rohár  ---
Hi! You backtrace does not contain Kopete debug symbols. Please install them
and send backtrace again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #17 from Pali Rohár  ---
Maybe I have knowledge how email should like, but I have absolutely no
knowledge of bugzilla and its code, so I'm not able to develop it...

I can only test implementation if it send correctly formatted emails :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 357694] Kopete crashed when looking at settings

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357694

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||pali.ro...@gmail.com
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Pali Rohár  ---
Please check if this problem is also older KDE version 4.14.13. Maybe it could
be similar to bug #355275

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 98295] [wish] selectable spellchecker language for each contact

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=98295

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #9 from Pali Rohár  ---
@Fibonacci: Patches are welcome.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] New: Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

Bug ID: 359603
   Summary: Incorrect and useless From header in emails generated
by KDE Bugzilla
   Product: bugs.kde.org
   Version: unspecified
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: pali.ro...@gmail.com
CC: she...@kde.org

Before Oct 2015 all emails generated by KDE Bugzilla when somebody adds comment
to bug or change description has From and Sender header in this format:

From: XNAMEX YYY 
Sender: bugzilla_nore...@kde.org

(where XNAMEX YYY is name and XEMAILX email address).

Since Oct 2015 email there is no Sender header and format of From is:

From: XNAMEX YYY via KDE Bugzilla 

(where XNAMEX YYY is name of who added comment to specific bug).

And now in this week I got emails from KDE Bugzilla which format of From header
is:

From: via KDE Bugzilla 

(again without any Sender header).

>From header with value "via KDE Bugzilla " is totally
useless, it does not contain truth information not any useful.

>From header with value "XNAMEX YYY via KDE Bugzilla "
is incorrect too. For specifying who sent that email there is Sender header.
>From header should be really in format "XNAMEX YYY" and email address. Not some
funny value like "via KDE Bugzilla".

Please fix generating From header for emails sent by KDE Bugzilla. Do not
invent new funny format of From header, but instead generate it according to
Email standards, like RFC 5322 (Originator Fields):
https://tools.ietf.org/html/rfc5322#section-3.6.2

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #2 from Pali Rohár  ---
Why it does now work? RFC 5322 says:

The "From:" field specifies the author(s) of the message, that is, the
mailbox(es) of the person(s) or system(s) responsible for the writing of the
message.

So using value "XNAMEX YYY via KDE Bugzilla " for
>From header is incorrect and in some conditions can be interpreted as violating
RFC document which is standard for email messages.

For specifing via KDE Bugzilla, there is Sender field, RFC 5322 says:

The "Sender:" field specifies the mailbox of the agent responsible for the
actual transmission of the message.  For example, if a secretary were to send a
message for another person, the mailbox of the secretary would appear in the
"Sender:" field and the mailbox of the actual author would appear in the
"From:" field.

KDE Bugzilla acts there as "secretary". If KDE Bugzilla provides email support
it should send emails according to email standards...

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #4 from Pali Rohár  ---
But if you ignore RFC 5322 how email structure must looks like, you are
breaking email message itself. It means that every email client which is RFC
5322 compliant just show incorrect or less useful data/email to user who is
trying to read it.

I cannot ignore RFC 5322 or its older version RFC 2822 or RFC 822. RFC 822 has
now "INTERNET STANDARD" status and meaning From and Sender field is there same
as in its last RFC 5322 in "DRAFT STANDARD".

In case of correctness RFC 822 is here unambiguous and "INTERNET STANDARD".
Standards are here to make interopability between other applications.

If you ignore it, it cause problem in all other applications which users use to
read emails. And really modified and useless information in From header cause
problems for me and my email softwares. I'm sure I'm not alone who use advanced
search or other actions on inboxes and such "fake" information in envelope
cause lot of problems...

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #6 from Pali Rohár  ---
I do not agree.

If somebody put correct and RFC-compliant message with meaningful headers
suitable for processing and parsing into spam folder it is his problem.

But if server generates incorrect email message and send it to the world, it is
problem of server, not client. If server generates something wrong it is bug on
server and like other bugs it should be fixed.

Think of user, receiver who configured that he *wants* to receive notifications
from KDE Bugzilla. And receive those notifications in form of email message. If
that message is incorrect or contains useless informations, it is useless for
receiver=user.

If somebody configured his bugzilla account that he want to receive *email*
messages, he should get email messages according to email message standard (RFC
822, or new). Not something different. Why otherwise he configure such option?

Receiving these emails correctly formatted is to make it easier, not harder
just becase emails comes "broken".

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

Pali Rohár  changed:

   What|Removed |Added

 Resolution|WONTFIX |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #9 from Pali Rohár  ---
@Nicolás: If problem is just on recipient site, then please consider at least
per-user option to generate valid RFC 5322 emails. It is really bad to do such
thing for all users automatically, without option to disable it or warning
users "we will send you incorrect email messages". Why should all users suffer
from this, even if they do not have such problems?

I will reopen this bug, because second part of this problem was not discussed
nor fixed. Some emails sent to me this week has this email header:

From: via KDE Bugzilla 

It is useless as it does not provide any information about user who is
responsible for the change. Name "via KDE Bugzilla" looks like you forgot to
include user identifier at the begining.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #11 from Pali Rohár  ---
And one more thing... Via kde.org domain are running more mailing list servers.
I do not see any discarding of From header in emails send to mailing list. So
why are you doing it for bugzilla emails? If somebody has problem with
bugzilla, does not it have also with mailing lists?

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #13 from Pali Rohár  ---
And for exactly such situation there is defined Sender header in RFC 5322 where
should be specified kde.org address and signed by kde key.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #15 from Pali Rohár  ---
So that DMARC is broken by design...

And one more reason for per-bugzilla-account option to enable/disable removing
>From header.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #27 from Pali Rohár  ---
Alright, I missed that second DKIM-Signarure header (from google). So yes,
there are two DKIM signartures, one from google and one from kde.

But it still does not explain, why emails from other 3rd web services signed
*only* by  that 3rd SMTP server are normally received into INBOX (and not to
spam like you writing in case for kde bugzilla).

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #24 from Pali Rohár  ---
Ben, but there is no difference between email sent by Bugzilla and email sent
by kde.org list (both with d=kde.org DKIM signature). In both cases that email
is sent by outgoing kde.org SMTP server.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

--- Comment #12 from Pali Rohár  ---
On Wednesday 16 March 2016 00:07:02 via KDE Bugzilla wrote:
> Not sure how this patch would be applied. I'm using OpenSUSE supplied 
> packages...

Download source code of Kopete, apply patch (patch -p1 -i file) and
recompile it.

Anyway, I would really like to see symbols/function names in valgrind
output. Can you look at it? That patch is just my first attempt but
without future more information I cannot detect root of this problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #21 from Pali Rohár  ---
(In reply to george from comment #20)
> Created attachment 97918 [details]
> kopete debug log using talk.google.com:5222, plaintext, no legacy SSL
> 
> Ok, I have tried again. Settings:
> 
> talk.google.com, port 5222, no legacy SSL

Looks better. According to my dns output, google has all host+port information
in dns, so default configuration (without overwriting host/port and enabling
legacy ssl) should work.

> The result is the attached log. As soon as I try to go Online, Kopete asks
> me for my password (although I have already entered it and remembered it in
> the account options). I enter it and tick the "Remeber" checkbox again. I
> attempts to login and again pops up asking for password. And so on to
> infinity.

That means that server rejected your password (= authentication failed).

> BUT!
> 
> In the meantime I received an email on the Gmail account:
> --
>   Sign-in attempt prevented   
>   
> Hi SANITIZED,
> Someone just tried to sign in to your Google Account saniti...@gmail.com
> from an app that doesn't meet modern security standards.
>   Details:
> Wednesday, March 16, 2016 12:27 AM
> (LOCATION SANITIZED)*
> We strongly recommend that you use a secure app, like Gmail, to access your
> account. All apps made by Google meet these security standards. Using a less
> secure app, on the other hand, could leave your account vulnerable. Learn
> more.
> 
> Google stopped this sign-in attempt, but you should review your recently
> used devices:
> --
> 
> Than I went to https://myaccount.google.com/security and saw the option
> Allow less secure apps: OFF. I put it to ON and now I can connect. Put it
> back to OFF and I cannot.
> 
> So it seems Kopete can connect only if using plaintext authentication and
> reducing the overall security of the Google account. I definitely don't feel
> safe doing this. Pidgin works with encryption turned on and without having
> to "Allow less secure apps".

Some fancy google security. Nothing standard for jabber protocol. So now we
know where is problem. This is great! Thanks for debugging. First problem is to
properly set settings (no legacy ssl and correct port) and second is to disable
some fancy google security.

> Can you fix that?

I see that google send this list of auth mechanisms:

X-OAUTH2
X-GOOGLE-TOKEN
PLAIN

First twos are some google non standard specific and last third is standard
(plain text). I do not see there any secure SCRAM auth mechanism. So I would
suspect that to connect without that google "less secure option" it is needed
to support one of that first two specific google auth mechanisms...

Anyway, Kopete for jabber connection (and also this authentication!) uses
external libiris library. So I cannot fix this problem in Kopete. It would mean
to implemented either X-OAUTH2 or X-GOOGLE-TOKEN in libiris. So please report
this problem to upstream libiris project. Now when we know that this is 100%
not in Kopete, I will close this bug as cannot do more. Project page of libiris
is: https://github.com/psi-im/iris

> Also - how do I debug to debug if the situation with Telepathy is the same?
> (which I suppose is quite possible) Maybe that might be worth a separate
> ticket.

I have no idea hwo KDE Telepathy is working and how to debug it. Please ask
this on Telepathy project.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

--- Comment #10 from Pali Rohár  ---
Created attachment 97919
  --> https://bugs.kde.org/attachment.cgi?id=97919=edit
jabber qpointer patch

Can you try attached patch? It just adds QPointer guard for account which try
to prevent use-after-free.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

Pali Rohár  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1
 Resolution|BACKTRACE   |---

--- Comment #9 from Pali Rohár  ---
Looks like that valgrind did not find where are those debug symbols installed
in your system. Try to use --extra-debuginfo-path= valgrind parameter. I need
to know function names and lines instead of "??? (in
/usr/lib64/kde4/kopete_jabber.so)"...

Also your last post with valgrind output is wrapped and hard to read/parse. In
future rather upload it as attachment to bugzilla as text file (this should
prevent wrapping).

Anyway, this crash is really strange. From that incomplete valgrind output it
looks like that Qt library decided to free memory where was allocated instance
of jabber account.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

--- Comment #5 from Pali Rohár  ---
It should be application independent, but I do not instructions for your
distribution... Try to look ak kopete-debug or kopete-dbg packages...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #17 from Pali Rohár  ---
This looks really suspicious. No credentials were sent, no handshake and google
closed connection even before it sent some response.

Can you recheck that you have correct configuration? No legacy ssl and default
server+port. Or you can set server to talk.google.com, port 5222 (no legacy
ssl).

If it still happens, please try to capture packages in wireshark. If
configuration is OK, then for unknown reasons google (or ISP) blocks you.

And telepathy does not use any jabber/xmpp library as Kopete.

Which version of Kopete do you try?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 359024] Icons for some protocols missing (e.g. Skype)

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359024

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||pali.ro...@gmail.com
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Pali Rohár  ---
Which icon theme do you use? Do you have correctly installed Kopete?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #5 from Pali Rohár  ---
Check if you can connect with Psi IM client. It uses same XMPP library as
Kopete.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 359444] Invalid message encoding using GroupWise protocol.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359444

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---
Hi! Is there any public groupwise server for testing reproducing it? I do not
have any groupwise account nor official Novell client, so I cannot test it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

--- Comment #3 from Pali Rohár  ---
Sorry, I have no idea how your distribution is working. Consult documentation
or support. Basically debug symbols are often in distribution package -debug or
-dbg. If your distribution does not provide them, you need to compile Kopete
from source.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

Pali Rohár  changed:

   What|Removed |Added

 CC||rich...@underpope.com

--- Comment #50 from Pali Rohár  ---
*** Bug 358922 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 358922] Crash when conversation window closed

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358922

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||pali.ro...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Pali Rohár  ---


*** This bug has been marked as a duplicate of bug 355275 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360029] Kopete sometimes crashes on exit

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360029

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 CC||pali.ro...@gmail.com
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Pali Rohár  ---
Please install debug symbols and report backtrace again. Without debug
information it is useless.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #9 from Pali Rohár  ---
(In reply to george from comment #8)
> I am not going to expose my credentials in plain text just because a program 
> doesn't work properly.

Blame google, not me or Kopete.

> If it works in plain text authentication only, I would rather not use it. 
> Sorry.

That is another option, stop using google account.

> Pidgin works without problem with encryption with the same account.

But you still did not understand, that jabber password is sent in SSL tunnel?
It is same as if you enter password in web browser. In 99.99% cases it is sent
in plain text (under SSL tunnel).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #11 from Pali Rohár  ---
(In reply to george from comment #10)
> I just tried Psi with another (less important) Google account in plain text
> mode - exactly the same result.

Psi and Kopete use same XMPP library. Pidgen use another...

In Kopete open XML console (right click on jabber account) and aftet that try
to connect. In XML console should be full XMPP communication and also reason
why login was rejected. Remove sensible information (like username+password)
and post here full output. Maybe it could help for debugging...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 CC||pali.ro...@gmail.com
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Pali Rohár  ---
Please install debug systems and provide backtrace again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #7 from Pali Rohár  ---
You need to use PLAIN mechanism (plain text password). Check that you enabled
plain text authentication as written in error message.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #13 from Pali Rohár  ---
Thats all what is in XML console? No  lines? It looks weird. Check
that you have opened XML console before trying to login...

Also try to "kopete (jabber)" and "kopete (jabber - raw protocol)" in
kdebugdialog application and then start kopete from terminal. On terminal there
should be full XMPP communication too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #15 from Pali Rohár  ---
Just start kdebugdialog application and enable those two checkboxes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #20 from Pali Rohár  ---
Nicolás: This is independent to email client. Email notification from this bug
contain "From: NAME via KDE Bugzilla " header, but
email notifications from e.g. bug 360384 contain only "From: via KDE Bugzilla
".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #19 from Pali Rohár  ---
(In reply to george from comment #18)
> I am using talk.google.com port 5223
...
> What should I do?

You are using wrong port number, that could explain reason. Use 5222. That port
is also stored in gmail.com DNS records:

$ host -t SRV _xmpp-client._tcp.gmail.com
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 alt4.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 alt2.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 alt3.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 alt1.xmpp.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 5 0 5222 xmpp.l.google.com.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 360384] Kopete crashes on exit. Every time, all the time.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360384

--- Comment #7 from Pali Rohár  ---
Hm... this looks very strange. No idea why it crash.

If you can reproduce this crash at 100% please install valgrind and run in
terminal kopete under valgrind as:

$ valgrind kopete --nofork

And post output from terminal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #35 from Pali Rohár  ---
Any response/objections/comments about my idea?

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #29 from Pali Rohár  ---
Ok, so in this case it is not problem with Gmail service...

Anyway... I still do not understand your decision. You broke all emails which
are sent from Bugzilla, made them non-filter-able and useless for all email
clients which are RFC822/2822/5322 compliant just because Yahoo and AOL decided
to start dropping bugzilla emails.

If somebody set-up email address for receiving email, then it is expected that
is using email service, not Yahoo or AOL (which just do not support *all*
emails).

I really do not like your decision. I thought that bugzilla (and its email
feature support) is there to help KDE developers to better track and fix bugs,
not to complicate it.

So please again, reconsider support for proper emails and not dropping it
because of yahoo-email or aol-email support...

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #32 from Pali Rohár  ---
On Monday 21 March 2016 06:02:49 Valorie Zimmerman via KDE Bugzilla wrote:
> Pali, the points you make have also been made by others, so you are not alone
> in your dismay with the changes we've had to make in email both here and on
> lists as well. I'm old enough to remember a time before spammers, believe it 
> or
> not. Now that they produce between 75 and 95% of all the mail sent, the old
> RFCs have had to be left behind.

Hi Valorie! Two important things:

1) Email clients implement those email RFCs (RFC2822 resp. RFC5322 and
others for MIME). RFC5322 is not old for sure and you cannot ignore it
or drop it. They are "email standards".

2) If such anti-spam protection drops more than 30% of non-spam emails
then it is not only useless but must be avoided because it drop regular
non-spam messages. Same as sending all emails to /dev/null. It is
absolute anti-spam protection but totally useless.

> Please believe that our sysadmin team is doing all they can to support our
> developers in every way they can. They have sweat blood over these changes, 
> and
> do not welcome repeated pleas to "go back to the old way" -- a way that did 
> not
> work for a large percentage of our developers.

I believe that. But I as person who working with emails, working on
application which parse, archive, view... incoming emails cannot accept
something which mangle emails or fill useless and incorrect info to
email headers.

Also as I'm (and probably other people) filtering emails by From header
it basically means that I cannot longer do it. Plus I need to totally
drop information from From header as it contains useless, incorrect and
invalid information also for *regular* (non-spam) emails.

By filtering I mean also active filter or search rule, not just applying
them on incoming emails.

If such anti-spam protection mangle emails, damage emails or is
inconsistent to "email standards", then that it cause problems to all
email clients which are compliant to "email standards".

Doing such thing really complicates everything for me for developing. I
cannot use anymore filter/search functionality on emails from KDE
bugzilla and so those emails have very low value. And bugzilla emails
for Kopete project what what I used, which means that I do not have any
relevant tool which works for Kopete bugs.

> We are all going to have to accept reality, and use the tools we have to 
> assist
> us in our work.

So instead of making KDE bugzilla to be compliant for "email standards"
which is implemented by email clients and what they expect (and e.g.
what I use for my work and tracking of Kopete bugs), you chose to
support two/three provides of email-like services gmail, yahoo, aol
(which are incompatible for normal emails).

This is that reality? I cannot accept such thing! It means that
indirectly you are forcing all KDE people (including developer!) to use
one of that email-like service and stop using email applications which
expect "standard emails".

I'm really not happy with this situation it just means that tools for
KDE developers are going to be only "gmail" compatible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 166225] Add New Account dialog displays poorly

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=166225

Pali Rohár  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||16.04
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kope
   ||te/54673d894a91412df75d9396
   ||6aa0a455b8d0ad48

--- Comment #4 from Pali Rohár  ---
Git commit 54673d894a91412df75d93966aa0a455b8d0ad48 by Pali Rohár, on behalf of
Paulo Lieuthier.
Committed on 25/03/2016 at 11:10.
Pushed by pali into branch 'Applications/16.04'.

Resize New Account dialog when changing page
FIXED-IN: 16.04

M  +5-0kopete/addaccountwizard/addaccountwizard.cpp

http://commits.kde.org/kopete/54673d894a91412df75d93966aa0a455b8d0ad48

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 331705] Kopete incorrectly places elements in transport registration window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=331705

Pali Rohár  changed:

   What|Removed |Added

   Version Fixed In||16.04
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kope
   ||te/46cfb747a6024baaea8f67d4
   ||03ae7eb9ef0cda74

--- Comment #7 from Pali Rohár  ---
Git commit 46cfb747a6024baaea8f67d403ae7eb9ef0cda74 by Pali Rohár, on behalf of
Paulo Lieuthier.
Committed on 25/03/2016 at 11:09.
Pushed by pali into branch 'Applications/16.04'.

Fix layout bugs in Jabber's service registration dialogs
FIXED-IN: 16.04

M  +3-2protocols/jabber/jabberformtranslator.cpp
M  +3-2protocols/jabber/jabberxdatawidget.cpp

http://commits.kde.org/kopete/46cfb747a6024baaea8f67d403ae7eb9ef0cda74

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #22 from Pali Rohár  ---
Nicolás, thank you! Please at least do that.

Anyway, I still do not understand, why problem is with Bugzilla and not
with (KDE) mailing lists?? I see that KDE mailing lists servers set
DKIM-Signature email header with "d=kde.org" value even if From: header
contains @gmail.com domain. And such emails are normally received to
gmail users into INBOX, not to spam.

So again, why bugzilla do not set correct From: and Sender: headers?

If problem would be really with mismatching domain in (d=) in
DKIM-Signature header and domain (after @...) in From header, then also
emails sent by mailing lists would go to spam...

Also I see others (non KDE) emails with different domain in
DKIM-Signature and From. And they also go to gmail INBOX, not spam.

So I would suspect, that problem is not in DKIM header/signature, but on
different place... Please can you look at it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #34 from Pali Rohár  ---
On Saturday 26 March 2016 19:13:24 Nicolás Alvarez via KDE Bugzilla 
wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
> 
> --- Comment #33 from Nicolás Alvarez  ---
> (In reply to Pali Rohár from comment #32)
> 
> > 2) If such anti-spam protection drops more than 30% of non-spam
> > emails then it is not only useless but must be avoided because it
> > drop regular non-spam messages. Same as sending all emails to
> > /dev/null. It is absolute anti-spam protection but totally
> > useless.
> 
> Yup, I agree.
> 
> But it's not our fault. Go complain to Yahoo and to the inventors of
> DMARC. We can't fix it, we can only apply workarounds to ensure our
> mail reaches our users.

Ok, here is my proposed solution for this problem:

Detect if provider of email receiver enforce DMARC and if not, do not 
mangle from/sender headers. Ideally add option to bugzilla account 
configuration to enable/disable mangling from/sender headers.

This could fix problem when yahoo (and others) drop emails from kde 
bugzilla and also allow other non-yahoo (and non-etc...) users to 
receive normal emails as before.

Nicolás, what do you think about it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #18 from Pali Rohár  ---
Please do something with this bug! Just having string "via KDE Bugzilla"
in From header without any other information about sender/creator makes
my work with bugzilla really hard. I --- as maintainer of Kopete IM client,
which is part of KDE --- needs some working system, not something like
this.

I really do not want to take Kopete project out of this KDE system, but
if you are not able to fix bug which is regression I would need to start
thinking what to do with it. As I'm really unable to use such broken
system.

It is probably good that users can report Kopete bugs into KDE bugzilla,
but really useless if those who want to fix them cannot easily use such
system. Please thing about it!

Anyway, I do not understand why you have problem with signing DKIM with
@kde.org domain key as lot of emails are normally received by gmail into
INBOX (not SPAM!) which has different DKIM key as domain specified in
email address in From: header. So there is probably broken also
something else...

If you need some other assistance, I can help, but I really od not like
this that nobody care about this my reported bug and there is just
silence...

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 360205] Inconsistent TAB parsing in Subject header

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360205

--- Comment #5 from Pali Rohár  ---
On Monday 07 March 2016 12:31:08 Erik Quaeghebeur via KDE Bugzilla wrote:
> line-breaks in subjects are not allowed.

Hm... is there restriction in RFC for this? Just asking.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

--- Comment #49 from Pali Rohár  ---
@mando: See that it is fixed in KDE version 4.14.16, but you have only 4.14.14.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 360205] Inconsistent TAB parsing in Subject header

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360205

--- Comment #11 from Pali Rohár  ---
On Monday 07 March 2016 15:05:24 Erik Quaeghebeur via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360205
> 
> --- Comment #10 from Erik Quaeghebeur  ---
> (In reply to Jan Kundrát from comment #8)
> > > More generally, as far as I've understood (and modulo folding), 
> > > a header value MUST NOT contain any line breaks.
> > 
> > There is RFC2047 which specifies how to send Unicode. It gets triggered by 
> > presence of LFs in my testing, and I think that this usage is actually 
> > kosher -- but i'll be happy to be proven wrong by a quite from some other 
> > RFC.
> 
> The token definition in RFC822 that allowed bare CR and bare LF was updated in
> RFC2822 to preclude them:
> 
> RFC2047 Section 5. (1) on p.7:
> « An ’encoded-word’ may replace a ’text’ token (as defined by RFC 822) in any
> Subject or Comments header field [...] »

So it means that UTF-8 encoded unicode character "newline" in MIME
Base64 is valid content for Subject header. Right?

> RFC822 Section 3.3 on p.10:
> « text =  »

Ah, so old RFC 822 allows directly "\n" in Subject. I did not know that.

> RFC2822 Section 3.2.1 on p.10:
> « text = %d1-9 / %d11 / %d12 / %d14-127 / obs-text ; Characters excluding
> CR and LF »
> 
> (RFC5322 doesn't reintroduce them.)
> 
> So digesting them is needed for dealing with old messages, but producing them
> is, in my understanding, against the latest RFC.

Right, my original question about newlines was because I wanted to know
if compliant email client needs to deal with such thing. So answer is
yes, "\n" in Subject is valid character.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 360205] Inconsistent TAB parsing in Subject header

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360205

--- Comment #9 from Pali Rohár  ---
On Monday 07 March 2016 13:17:45 Erik Quaeghebeur via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360205
> 
> --- Comment #7 from Erik Quaeghebeur  ---
> (In reply to Pali Rohár from comment #5)
> > On Monday 07 March 2016 12:31:08 Erik Quaeghebeur via KDE Bugzilla wrote:
> > > line-breaks in subjects are not allowed.
> > 
> > Hm... is there restriction in RFC for this? Just asking.
> 
> In RFC 5322, it is said that Subject is an unstructured field, which is
> described in Section 2.2.1 as
> 
> « Some field bodies in this specification are defined simply as
> "unstructured" (which is specified in section 3.2.5 as any printable
> US-ASCII characters plus white space characters) with no further
> restrictions. These are referred to as unstructured field bodies.
> Semantically, unstructured field bodies are simply to be treated as a
> single line of characters with no further processing (except for
> "folding" and "unfolding" as described in section 2.2.3). »
> 
> More generally, as far as I've understood (and modulo folding), a header value
> MUST NOT contain any line breaks.
> 

This is truth, but RFC 2047 allows you to include any unicode character
into header body (via encoding unicode character to UTF-8 and encoding
it to either QP or Base64). It means that also newline can be encoded
into Base64. From RFC 5322 point of view, Base64 is single line (after
unfolding) but you have funny unicode and also ascii whitespaces in
header body...

Or is there some restriction that above is violation of MIME or
something else?

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 361372] Trojita crashes with symbol lookup error against QtKeychain on startup

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361372

--- Comment #2 from Pali Rohár  ---
On Monday 04 April 2016 11:08:40 Jan Kundrát via KDE Bugzilla  wrote:
> Please ask your vendor (someone in ArchLinux likely?) to rebuild trojita after
> an update to qtkeychain. The latest qtkeychain update is apparently not
> ABI-compatible.

That then looks like either qtkeychain project does not correctly
increased SOVERSION when introduced ABI incompatibility or package
maintainer did not propagated SOVERSION or correct dependency...

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #38 from Pali Rohár  ---
On Saturday 23 April 2016 01:55:21 Ben Cooksley via KDE Bugzilla wrote:
> Detection of DMARC enforcement would involve making DNS queries everytime an
> action takes place on Bugzilla (for every single recipient none the less),
> which would make the system unnecessarily unreliable and prone to failure.

DNS query is already sent for each recipient when sending email. Asking
for MX record... So I do not see problem here.

But if this is problem, then we can just add option ENABLE/DISABLE
mangling of address in profile settings. Where user could specify action
for emails sent to his address.

And we can choose default settings for this option when user register
account.

> It would also require making invasive changes to the Bugzilla codebase -
> patches we would have to support going forward.

Also that simple option? It could be just one query to database (or
where are stored user options) and based on this generate email.

But here I do not know. I have not seen bugzilla source code (I guess it
is some PHP application?), so I just try to find out solution to this
problem... But with PHP I could not help.

> It also wouldn't help where Bugzilla emails go to mailing lists, which then
> have subscribers which enforce DMARC.

Mailing lists adding subject prefix or change some email headers.
Therefore they are by DMARC definitions incompatible with DMARC.

> Finally, it would make behaviour of Bugzilla inconsistent from person to
> person, which is bound to result in other bugs being raised.

Same argument can be used from another point of view: Users who enforce
DMARC on their own address are already inconsistent with whole email
infrastructure.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356326

--- Comment #10 from Pali Rohár  ---
On Thursday 12 May 2016 12:19:18 Rex Dieter via KDE Bugzilla wrote:
> I'm offering to do the work to address this, if needed.

Ok, if you want to spend time on it, feel free to do.

But please contact Harsh Shah (harshcrop). His GSoC project for Kopete
is writing new IRC protocol. So please decide with him how and what to
remote/modify to prevent merge conflicts, etc...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356326

--- Comment #5 from Pali Rohár  ---
IRC code is going to be rewritten (from scratch). So after that new IRC
code should fix also this problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #44 from Pali Rohár  ---
On Tuesday 17 May 2016 09:29:17 Ben Cooksley via KDE Bugzilla wrote:
> This isn't a bug - it's intended behaviour and conforms with what email
> providers these days expect. It therefore won't be changing.

I cannot agree with you. It is a bug, email sent by kde bugzilla does
not conform to email standards. And more over it is regression, because
it worked correctly before.

I want to have working bugzilla again and so, I proposed solutions to
this problems.

If somebody use email provider who does not respect email standards (and
still mark that service as "email") it is his problem. But I'm really
against mangling emails, make them less usable and similar... for people
who support correct email behaviour. Still, I proposed solutions which
does not affect those "other providers". And I could think about other
options.

But I really want to see this problem fixed, not ignored from KDE admins
and KDE community. If you are going to do that, then I'm forced to move
my projects outside of (non working) KDE infrastructure... which I
really do not want...

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #40 from Pali Rohár  ---
Ok, and what about option which do not check DNS records when user
change it? That will not lock bugzilla...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356326

--- Comment #17 from Pali Rohár  ---
On Monday 16 May 2016 12:53:57 Rex Dieter via KDE Bugzilla wrote:
> I don't see anything committed to kopete's git (since Apr 08) either.

I do not see any patches on reviewboard, nor in kopete-devel mailing list...

> Did you maybe forget to push the changes or is it someone else's 
> responsibility
> to commit the changes?

I can commit changes, but first need to see patches (on reviewboard or ML).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356326

--- Comment #20 from Pali Rohár  ---
On Monday 16 May 2016 13:04:09 Jonathan Riddell via KDE Bugzilla wrote:
> sorry, pushed now

Ok, but you are missing BUG keyword in commit message... :-(
That could allow us in future to map commit into bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356326

--- Comment #7 from Pali Rohár  ---
On Thursday 12 May 2016 12:03:42 Rex Dieter via KDE Bugzilla wrote:
> Except the code is non-compliant *now*, any objections to my removing it 
> (since
> it's not used)?

It is not compliant not only now, but for longer time. If we are able to
wait and deal with it for years, I think we can also another period of
time...

I do not want to break something... (Need to check how to modify build
infrastructure, etc, ...) And also do want to invest time for code which
will be replaced.

Development time for Kopete can be used in better way.

As I said, this problem will be resolved by rewriting IRC code.

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 362551] Some fixes in CMakeLists.txt that prevent a FTBFS

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362551

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #4 from Pali Rohár  ---
Why soversion? That library does not have any public API/ABI, so versioning
does not make sense...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 362535] Kopete 1.9.0 somtimes won't encrypt even though the GUI says otherwise

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362535

--- Comment #6 from Pali Rohár  ---
(In reply to OlafLostViking from comment #5)
> Since the dropdown in the bug report form isn't up to date either (latest is
> 1.7.2),

Thats bugzilla configuration... and I have no idea how to change it...

> I wonder if Kopete is still being maintained or if it's dead: Are
> there any developers left

Kopete is still maintained, there are few developers around. KF5 port is work
in progress, jabber library periodically updated and when I have time I also
fixing some bugs... I would say it is not dead, just not heavily developed as
10 years ago.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 272855] kopete fails to connect after network connection is switched to vpnc

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=272855

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||pali.ro...@gmail.com

--- Comment #4 from Pali Rohár  ---
Hi! This is not a problem with Kopete, but with your VPN software which does
set routing correctly. I'm not goint to add any hacks into Kopete just because
some VPN softwares are broken... I will close this bug as invalid Kopete
project. Rather report problem to your VPN software.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 365092] Frequent disconnects on fast networks

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365092

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---
Hi! Kopete uses libiris library for communication with jabber server. If you
think that problem is related with low level parts of jabber protocol (like
socket, network connection or parsing jabber xml parts), then please report it
to libiris project: https://github.com/psi-im/iris

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 365016] it is impossible to enter the credentials for the jabber transport

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365016

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---
Sorry but linked pictures cannot be shown. In future attach all materials to
bugzilla and not link to external services which can trash data...

Anyway, from your description it looks like a problem from bug 331705 which was
fixed in Kopete version 1.9.0. Can you verify it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 234167] Text doesn't wrap correctly in kopete chat window

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=234167

Pali Rohár  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||pali.ro...@gmail.com

--- Comment #3 from Pali Rohár  ---
On that place is animated icon when sending message. After message is sent icon
disappear. This looks like a problem that background under that icon is not
rendered again after icon disappear... I have no idea where is problem (maybe
it is something in KDE/Qt libraries).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=225747

Pali Rohár  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||pali.ro...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

--- Comment #5 from Pali Rohár  ---
Confirmed, unicode characters in XML should be encoded as full codepoints, not
as UTF-16 surrogate pairs. Surrogate pairs are invalid in XML, so server should
really disconnect you.

See: http://www.w3.org/TR/REC-xml/#charsets

Character Range

[2]   Char   ::=   #x9 | #xA | #xD | [#x20-#xD7FF] |
[#xE000-#xFFFD] | [#x1-#x10]/* any Unicode character, excluding the
surrogate blocks, FFFE, and . */

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 314272] Kopete disconnects from Jabber when sending text outside of BOM

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=314272

Pali Rohár  changed:

   What|Removed |Added

 Resolution|UPSTREAM|DUPLICATE

--- Comment #10 from Pali Rohár  ---
For sure this is same bug as #225747... I can reproduce it.

*** This bug has been marked as a duplicate of bug 225747 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=225747

--- Comment #7 from Pali Rohár  ---
This is bug in QtXml... My workaround for libiris:
https://github.com/psi-im/iris/pull/44

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=225747

Pali Rohár  changed:

   What|Removed |Added

 CC||char...@kde.org

--- Comment #6 from Pali Rohár  ---
*** Bug 314272 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 279269] Kopete history plugin escapes quote and ampersand characters

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=279269

Pali Rohár  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE
 CC||pali.ro...@gmail.com

--- Comment #4 from Pali Rohár  ---


*** This bug has been marked as a duplicate of bug 269097 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 269097] [PATCH] Some html entities are not correctly displayed in history

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=269097

Pali Rohár  changed:

   What|Removed |Added

 CC||m...@sevik.ru

--- Comment #4 from Pali Rohár  ---
*** Bug 279269 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=225747

Pali Rohár  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||16.08.1
  Latest Commit||http://commits.kde.org/kope
   ||te/f23d6ccc7a7f542059c3956d
   ||64d912a34584723e

--- Comment #8 from Pali Rohár  ---
Git commit f23d6ccc7a7f542059c3956d64d912a34584723e by Pali Rohár.
Committed on 15/08/2016 at 15:58.
Pushed by pali into branch 'Applications/16.08'.

jabber: Workaround bug in QtXML: Fix xmlToString when QDomElement contains
Unicode characters above 0x

Upstream:
https://github.com/psi-im/iris/commit/8612bc340421087cf0ebfd426661ff22f7351270

See also discussion:
https://github.com/psi-im/iris/pull/44
https://github.com/psi-im/iris/pull/43
https://github.com/psi-im/iris/issues/42
https://github.com/psi-im/iris/issues/13
https://bugreports.qt.io/browse/QTBUG-25291
Related: bug 314272
FIXED-IN: 16.08.1

A  +19   -0protocols/jabber/libiris/patches/01_qtxml_unicode.patch
M  +8-0protocols/jabber/libiris/src/xmpp/xmpp-core/xmlprotocol.cpp

http://commits.kde.org/kopete/f23d6ccc7a7f542059c3956d64d912a34584723e

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 314272] Kopete disconnects from Jabber when sending text outside of BOM

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=314272

Pali Rohár  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kope
   ||te/f23d6ccc7a7f542059c3956d
   ||64d912a34584723e
   Version Fixed In||16.08.1
 Resolution|DUPLICATE   |FIXED

--- Comment #11 from Pali Rohár  ---
Git commit f23d6ccc7a7f542059c3956d64d912a34584723e by Pali Rohár.
Committed on 15/08/2016 at 15:58.
Pushed by pali into branch 'Applications/16.08'.

jabber: Workaround bug in QtXML: Fix xmlToString when QDomElement contains
Unicode characters above 0x

Upstream:
https://github.com/psi-im/iris/commit/8612bc340421087cf0ebfd426661ff22f7351270

See also discussion:
https://github.com/psi-im/iris/pull/44
https://github.com/psi-im/iris/pull/43
https://github.com/psi-im/iris/issues/42
https://github.com/psi-im/iris/issues/13
https://bugreports.qt.io/browse/QTBUG-25291
Related: bug 225747
FIXED-IN: 16.08.1

A  +19   -0protocols/jabber/libiris/patches/01_qtxml_unicode.patch
M  +8-0protocols/jabber/libiris/src/xmpp/xmpp-core/xmlprotocol.cpp

http://commits.kde.org/kopete/f23d6ccc7a7f542059c3956d64d912a34584723e

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=225747

--- Comment #9 from Pali Rohár  ---
*** Bug 314272 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 314272] Kopete disconnects from Jabber when sending text outside of BOM

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=314272

Pali Rohár  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #12 from Pali Rohár  ---


*** This bug has been marked as a duplicate of bug 225747 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

Pali Rohár  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #27 from Pali Rohár  ---
@george: If you do not want to compile Kopete, you can try it on Ubuntu/Kubuntu
distributions. Daily kopete packages from git with that X-OAUTH2 patch are in
repository: https://launchpad.net/~pali/+archive/ubuntu/kopete/+packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 370450] incorrect launch command for skype accounts

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370450

--- Comment #3 from Pali Rohár  ---
Probably problem is really in localized strings... But localization files are
not part of Kopete.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 338891] SASL Autenthication error while connecting to Jabber-Server

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=338891

Pali Rohár  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Pali Rohár  ---
SCRAM-SHA-1 is already supported, closing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 370450] incorrect launch command for skype accounts

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370450

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #1 from Pali Rohár  ---
Default is "skype" with small 's'. Do you have localized KDE?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 368340] Build fails with mediastreamer 2.14

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368340

Pali Rohár  changed:

   What|Removed |Added

 CC||pali.ro...@gmail.com

--- Comment #3 from Pali Rohár  ---
Hi Fabian Vogt! Can you cleanup your patch and post it to
git.reviewboard.kde.org to kopete group?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

Pali Rohár  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

Pali Rohár  changed:

   What|Removed |Added

   Version Fixed In|16.12   |
  Latest Commit|http://commits.kde.org/kope |
   |te/3bff188483fd2ee01bb8310a |
   |511e8cc9a4808d22|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

--- Comment #25 from Pali Rohár  ---
Support for X-OAuth2 is in kopete branch jabber-xoauth2, diff uploaded to
reviewboard: https://git.reviewboard.kde.org/r/129239/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 354473] Cannot login to Google account

[Pali Rohár via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354473

Pali Rohár  changed:

   What|Removed |Added

   Version Fixed In||16.12
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kope
   ||te/3bff188483fd2ee01bb8310a
   ||511e8cc9a4808d22

--- Comment #24 from Pali Rohár  ---
Git commit 3bff188483fd2ee01bb8310a511e8cc9a4808d22 by Pali Rohár.
Committed on 21/10/2016 at 16:44.
Pushed by pali into branch 'jabber-xoauth2'.

Add support for X-OAuth2 authentication in Jabber protocol

Based on Psi demo code from:
https://github.com/psi-im/iris/issues/35
https://github.com/psi-plus/main/blob/master/patches/dev/xoauth2-support-demo.diff

REVIEW: 129239
FIXED-IN: 16.12

M  +3-0CMakeLists.txt
M  +4-4protocols/CMakeLists.txt
M  +5-1protocols/jabber/CMakeLists.txt
M  +4-1protocols/jabber/jabberaccount.cpp
M  +40   -0protocols/jabber/jabberclient.cpp
M  +3-0protocols/jabber/jabberclient.h
M  +98   -0protocols/jabber/ui/dlgjabbereditaccountwidget.ui
A  +76   -0protocols/jabber/ui/dlgjabberxoauth2.cpp [License: GPL
(v2+)]
A  +43   -0protocols/jabber/ui/dlgjabberxoauth2.h [License: GPL (v2+)]
A  +161  -0protocols/jabber/ui/dlgxoauth2.ui
M  +18   -1protocols/jabber/ui/jabbereditaccountwidget.cpp
M  +1-0protocols/jabber/ui/jabbereditaccountwidget.h
A  +331  -0protocols/jabber/xoauth2provider.cpp [License: GPL (v2+)]
A  +25   -0protocols/jabber/xoauth2provider.h [License: GPL (v2+)]

http://commits.kde.org/kopete/3bff188483fd2ee01bb8310a511e8cc9a4808d22

-- 
You are receiving this mail because:
You are watching all bug changes.