Your message dated Thu, 28 Jan 2010 21:41:27 +0100
with message-id <4b61f677.10...@gmail.com>
and subject line kopete: Not connected on startup
has caused the Debian Bug report #530934,
regarding kopete: Not connected on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
530934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kopete
Version: 4:4.2.2-1
Severity: normal
Hallo,
The status of kopete is not set to "online" on startup.
I have the setting Behaviour->Initial Status set to "Online". I have
also one account, a WLM-account with password saved and NOT "Exclude
from connect all" set.
Kopete is starting up with the state "Offline". In case I set the state to
"Online" manualy, it changes the state without problems.
I was expecting kopete to startup in the "Online" state.
Regards,
Vincent Smeets
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kopete depends on:
ii kdebase-runtime 4:4.2.2-1 runtime components from the offici
ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli
ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli
ii libasound2 1.0.19-1 shared library for ALSA applicatio
ii libc6 2.9-12 GNU C Library: Shared libraries
ii libglib2.0-0 2.20.1-2 The GLib library of C routines
ii libidn11 1.14-3 GNU Libidn library, implementation
ii libkopete4 4:4.2.2-1 main Kopete library
ii libmeanwhile1 1.0.2-3 open implementation of the Lotus S
ii libmsn0.1 4.0~beta3-1 high-level C++ library for MSN Mes
ii libortp8 3.0.0-3 Real-time Transport Protocol stack
ii libotr2 3.2.0-1 Off-the-Record Messaging library
ii libqca2 2.0.0-4 libraries for the Qt Cryptographic
ii libqimageblitz4 1:0.0.4-4 QImageBlitz image effects library
ii libqt4-dbus 4.5.1-2 Qt 4 D-Bus module
ii libqt4-network 4.5.1-2 Qt 4 network module
ii libqt4-qt3support 4.5.1-2 Qt 3 compatibility library for Qt
ii libqt4-sql 4.5.1-2 Qt 4 SQL module
ii libqt4-xml 4.5.1-2 Qt 4 XML module
ii libqtcore4 4.5.1-2 Qt 4 core module
ii libqtgui4 4.5.1-2 Qt 4 GUI module
ii libspeex1 1.2~rc1-1 The Speex codec runtime library
ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3
ii libxml2 2.7.3.dfsg-1 GNOME XML library
ii libxslt1.1 1.1.24-2 XSLT processing library - runtime
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
Versions of packages kopete recommends:
ii libqca2-plugin-ossl 0.1~20070904-3 QCA OSSL plugin for libqca2
Versions of packages kopete suggests:
ii kdeartwork-emoticons 4:4.2.2-2 emoticon collections for KDE 4 cha
pn khelpcenter <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hallo,
I am closing this bug as I have found the problem and it isn't a kopete
problem.
On my system (Debian-Testing) I have the NetworkManager running, but it
was never configured. I found out that the file
/etc/NetworkManager/nm-system-settings.conf contained the line
"managed=false". So the NetworkManager didn't know the state of the network.
After setting the line to "managed=true" and restarting does the
NetworkManager know the network state. Now NetworkManager knows the
state and can pass it to kopete. Kopete now automatically goes to the
online state as expected.
Kopete checks the network state of the NetworkManager before setting the
initial state of Kopete. The problem is that this doesn't work in case
the NetworkManager isn't working correctly. That was my problem. There
are some solutions to this problem:
* Always set the initial state to the state defined by the settings
and after that, react on state changes from the NetworkManager.
* Keep the current behavior and add some description to the setting
that the initial state is only set in case the NetworkManager has
been configured and the network is online.
Can you also close the bug (https://bugs.kde.org/show_bug.cgi?id=189149)
in KDE as I don't have an account there.
Regards,
Vincent Smeets
--- End Message ---
