Bug#523363: kontact: problem at logon when starting kontact

2010-05-03 Thread Sergiy Yegorov
I have test KDE 4.4.2 (experimental) - looks like bug is fixed.
-- 
Yours sincerely
Sergiy Yegorov
RHCT


signature.asc
Description: This is a digitally signed message part.


Bug#523363: kontact: problem at logon when starting kontact

2010-04-26 Thread Sergiy Yegorov
This bug is still present in Sid (kontact 4:4.3.4-2)
-- 
Yours sincerely
Sergiy Yegorov
RHCT


signature.asc
Description: This is a digitally signed message part.


Bug#523363: Re : Bug#523363: kontact: problem at logon when starting kontact

2009-07-21 Thread Gerard Mensoif

Hi,

I don't have an IMAP based Adressebook, but an FTP based calendar. So normally 
no call to kmail. But thanks for your hint I will have a closer look at KRunner.

Regards
Gerard



- Message d'origine 
De : Kevin Krammer kevin.kram...@gmx.at
À : Gerard Mensoif mensoif_ger...@yahoo.fr; 523...@bugs.debian.org
Envoyé le : Lundi, 13 Juillet 2009, 12h40mn 26s
Objet : Re: Bug#523363: kontact: problem at logon when starting kontact

On Sunday, 2009-06-21, Gerard Mensoif wrote:
 Hi,

 I have the same problem as described by Andres, and I don't have kontact in
 .kde/Autostart/

If you have an IMAP based address book, this could be causing a start at login 
if the Contacts plugin of KRunner (ALT+F2 thingy) is enabled.

The reason is that the plugin accesses the addressbook which in turn needs to 
access the IMAP addressbook which in turn needs KMail (stand-alone or in 
Kontact) to provide the IMAP access.

Cheers,
Kevin







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523363: kontact: problem at logon when starting kontact

2009-07-13 Thread Kevin Krammer
On Sunday, 2009-06-21, Gerard Mensoif wrote:
 Hi,

 I have the same problem as described by Andres, and I don't have kontact in
 .kde/Autostart/

If you have an IMAP based address book, this could be causing a start at login 
if the Contacts plugin of KRunner (ALT+F2 thingy) is enabled.

The reason is that the plugin accesses the addressbook which in turn needs to 
access the IMAP addressbook which in turn needs KMail (stand-alone or in 
Kontact) to provide the IMAP access.

Cheers,
Kevin


signature.asc
Description: This is a digitally signed message part.


Bug#523363: kontact: problem at logon when starting kontact

2009-06-21 Thread Gerard Mensoif

Hi,

I have the same problem as described by Andres, and I don't have kontact in 
.kde/Autostart/

Regards
Gerard







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523363: kontact: problem at logon when starting kontact

2009-04-09 Thread Andres Mejia
Package: kontact
Version: 4:4.2.2-1
Severity: normal

I have a problem with kontact at logon. When you logoff from a session without
closing kontact first, and then log back on, I get the standard prompt from
kwallet and another prompt stating the following.

'Kontact already seems to be running on another display on this machine. Running
Kontact more than once can cause the loss of mail. You should not start Kontact
unless you are sure that it is not already running.' 

Then there's two prompts. Selecting 'Start Kontact' and then entering my
passphrase in kwallet will start two instances of kontact. Selecting 'Exit' will
not start kontact at all.

Furthermore, with the two instances of kontact running, closing one will close
the other as well, probably because it crashes. In the end, I have to manually 
start kontact again anyway.

Here's a copy of the crash dump of the crash I mentioned.

Application: Kontact (kontact), signal SIGSEGV
[Current thread is 0 (LWP 19093)]

