Bug 494732 – =kde-base/kopete-4.11.4[xmpp] starts unconditionally as away

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Agostino Sarubbo 2013-12-19 11:51:27 UTC]

When I start the IM, it starts as away instead of online.

[Comment 1 Johannes Huber (RETIRED) 2013-12-19 12:28:14 UTC]

What is the behaviour in current stable? 

Sounds more like an upstream bug, so i guess you should report this to bugs.kde.org.

[Comment 2 Agostino Sarubbo 2013-12-19 15:02:53 UTC]

(In reply to Johannes Huber from comment #1)
> What is the behaviour in current stable? 

In the current stable is fine.

Also, it fails to go from away to online when there is again the activity



> Sounds more like an upstream bug, so i guess you should report this to
> bugs.kde.org.

This is useful here to block the stabilization.

[Comment 3 Johannes Huber (RETIRED) 2013-12-19 16:21:47 UTC]

There only 2 commits since 4.11.2, so you can test which one introduced the bug and then report this upstream.

https://projects.kde.org/projects/kde/kdenetwork/kopete/repository/show?rev=KDE%2F4.11

[Comment 4 rick vernam 2014-01-07 15:52:00 UTC]

Ping?

[Comment 5 Michael Palimaka (kensington) 2014-01-07 22:52:24 UTC]

(In reply to rick vernam from comment #4)
> Ping?

As stated in comment #1, this is in all probability an upstream issue, and should be reported there too (we only package kopete, we don't develop it).

[Comment 6 rick vernam 2014-01-09 03:27:27 UTC]

Yes, I understand that.  Was a bug filed upstream?  I could go dig around there, but I would sort of expect a post here linking to that upstream report.  So my ping is to find any knowledge of the state of that upstream report - I suppose I could have taken a moment to state that initially, though I thought it was implied.
I see bug reports here sit for weeks, silent, so that anybody who tries to keep abrest of things and perhaps lend a hand would not have a good method to find the current state of things.
If I am wrong that I should expect some ability to check status here, then where should I look?

[Comment 7 Michael Palimaka (kensington) 2014-01-09 09:08:32 UTC]

Hi, thanks for your interest in the bug. I apologise if I sounded short in my previous comment - that definitely wasn't intended.

Normally if there is a KDE report it is linked in the bug here, however after a quick check I couldn't find anything.

Can anyone else confirm that 4.11.2-r1 definitely works?

[Comment 8 Agostino Sarubbo 2014-01-10 16:45:22 UTC]

(In reply to Michael Palimaka (kensington) from comment #7)
> Can anyone else confirm that 4.11.2-r1 definitely works?

Yes, works for me.

[Comment 9 Michael Palimaka (kensington) 2014-01-10 23:37:31 UTC]

(In reply to Agostino Sarubbo from comment #8)
> (In reply to Michael Palimaka (kensington) from comment #7)
> > Can anyone else confirm that 4.11.2-r1 definitely works?
> 
> Yes, works for me.

Is this on the same machine? This could be a tricky one, it looks like 4.11.2-r1 backports the only two changes made since .4

[Comment 10 Andreas K. Hüttel 2014-02-05 11:43:10 UTC]

(In reply to Agostino Sarubbo from comment #8)
> (In reply to Michael Palimaka (kensington) from comment #7)
> > Can anyone else confirm that 4.11.2-r1 definitely works?
> 
> Yes, works for me.

Ago, could you please identify which one of the two commits introduces the problem?

[Comment 11 Agostino Sarubbo 2014-02-06 15:09:02 UTC]

It is not reproducible always, so the cause could not be kopete itself.