Bug#529532: please package libqca2 2.0.2
Package: libqca2 Version: 2.0.0-4 Severity: wishlist It fixes a known incompatibility when Psi 0.12 used with Qt 4.5. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-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 libqca2 depends on: ii libc6 2.9-10 GNU C Library: Shared libraries ii libgcc1 1:4.4.0-5 GCC support library ii libqt4-core 4.4.3-2transitional package for Qt 4 core ii libstdc++64.4.0-5The GNU Standard C++ Library v3 libqca2 recommends no packages. Versions of packages libqca2 suggests: pn libqca2-plugin-cyrus-sasl (no description available) ii libqca2-plugin-gnupg 0.1~20070904-2 QCA gnupg plugin for libqca2 ii libqca2-plugin-ossl 0.1~20070904-3 QCA OSSL plugin for libqca2 pn libqca2-plugin-pkcs11 (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#529002: Acknowledgement (korganizer: crashes with SIGILL when attempting to edit recurring event)
Here is the core dump: http://www.easy-share.com/1905264380/korganizer.core.bz2 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: (no subject)
Processing commands for cont...@bugs.debian.org: > fixed 451963 4:4.2.2-1+b1 Bug#451963: [kalzium] crashes using the Equation Solver Bug marked as fixed in version 4:4.2.2-1+b1. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Correctly Put on a Condom Every Time You Hook Upp
<>
dAult Toys - Uses and Care
<>
Quanta's VPL editor don't handle accents
Package: quanta Version: 4:3.5.9-3 Severity: normal -- System Information: Debian Release: 5.0.1 *** Please type your report below this line *** In the VPL editor, the accents are not handle right. Examples: I write "á é í ó ú", but in the VPL editor appear "´a ´e ´i ´o ´u". The HTML codification (charset= utf8, ISO-8859,...) not affect this. Thanks
Bug#529487: kde-window-manager: KDE 4.2 broke dual-head setup with fglrx
Package: kde-window-manager Version: 4:4.2.2-2 Severity: normal Hello, after installing KDE 4.2 my dual-head setup with an ATI Radeon 3870 X2 (fglrx driver) doesn't work anymore with KDE. KDE doesn't recognize the second screen (it doesn't show up in the systemsettings panel, so maybe this is a systemsettings and not a kde-window-manager bug). This leads to the first screen working as expected and the second staying black. With KDE 3.5 it worked. fglrxinfo reports both screens correctly. If you should need further information please contact me and I'd be happy to provide you with whatever you'll need to fix this issue. Kind regards, Fabian Ossevorth _ http://redirect.gimas.net/?n=M0905xFTP_SpringCampaign2 --> Für Fotos hier abdrücken <-
Bug#529356: akregator: SIGSEV after marking a lot of unread feeds as read
On Tuesday 19 May 2009 05:37:35 you wrote:
> On Mon, 18 May 09 23:17, Jordan Manolov wrote:
> > Package: akregator
> > Version: 4:4.2.2-1
> > Severity: normal
> >
> > After fetching feeds - about 75-100 - and marking them as read,
> > akregator always crashes. Here is the backtrace:
> >
> > Application: Akregator (akregator), signal SIGSEGV
> >
> > Thread 1 (Thread 0xb4fae710 (LWP 12671)):
> > #0 0xb7f61424 in __kernel_vsyscall ()
> > #1 0xb69a2386 in nanosleep () from /lib/i686/cmov/libc.so.6
> > #2 0xb69a219e in sleep () from /lib/i686/cmov/libc.so.6
> > #3 0xb7c90738 in ?? () from /usr/lib/libkdeui.so.5
> > #4 0x in ?? ()
>
> Could you please install kdepim-dbg (attention, it is large) and
> recreate the backtrace? The one above is quite meaningless
without
> debugging symbols.
>
> Thanks in advance,
> Armin
Sorry, I responded to the email and the backtrace was sent to the
developer..
Here is the result:
Application: Akregator (akregator), signal SIGSEGV
[Current thread is 0 (LWP 3456)]
Thread 2 (Thread 0xb1746b90 (LWP 4122)):
#0 0xb7f47424 in __kernel_vsyscall ()
#1 0xb58082e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2 0xb69daf84 in pthread_cond_timedwait () from
/lib/i686/cmov/libc.so.6
#3 0xb75b07fc in QWaitCondition::wait (this=0x93e7738,
mutex=0x93e7734, time=3) at
thread/qwaitcondition_unix.cpp:85
#4 0xb75a5db6 in QThreadPoolThread::run (this=0x92ab928) at
concurrent/qthreadpool.cpp:140
#5 0xb75af80e in QThreadPrivate::start (arg=0x92ab928) at
thread/qthread_unix.cpp:189
#6 0xb58044e5 in start_thread () from
/lib/i686/cmov/libpthread.so.0
#7 0xb69cc10e in clone () from /lib/i686/cmov/libc.so.6
Thread 1 (Thread 0xb4f94710 (LWP 3456)):
[KCrash Handler]
#6 0xb69601cb in strlen () from /lib/i686/cmov/libc.so.6
#7 0xb2eeba18 in c4_String (this=0xbfa64578, p=0x
) at
../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:129
#8 0xb2eed55c in c4_Property (this=0xbfa645b8, type_=73 'I',
name_=0x ) at
../../../../akregator/plugins/mk4storage/metakit/src/view.cpp:1100
#9 0xb2edfb77 in f4_CreateFormat (pro...@0x958788c,
se...@0x9559df0) at
../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:524
#10 0xb2ee1a54 in c4_HandlerSeq::CreateHandler (this=0x9559df0,
pro...@0x958788c) at
../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:131
#11 0xb2ef00cc in c4_Sequence::PropIndex (this=0x9559df0,
pro...@0x958788c) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:292
#12 0xb2ef1436 in c4_Sequence::Set (this=0x9559df0, index_=494,
pro...@0x958788c, bu...@0xbfa647a0) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:325
#13 0xb2eecd05 in c4_View::SetItem (this=0x9559d24, row_=494,
col_=21, bu...@0xbfa647a0) at
../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:426
#14 0xb2ee8365 in c4_HashViewer::SetItem (this=0x9559d20,
row_=494, col_=21, bu...@0xbfa647a0) at
../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366
#15 0xb2ed66e9 in c4_CustomSeq::DoSet (this=0x95833e8,
row_=494, col_=21, bu...@0xbfa647a0) at
../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:154
#16 0xb2ed6cca in c4_CustomHandler::Set (this=0x957f428,
index_=494, bu...@0xbfa647a0) at
../../../../akregator/plugins/mk4storage/metakit/src/custom.cpp:69
#17 0xb2ef0933 in c4_Sequence::SetAt (this=0x95833e8,
index_=494, newElem_={_seq = 0xa246ce8, _index = 0}) at
../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104
#18 0xb2ef26aa in
Akregator::Backend::FeedStorageMK4Impl::setStatus
(this=0x956eec8, gu...@0x993b480, status=8) at
../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89
#19 0xb38c26f0 in Akregator::Article::setStatus (this=0xbfa64978,
stat=1) at ../../../akregator/src/article.cpp:367
#20 0xb38c8d02 in Akregator::ArticleModifyJob::doStart
(this=0xb46d9e0) at ../../../akregator/src/articlejobs.cpp:144
#21 0xb38c92b5 in Akregator::ArticleModifyJob::qt_metacall
(this=0xb46d9e0, _c=QMetaObject::InvokeMetaMethod, _id=0,
_a=0xbfa64a38) at ./articlejobs.moc:158
#22 0xb76b8b98 in QMetaObject::activate (sender=0xb5e3720,
from_signal_index=4, to_signal_index=4, argv=0x0) at
kernel/qobject.cpp:3120
#23 0xb76b9822 in QMetaObject::activate (sender=0xb5e3720,
m=0xb7793ae8, local_signal_index=0, argv=0x0) at
kernel/qobject.cpp:3194
#24 0xb76be027 in QSingleShotTimer::timeout (this=0xb5e3720) at
.moc/release-shared/qtimer.moc:76
#25 0xb76be14c in QSingleShotTimer::timerEvent (this=0xb5e3720)
at kernel/qtimer.cpp:298
#26 0xb76b304f in QObject::event (this=0xb5e3720, e=0xbfa64ebc)
at kernel/qobject.cpp:1082
#27 0xb6ca97bc in QApplicationPrivate::notify_helper
(this=0x90ca4f8, receiver=0xb5e3720, e=0xbfa64ebc) at
kernel/qapplication.cpp:4057
#28 0xb6cb1ace in QApplication::notify (this=0xbfa65130,
receiver=0xb5e3720, e=0xbfa64ebc) at
kernel/qapplication.cpp:3604
#29 0xb7c06b7d in KApplication::notify (
Bug#529435: QListBox::current set in insertItem without currentChanged emiting
On Tue, May 19, 2009 at 01:17:24PM +0200, Michal Hocko wrote:
> Package: qt-x11-free
> Severity: normal
>
> Hi,
> I have just noticed that buggy behavior in my application is caused by
> QListBox::current being set during insertItem without triggering
> currentChanged.
> My application uses currentChanged handler for enable/disable logic and
> so this doesn't work in case that box was empty.
>
> I am not sure whether this is correct or not, but it is at least
> inconsistent for cases like:
>
> box->insertItem(item, pos);
> box->setCurrentItem(pos);
>
> because this will trigger currentChanged signal only if box wasn't empty
> before.
>
> I have checked the source and really QListBox::insertItem does something
> like:
>
> if ( hasFocus() && !d->current ) {
> d->current = d->head;
> updateItem( d->current );
> emit highlighted( d->current );
> emit highlighted( d->current->text() );
> emit highlighted( index );
> }
>
> I think that we are missing emit currentChanged there.
I would suggest the attached patch. Please note that I haven't tested
it.
There are more places which set current to some value and don't emit
currentChanged but I wasn't sure whether to fix them as well (e.g.
QListBox::mousePressEventEx, QListBox::mouseReleaseEvent).
--
Michal Hocko
Index: qt-x11-free-3.3.8b/src/widgets/qlistbox.cpp
===
--- qt-x11-free-3.3.8b.orig/src/widgets/qlistbox.cpp 2009-05-19 14:01:28.0 +0200
+++ qt-x11-free-3.3.8b/src/widgets/qlistbox.cpp 2009-05-19 14:04:47.0 +0200
@@ -1482,6 +1482,7 @@ void QListBox::insertItem( const QListBo
if ( hasFocus() && !d->current ) {
d->current = d->head;
updateItem( d->current );
+ emit currentChanged( d->current );
emit highlighted( d->current );
emit highlighted( d->current->text() );
emit highlighted( index );
@@ -1538,6 +1539,7 @@ void QListBox::insertItem( const QListBo
if ( hasFocus() && !d->current ) {
d->current = d->head;
updateItem( d->current );
+ emit currentChanged( d->current );
emit highlighted( d->current );
emit highlighted( d->current->text() );
emit highlighted( index( d->current ) );
Bug#529435: QListBox::current set in insertItem without currentChanged emiting
On Tue, May 19, 2009 at 01:17:24PM +0200, Michal Hocko wrote:
> Package: qt-x11-free
> Severity: normal
>
> Hi,
> I have just noticed that buggy behavior in my application is caused by
> QListBox::current being set during insertItem without triggering
> currentChanged.
> My application uses currentChanged handler for enable/disable logic and
> so this doesn't work in case that box was empty.
>
> I am not sure whether this is correct or not, but it is at least
> inconsistent for cases like:
>
> box->insertItem(item, pos);
> box->setCurrentItem(pos);
>
> because this will trigger currentChanged signal only if box wasn't empty
> before.
>
> I have checked the source and really QListBox::insertItem does something
> like:
>
> if ( hasFocus() && !d->current ) {
> d->current = d->head;
> updateItem( d->current );
> emit highlighted( d->current );
> emit highlighted( d->current->text() );
> emit highlighted( index );
> }
>
> I think that we are missing emit currentChanged there.
I forgot to say that setCurrentItem after insertItem doesn't trigger
currentChanged because the setCurrentItem returns immediately if the
current is same as the given one which is exactly the case here.
--
Michal Hocko
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#529435: QListBox::current set in insertItem without currentChanged emiting
Package: qt-x11-free
Severity: normal
Hi,
I have just noticed that buggy behavior in my application is caused by
QListBox::current being set during insertItem without triggering currentChanged.
My application uses currentChanged handler for enable/disable logic and
so this doesn't work in case that box was empty.
I am not sure whether this is correct or not, but it is at least
inconsistent for cases like:
box->insertItem(item, pos);
box->setCurrentItem(pos);
because this will trigger currentChanged signal only if box wasn't empty
before.
I have checked the source and really QListBox::insertItem does something
like:
if ( hasFocus() && !d->current ) {
d->current = d->head;
updateItem( d->current );
emit highlighted( d->current );
emit highlighted( d->current->text() );
emit highlighted( index );
}
I think that we are missing emit currentChanged there.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-rc6-22ef37eed673587ac984965dc88ba94c68873291 (SMP w/2 CPU
cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#529431: akregator: Sometimes "unread" is more then "total"
Package: akregator Version: 4:4.2.2-1 Severity: minor *** Please type your report below this line *** Some feeds, eg, at the moment, Planet PHP (http://www.planet-php.net/ or http://www.planet-php.net/rdf/) cause incorrect totals to be generated where "unread" is more then "total". Currently in list view I see five items, four unread. The side pane is saying four unread out of total three. As soon as I delete an item correct totals are generated. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages akregator 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-4 GNU C Library: Shared libraries ii libgcc1 1:4.4.0-4 GCC support library ii libkdepim44:4.2.2-1 KDE PIM library ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libqt4-dbus 4.5.1-2Qt 4 D-Bus module ii libqt4-xml4.5.1-2Qt 4 XML module ii libqtcore44.5.1-2Qt 4 core module ii libqtgui4 4.5.1-2Qt 4 GUI module ii libstdc++64.4.0-4The GNU Standard C++ Library v3 akregator recommends no packages. akregator suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#520426: wishlist: please no dependency on kdebase-workspace-*
Hello, > The package should either contain the /usr/lib/kde4/kgreet_*.so files or > depend on kdebase-workspace-bin where the files are located now. Would like to see that files in an separate package, because i only wan to use kdm. Installing of kdebase-workspace-bin brought a lot of not-fun-stuff i just do not need. Thanks christian __ Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele ausländische Netze zum gleichen Preis! https://produkte.web.de/webde_sms/sms -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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-2Qt 4 D-Bus module ii libqtcore44.5.1-2Qt 4 core module ii libqtgui4 4.5.1-2Qt 4 GUI module ii libstdc++64.4.0-5The GNU Standard C++ Library v3 kgpg recommends no packages. kgpg suggests no packages. -- no debconf information Application: KGpg (kgpg), signal SIGSEGV 0x7f2662952831 in nanosleep () from /lib/libc.so.6 [Current thread is 0 (LWP 9015)] Thread 2 (Thread 0x7f2658a1f950 (LWP 9016)): #0 0x7f266297baf2 in select () from /lib/libc.so.6 #1 0x7f2663049936 in QProcessManager::run (this=0x20aacd0) at io/qprocess_unix.cpp:305 #2 0x7f2662f82742 in QThreadPrivate::start (arg=0x20aacd0) at thread/qthread_unix.cpp:189 #3 0x7f265eccbfaa in start_thread (arg=) at pthread_create.c:300 #4 0x7f266298229d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7f26656e9760 (LWP 9015)): [KCrash Handler] #5 0x004363c7 in _start ()
Processed: Re: Bug#529421: kde4/testing (drkonqi) crashes when I click display
Processing commands for cont...@bugs.debian.org: > reassign 529421 kdebase-runtime Bug#529421: kde4/testing (drkonqi) crashes when I click display Warning: Unknown package 'drkonqi' Bug reassigned from package `drkonqi' to `kdebase-runtime'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520426:
Hello, > The package should either contain the /usr/lib/kde4/kgreet_*.so files or > depend on kdebase-workspace-bin where the files are located now. Would like to see that files in an own package, because i only wan to use kdm. Installing of kdebase-workspace-bin brought a lot of not-fun-stuff i just do not need. Thanks christian __ Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele ausländische Netze zum gleichen Preis! https://produkte.web.de/webde_sms/sms -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 520426 is serious
Processing commands for cont...@bugs.debian.org: > severity 520426 serious Bug#520426: kdm misses the /usr/lib/kde4/kgreet_* files Severity set to `serious' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520426: still an issue.
still present in 4:4.2.2-2, solved the problem by installing the recommended package above. the severity for this bug could be raised as the package is in my opinion unusable in this state. grave: "makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package." important: "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." -- Martin -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
