Pidgin won't start (completely)
Christian Baer
christian.baer at uni-dortmund.de
Fri Sep 21 09:18:01 EDT 2007
On Fri, Sep 21, 2007 at 08:29 -0400, Luke Schierer wrote:
Greetings, Programs! :-)
> > > Sounds like it is starting fine, and is minimized into the system
> > > tray/notification area/whatever KDE calls it (dock, maybe?).
> >
> > You had me going there for a moment, because I thought I had actually been
> > to blind to see that. And even though it wouldn't have been good for my
> > ego, a "user to dumb error" that solves the problem is fine with me. :-)
> >
> > In this case, unfortunately, no...
> >
>
> Try moving (do not delete) your ~/.purple/prefs.xml out of the way, does
> this still happen?
This was a new insallation of Pidgin, so there is no prefs.xml (yet). It
seems as if purple didn't get that far.
There is this path (which I didn't create):
~/.purple/certificates/x509/tls_peers/
There are no files in any of these folders.
I got a hint from someone in a newsgroup (I thought this might also be a
FreeBSD issue), that nat-pmp could be the problem, as I am not aware of
anyone other than Apple having a working implementation of this. So I used
kdump(1) to find out what is going on. I don't want to post the whole file
here (it is rather long). But a few things I did notice...
90378 dbus-daemon RET read 144/0x90
90378 dbus-daemon CALL read(0xb,0x2a1000,0x800)
90378 dbus-daemon RET read -1 errno 35 Resource temporarily unavailable
90378 dbus-daemon CALL gettimeofday(0x7fdffffe240,0)
90378 dbus-daemon RET gettimeofday 0
90378 dbus-daemon CALL poll(0x7fdffffe540,0x3,0)
90378 dbus-daemon RET poll 0
90378 dbus-daemon CALL poll(0x282000,0x3,0)
90378 dbus-daemon RET poll 0
90378 dbus-daemon CALL poll(0x282000,0x4,0xffffffffffffffff)
90373 pidgin CALL setitimer(0x2,0x7fdffffd0d0,0)
90373 pidgin RET setitimer 0
90373 pidgin CALL close(0x3)
90373 pidgin RET close 0
90373 pidgin CALL close(0x4)
90373 pidgin RET close 0
90373 pidgin CALL fcntl(0,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0x1,0x3,0)
90373 pidgin RET fcntl 2
90373 pidgin CALL fcntl(0x1,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0x2,0x3,0)
90373 pidgin RET fcntl 2
90373 pidgin CALL fcntl(0x2,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0x6,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0x6,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0x7,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0x7,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0x8,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0x8,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0xa,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0xa,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0xb,0x3,0)
90373 pidgin RET fcntl 4
90373 pidgin CALL fcntl(0xb,0x4,0)
90373 pidgin RET fcntl 0
90373 pidgin CALL fcntl(0xc,0x3,0)
90373 pidgin RET fcntl 6
90373 pidgin CALL fcntl(0xc,0x4,0x2)
90373 pidgin RET fcntl 0
90373 pidgin CALL exit(0)
90378 dbus-daemon RET poll 1
90378 dbus-daemon CALL gettimeofday(0x405d73a8,0)
90378 dbus-daemon RET gettimeofday 0
90378 dbus-daemon CALL gettimeofday(0x7fdffffe240,0)
90378 dbus-daemon RET gettimeofday 0
90378 dbus-daemon CALL read(0xb,0x2a1000,0x800)
90378 dbus-daemon GIO fd 11 read 0 bytes
""
90378 dbus-daemon RET read 0
90378 dbus-daemon CALL fstat(0xb,0x7fdffffda30)
90378 dbus-daemon RET fstat 0
90378 dbus-daemon CALL close(0xb)
90378 dbus-daemon RET close 0
90378 dbus-daemon CALL gettimeofday(0x7fdffffe240,0)
90378 dbus-daemon RET gettimeofday 0
90378 dbus-daemon CALL poll(0x7fdffffe540,0x2,0)
90378 dbus-daemon RET poll 0
90378 dbus-daemon CALL poll(0x282000,0x2,0)
90378 dbus-daemon RET poll 0
90378 dbus-daemon CALL poll(0x282000,0x3,0xffffffffffffffff)
I have a typical problem in the sense of "I know what it says, but I don't
know what it means." especially since I don't know what all those numbers
mean off by heart.
Maybe that helps. If you need it, I can supply the whole file, but not on
the list as it is about 280K big.
Regards
Chris
More information about the Support
mailing list