[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#529425: kgpg: crashes when refreshing keys from keyserver



Package: kgpg
Version: 4:4.2.2-1
Severity: important

Steps to reproduce:
Start kgpg
Right click on any key
Select Refresh key from keyserver
Crash!

Attached is the kcrashhandler backtrace.

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

Kernel: Linux 2.6.29-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 kgpg 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-12     GNU C Library: Shared libraries
ii  libqt4-dbus                   4.5.1-2    Qt 4 D-Bus module
ii  libqtcore4                    4.5.1-2    Qt 4 core module
ii  libqtgui4                     4.5.1-2    Qt 4 GUI module
ii  libstdc++6                    4.4.0-5    The GNU Standard C++ Library v3

kgpg recommends no packages.

kgpg suggests no packages.

-- no debconf information
Application: KGpg (kgpg), signal SIGSEGV
0x00007f2662952831 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 9015)]

Thread 2 (Thread 0x7f2658a1f950 (LWP 9016)):
#0  0x00007f266297baf2 in select () from /lib/libc.so.6
#1  0x00007f2663049936 in QProcessManager::run (this=0x20aacd0) at io/qprocess_unix.cpp:305
#2  0x00007f2662f82742 in QThreadPrivate::start (arg=0x20aacd0) at thread/qthread_unix.cpp:189
#3  0x00007f265eccbfaa in start_thread (arg=<value optimized out>) at pthread_create.c:300
#4  0x00007f266298229d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f26656e9760 (LWP 9015)):
[KCrash Handler]
#5  0x00000000004363c7 in _start ()


Reply to: