Bug#372767: kgpg: Kgpg editor crashes on decrypting

2006-06-20 Thread Marek Schmidt
Hello,

I have the same problem, here is mine with debug symbols.

Package: kgpg
Version: 4:3.5.3-1

Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
[Thread debugging using libthread_db enabled]
[New Thread -1503344960 (LWP 6788)]
[KCrash handler]
#6  0x080683e0 in KgpgApp::slotResetEncoding (this=0x0, enc=false)
at /home/sid-user/kdeutils/kdeutils-3.5.3/./kgpg/kgpgeditor.cpp:199
#7  0x080eb64b in KgpgApp::qt_invoke (this=0x82db138, _id=75, _o=0xafa4bf18)
at ./kgpgeditor.moc:212
#8  0xa6d7254b in QObject::activate_signal (this=0x830e240, clist=0x8312740, 
o=0xafa4bf18) at kernel/qobject.cpp:2356
#9  0xa6d728a1 in QObject::activate_signal_bool (this=0x830e240, signal=2, 
param=false) at kernel/qobject.cpp:2452
#10 0x0806a449 in KgpgView::resetEncoding (this=0x0, t0=false)
at ./kgpgview.moc:296
#11 0x080ed417 in KgpgView::qt_invoke (this=0x830e240, _id=55, _o=0xafa4c078)
at ./kgpgview.moc:323
#12 0xa6d7254b in QObject::activate_signal (this=0x83bbd50, clist=0x83bc708, 
o=0xafa4c078) at kernel/qobject.cpp:2356
#13 0xa6d72a78 in QObject::activate_signal (this=0x83bbd50, signal=6, 
[EMAIL PROTECTED]) at kernel/qobject.cpp:2451
#14 0x08085857 in KgpgInterface::txtdecryptionfinished (this=0x0, [EMAIL 
PROTECTED])
at ./kgpginterface.moc:683
#15 0x08085982 in KgpgInterface::txtdecryptfin (this=0x83bbd50)
at /home/sid-user/kdeutils/kdeutils-3.5.3/./kgpg/kgpginterface.cpp:349
#16 0x0809f852 in KgpgInterface::qt_invoke (this=0x83bbd50, _id=25, 
_o=0xafa4c5a4) at ./kgpginterface.moc:895
#17 0xa6d7254b in QObject::activate_signal (this=0x83bc950, clist=0x83bd5f0, 
o=0xafa4c5a4) at kernel/qobject.cpp:2356
#18 0xa7366e42 in KProcess::processExited (this=0x83bc950, t0=0x0)
at ./kprocess.moc:137
#19 0xa7366eaf in KProcess::processHasExited (this=0x83bc950, state=0)
at /build/buildd/kdelibs-3.5.3/./kdecore/kprocess.cpp:828
#20 0xa7360730 in KProcessController::slotDoHousekeeping (this=0x81a2858)
at /build/buildd/kdelibs-3.5.3/./kdecore/kprocctrl.cpp:202
#21 0xa7360852 in KProcessController::qt_invoke (this=0x81a2858, _id=2, 
_o=0x0) at ./kprocctrl.moc:82
#22 0xa6d7254b in QObject::activate_signal (this=0x819e458, clist=0x813c3a8, 
o=0xafa4c718) at kernel/qobject.cpp:2356
#23 0xa6d72e52 in QObject::activate_signal (this=0x819e458, signal=2, param=8)
at kernel/qobject.cpp:2449
#24 0xa7104f7f in QSocketNotifier::activated (this=0x819e458, t0=8)
at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#25 0xa6d9280a in QSocketNotifier::event (this=0x819e458, e=0xafa4ca70)
at kernel/qsocketnotifier.cpp:258
#26 0xa6d0887a in QApplication::internalNotify (this=0x813d070, 
receiver=0x819e458, e=0xafa4ca70) at kernel/qapplication.cpp:2635
#27 0xa6d08a76 in QApplication::notify (this=0x813d070, receiver=0x819e458, 
e=0xafa4ca70) at kernel/qapplication.cpp:2358
#28 0xa741324e in KApplication::notify (this=0x813d070, receiver=0x819e458, 
event=0xafa4ca70)
at /build/buildd/kdelibs-3.5.3/./kdecore/kapplication.cpp:550
#29 0xa6c9a001 in QApplication::sendEvent (receiver=0x819e458, 
event=0xafa4ca70) at kernel/qapplication.h:520
#30 0xa6cfa435 in QEventLoop::activateSocketNotifiers (this=0x81a2c98)
at kernel/qeventloop_unix.cpp:578
#31 0xa6cadd06 in QEventLoop::processEvents (this=0x81a2c98, flags=4)
at kernel/qeventloop_x11.cpp:383
#32 0xa6d21255 in QEventLoop::enterLoop (this=0x81a2c98)
at kernel/qeventloop.cpp:198
#33 0xa6d2117a in QEventLoop::exec (this=0x81a2c98)
at kernel/qeventloop.cpp:145
#34 0xa6d0738d in QApplication::exec (this=0x813d070)
at kernel/qapplication.cpp:2758
#35 0x0806d302 in main (argc=0, argv=0x0)
at /home/sid-user/kdeutils/kdeutils-3.5.3/./kgpg/main.cpp:66
#36 0xa77b5eb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x08064c11 in _start () at ../sysdeps/i386/elf/start.S:119


-- 
Marek Schmidt (xschmi01)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#346029: libqt3-mt: Deadkeys don't work with Qt-based applications and cz keyboard

2006-01-11 Thread Marek Schmidt
I think I've found the source of this problem, 

cs_CZ.UTF-8 is missing in /usr/X11R6/lib/X11/locale/compose.dir

I've reported a bug aginst xlibs-data describing this, see bug #347531

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347531

Marek Schmidt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#346029: libqt3-mt: Deadkeys don't work with Qt-based applications and cz keyboard

2006-01-08 Thread Marek Schmidt
I've just found that GTK applications are not using X input method by 
default... 

same problem occurs when running gtk programs with:

LC_CTYPE=cs_CZ.UTF-8 GTK_IM_MODULE=xim gedit

so this is probably not a Qt bug, but rather some problem with compose  
cs_CZ.UTF-8

Marek Schmidt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#346029: libqt3-mt: Deadkeys don't work with Qt-based applications and cz keyboard

2006-01-05 Thread Marek Schmidt
Hello, 

I have exactly the same problem.  (after upgrading xorg to 6.9.0)

Running a qt app with different locale than cs_CZ.UTF-8 seems to work 
correctly, though... I have tested cs_CZ (iso-8859-2), en_US.UTF-8 and 
pl_PL.UTF-8 and these worked well with czech keyboard layout.

Marek Schmidt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]