Bug 288312

Summary: can not connect to a network
Product: [Unmaintained] telepathy Reporter: Sandra <lumks>
Component: generalAssignee: Telepathy Bugs <kde-telepathy-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: heri+kde, kde, mklapetek, plusfabi
Priority: NOR    
Version: unspecified   
Target Milestone: 0.4.0   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: command-log
Gabble debug with missing ~/.cache/dconf

Description Sandra 2011-12-06 07:02:13 UTC
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

hi there. i have tried to use telepathy kde the last days. first via selfbuild and later via kubuntu ppa https://launchpad.net/~telepathy-kde/+archive/ppa . the same thing happens. 
after adding a accound (gmail/xmpp) i get a little popup with
"There was a problem while trying to connect [messengeraccount] - Some of the IM components are not working correctly (and your system does not tell us which one)"
i dont know what i can do to fix is. other people are able to run it via the ppa version.

Reproducible: Always

Steps to Reproduce:
1. add ppa/compile yourself
2. add an account


Actual Results:  
can not connect for some reason

Expected Results:  
schould be able so connect

create a new user do not fix it. the same error as with an old useraccound
Comment 1 Martin Klapetek 2011-12-08 12:25:16 UTC
Which account is it you're trying to connect?
Comment 2 Sandra 2011-12-08 13:37:10 UTC
Its an account on neko.im, as well as an account on googletalk. both time the same message.
Tried the last days a fresh reinstall of kubuntu+this ppa and it works without an problem. so maybe its some kind of misconfiguration in an unknown part.
so i tried now to delete ~/.mission-control and ~/.kde/share/apps/ktelepathy but it changed nothing.
A Friend has sayd i should install empathy and try to login there and after that give ktelepathy another try because both a telepathy clients. is this a good idea?
Comment 3 Martin Klapetek 2011-12-08 13:53:54 UTC
Yes, they are both Telepathy clients (or "frontends", rather), installing Empathy might shed some light on it, but there's a better way to find out what's wrong.

Disable all your accounts but the GTalk. Disconnect everything and make sure telepathy-gabble is not running.

Then run this command from terminal:
GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy-gabble

Note that it might not find the telepathy-gabble there, in that case, please replace it with the correct path (use "locate telepathy-gabble" for example).

After it's running, connect your GTalk account. Then check the log for sensitive data and if there are none, please attach it here. If it has sensitive data, you can send it to me by email.
Comment 4 Sandra 2011-12-08 16:11:38 UTC
Created attachment 66507 [details]
command-log

wow thats strange. after your command 
"GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble"
i was online. tried to reboot and no problems anymore. my second accound works too.
the process "telepathy-gabble" was not running.after the start from ktelepathy. there was just a "telepathy-haze"
seems to be fixed/workaroundet/whatever for now
Comment 5 David Edmundson 2011-12-30 01:51:15 UTC
Original reporter claims it now works. Not much we can do to diagnose the original problem, hopefully it's gone away (and was upstream anyway).
Comment 6 FabiB 2011-12-30 03:45:10 UTC
Dont know if it is related to this but maybe its because of this. If there is no directory "~/.cache/dconf" you will not be able to connect. (k)telepathy seems to not be able to create it, if it isnt there. 

test:
kill telepathy-gabble and maybe mission-control too
rm -r ~/.cache/dconf
now start ktelepathy and try to connect to an network. you will get the same text as Sandra.

fix:
mkdir -p ~/.cache/dconf
start ktelepathy and it will work
Comment 7 Martin Klapetek 2012-01-13 14:47:37 UTC
Created attachment 67784 [details]
Gabble debug with missing ~/.cache/dconf

I managed to get another gabble debug from a friend who had exactly the same problem - missing ~/.cache/dconf. He wasn't able to connect to gtalk with "internal component error", after just creating this folder, everything works.

Maybe it's gabble bug actually?
Comment 8 Dennis Schridde 2012-01-31 09:41:03 UTC
I also had this problem. But when I looked today, ~/.cache/dconf existed, and when I added Telepathy KDE to the systray again (I removed it recently, because it did not work anyway), it suddenly worked. I did not do anything in particular to fix this, especially did I not run telepathy-gabble manually or create the beforementioned directory.
Comment 9 buzzmandt 2012-01-31 14:46:09 UTC
I had the same issue causing the same internal component error. This from a
fresh install of Kubuntu + ppa.  Ill try it over again to see if the issue
is truely gone.
On Jan 31, 2012 5:06 AM, "Dennis Schridde" <devurandom@gmx.net> wrote:

> https://bugs.kde.org/show_bug.cgi?id=288312
>
>
> Dennis Schridde <devurandom@gmx.net> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |devurandom@gmx.net
>
>
>
>
> --- Comment #8 from Dennis Schridde <devurandom gmx net>  2012-01-31 09:41:03
> ---
> I also had this problem. But when I looked today, ~/.cache/dconf existed,
> and
> when I added Telepathy KDE to the systray again (I removed it recently,
> because
> it did not work anyway), it suddenly worked. I did not do anything in
> particular to fix this, especially did I not run telepathy-gabble manually
> or
> create the beforementioned directory.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy@kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy
>