Thread 3 (Thread 0xb0d32b90 (LWP 19330)):
#0  0xb7ef8424 in __kernel_vsyscall ()
#1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from 
/lib/i686/cmov/libpthread.so.0
#2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb020eb90 (LWP 19337)):
#0  0xb7ef8424 in __kernel_vsyscall ()
#1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from 
/lib/i686/cmov/libpthread.so.0
#2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4a86700 (LWP 19093)):
#0  0xb7ef8424 in __kernel_vsyscall ()
#1  0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5
#4  0x in ?? ()



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (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/dash

Versions of packages kontact 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  libc6 2.9-6  GNU C Library: Shared libraries
ii  libkdepim44:4.2.2-1  KDE PIM library
ii  libkontactinterfaces4 4:4.2.2-1  KDE Kontact interface library
ii  libqt4-dbus   4.4.3-2Qt 4 D-Bus module
ii  libqt4-qt3support 4.4.3-2Qt 3 compatibility library for Qt 
ii  libqtcore44.4.3-2Qt 4 core module
ii  libqtgui4 4.4.3-2Qt 4 GUI module
ii  libstdc++64.3.3-7The GNU Standard C++ Library v3

Versions of packages kontact recommends:
ii  akregator 4:4.2.2-1  RSS feed aggregator for KDE
ii  kaddressbook  4:4.2.2-1  KDE address book
ii  kmail 4:4.2.2-1  KDE Email client
ii  knotes4:4.2.2-1  KDE sticky notes
ii  korganizer4:4.2.2-1  KDE personal organizer

Versions of packages kontact suggests:
pn  gnokiinone (no description available)
ii  kjots 4:4.2.2-1  note-taking utility for KDE 4
ii  knode 4:4.2.2-1  KDE news reader
pn  ktimeticker   none (no description available)

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523363: kontact: problem at logon when starting kontact

2009-04-09 Thread Sune Vuorela
On Thursday 09 April 2009 17:50:56 Andres Mejia wrote:
 Package: kontact
 Version: 4:4.2.2-1
 Severity: normal

 I have a problem with kontact at logon. When you logoff from a session
 without closing kontact first, and then log back on, I get the standard
 prompt from kwallet and another prompt stating the following.

 'Kontact already seems to be running on another display on this machine.
 Running Kontact more than once can cause the loss of mail. You should not
 start Kontact unless you are sure that it is not already running.'

 Then there's two prompts. Selecting 'Start Kontact' and then entering my
 passphrase in kwallet will start two instances of kontact. Selecting 'Exit'
 will not start kontact at all.

Do you have kontact to start twice?

I had set kontact to autostart in my .kde/Autostart dir and also as part of a 
saved session, and I saw this exact behaviour.

/Sune

 Furthermore, with the two instances of kontact running, closing one will
 close the other as well, probably because it crashes. In the end, I have to
 manually start kontact again anyway.

 Here's a copy of the crash dump of the crash I mentioned.

 Application: Kontact (kontact), signal SIGSEGV
 [Current thread is 0 (LWP 19093)]

 Thread 3 (Thread 0xb0d32b90 (LWP 19330)):
 #0  0xb7ef8424 in __kernel_vsyscall ()
 #1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
 /lib/i686/cmov/libpthread.so.0
 #2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
 #3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
 #4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
 #5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
 #6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
 #7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6

 Thread 2 (Thread 0xb020eb90 (LWP 19337)):
 #0  0xb7ef8424 in __kernel_vsyscall ()
 #1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
 /lib/i686/cmov/libpthread.so.0
 #2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
 #3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
 #4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
 #5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
 #6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
 #7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6

 Thread 1 (Thread 0xb4a86700 (LWP 19093)):
 #0  0xb7ef8424 in __kernel_vsyscall ()
 #1  0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6
 #2  0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6
 #3  0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5
 #4  0x in ?? ()



 -- System Information:
 Debian Release: squeeze/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: i386 (i686)

 Kernel: Linux 2.6.26-1-686 (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/dash

 Versions of packages kontact 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  libc6 2.9-6  GNU C Library:
 Shared libraries ii  libkdepim44:4.2.2-1  KDE PIM
 library
 ii  libkontactinterfaces4 4:4.2.2-1  KDE Kontact interface library
 ii  libqt4-dbus   4.4.3-2Qt 4 D-Bus module
 ii  libqt4-qt3support 4.4.3-2Qt 3 compatibility library for
 Qt ii  libqtcore44.4.3-2Qt 4 core module
 ii  libqtgui4 4.4.3-2Qt 4 GUI module
 ii  libstdc++64.3.3-7The GNU Standard C++ Library
 v3

 Versions of packages kontact recommends:
 ii  akregator 4:4.2.2-1  RSS feed aggregator for KDE
 ii  kaddressbook  4:4.2.2-1  KDE address book
 ii  kmail 4:4.2.2-1  KDE Email client
 ii  knotes4:4.2.2-1  KDE sticky notes
 ii  korganizer4:4.2.2-1  KDE personal organizer

 Versions of packages kontact suggests:
 pn  gnokiinone (no description available)
 ii  kjots 4:4.2.2-1  note-taking utility for KDE 4
 ii  knode 4:4.2.2-1  KDE news reader
 pn  ktimeticker   none (no description available)

 -- no debconf information

-- 
Man, do you know how to save the desktop from X-Windows 5.4?

From the control preferences inside Word XP you should insert a TCP display.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523363: kontact: problem at logon when starting kontact

2009-04-09 Thread Andres Mejia
On Thursday 09 April 2009 17:52:12 Sune Vuorela wrote:
 On Thursday 09 April 2009 17:50:56 Andres Mejia wrote:
  Package: kontact
  Version: 4:4.2.2-1
  Severity: normal
 
  I have a problem with kontact at logon. When you logoff from a session
  without closing kontact first, and then log back on, I get the standard
  prompt from kwallet and another prompt stating the following.
 
  'Kontact already seems to be running on another display on this machine.
  Running Kontact more than once can cause the loss of mail. You should not
  start Kontact unless you are sure that it is not already running.'
 
  Then there's two prompts. Selecting 'Start Kontact' and then entering my
  passphrase in kwallet will start two instances of kontact. Selecting
  'Exit' will not start kontact at all.

 Do you have kontact to start twice?

 I had set kontact to autostart in my .kde/Autostart dir and also as part of
 a saved session, and I saw this exact behaviour.

I don't have kontact set to autostart. Not sure what you mean by saved session. 
This behavior happens to me when I leave kontact open when logging off and then 
logging back on.

 /Sune

  Furthermore, with the two instances of kontact running, closing one will
  close the other as well, probably because it crashes. In the end, I have
  to manually start kontact again anyway.
 
  Here's a copy of the crash dump of the crash I mentioned.
 
  Application: Kontact (kontact), signal SIGSEGV
  [Current thread is 0 (LWP 19093)]
 
  Thread 3 (Thread 0xb0d32b90 (LWP 19330)):
  #0  0xb7ef8424 in __kernel_vsyscall ()
  #1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
  /lib/i686/cmov/libpthread.so.0
  #2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
  #3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
  #4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
  #5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
  #6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
  #7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6
 
  Thread 2 (Thread 0xb020eb90 (LWP 19337)):
  #0  0xb7ef8424 in __kernel_vsyscall ()
  #1  0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
  /lib/i686/cmov/libpthread.so.0
  #2  0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
  #3  0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
  #4  0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4
  #5  0xb75f752e in ?? () from /usr/lib/libQtCore.so.4
  #6  0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
  #7  0xb6b360de in clone () from /lib/i686/cmov/libc.so.6
 
  Thread 1 (Thread 0xb4a86700 (LWP 19093)):
  #0  0xb7ef8424 in __kernel_vsyscall ()
  #1  0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6
  #2  0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6
  #3  0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5
  #4  0x in ?? ()
 
 
 
  -- System Information:
  Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
  Architecture: i386 (i686)
 
  Kernel: Linux 2.6.26-1-686 (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/dash
 
  Versions of packages kontact 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  libc6 2.9-6
   GNU C Library: Shared libraries ii  libkdepim4   
  4:4.2.2-1  KDE PIM library
  ii  libkontactinterfaces4 4:4.2.2-1  KDE Kontact interface
  library ii  libqt4-dbus   4.4.3-2Qt 4 D-Bus module
  ii  libqt4-qt3support 4.4.3-2Qt 3 compatibility library
  for Qt ii  libqtcore44.4.3-2Qt 4 core module ii 
  libqtgui4 4.4.3-2Qt 4 GUI module
  ii  libstdc++64.3.3-7The GNU Standard C++ Library
  v3
 
  Versions of packages kontact recommends:
  ii  akregator 4:4.2.2-1  RSS feed aggregator for KDE
  ii  kaddressbook  4:4.2.2-1  KDE address book
  ii  kmail 4:4.2.2-1  KDE Email client
  ii  knotes4:4.2.2-1  KDE sticky notes
  ii  korganizer4:4.2.2-1  KDE personal organizer
 
  Versions of packages kontact suggests:
  pn  gnokiinone (no description available)
  ii  kjots 4:4.2.2-1  note-taking utility for KDE
  4 ii  knode 4:4.2.2-1  KDE news reader
  pn  ktimeticker   none (no description available)
 
  -- no debconf information

-- 
Regards,
Andres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact