[kontact] [Bug 417215] New: vcf import not working
https://bugs.kde.org/show_bug.cgi?id=417215 Bug ID: 417215 Summary: vcf import not working Product: kontact Version: 5.13.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-bugs@kde.org Reporter: axel.br...@gmx.de Target Milestone: --- SUMMARY Import of a vcf file does not work STEPS TO REPRODUCE 1. have a VCF file somewhere in the filesystem 2. open file with 'addressbook-importfile' (Mit Adressbuch-importdatei öffnen) 3. you see the 'addressbook-importfile' in the taskbar, but nothing is imported SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200201 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 417207] Notes widget doesn't launch when no window is active
https://bugs.kde.org/show_bug.cgi?id=417207 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 410612 *** -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 417207] New: Notes widget doesn't launch when no window is active
https://bugs.kde.org/show_bug.cgi?id=417207 Bug ID: 417207 Summary: Notes widget doesn't launch when no window is active Product: knotes Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: n_s_mend...@hotmail.com CC: myr...@kde.org Target Milestone: --- SUMMARY The Plasma notes widget doesn't work properly when put in the panel. More accurately, it doesn't show up when clicked on when no window is active - i.e. when I'm staring at the desktop or after writing stuff on the note or using any other panel widget. STEPS TO REPRODUCE 1. Put the notes plasmoid on the bottom default panel (stock manjaro KDE panel) 2. Click on the notes plasmoid to launch it. Nothing happens. 3. Open a program like a web browser and focus on it with the mouse 4. Click on the notes plasmoid to launchg it. It shows up as expected. 5. Write something inside the plasmoid. Click somewhere on the panel tray to hide the notes 6. Click on the notes plasmoid to launch it. OBSERVED RESULT The notes plasmoid doesn't launch when no windows is focused on (when showing desktop or when using the panel). EXPECTED RESULT The notes plasmoid should show up at all times when clicked on SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Manjaro up to date (05.02.2020) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 kernel_panic changed: What|Removed |Added CC||vic.m.iva...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] New: KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206
Bug ID: 417206
Summary: KMail wrong date in IMAP APPEND command
Product: kmail2
Version: 5.12.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: commands and actions
Assignee: kdepim-bugs@kde.org
Reporter: vic.m.iva...@gmail.com
Target Milestone: ---
SUMMARY
When copying an email from one account's folder (e.g. Inbox) to another
account's folder (e.g. Inbox again) the wrong email date is supplied in the
IMAP APPEND command. At present, KMail provides the current date/time string.
This is contrary to RFC 3501 section 6.3.11 which states:
If a date-time is specified, the internal date SHOULD be set in
the resulting message; otherwise, the internal date of the
resulting message is set to the current date and time by default
suggesting that, if possible, the message's internal date/time string should
take precedence.
STEPS TO REPRODUCE
1. Enable logging: "$ export KIMAP_LOGFILE=$HOME/kimap/kimap.log"
2. Copy (e.g. old) email from a folder in account A to a folder in account B
3. Observe logged IMAP communication, notably the APPEND command as logged
OBSERVED RESULT
For an email with internal date (i.e. has "Date" header) of "01-Jan-2010
12:34:56 +" the APPEND command, as logged, looks something like:
C: A04 APPEND "INBOX" (\Seen) "05-Feb-2020 10:20:30 +" {104666}
where the timestamp of the IMAP command is the time that the command was
submitted to the mail server, followed by the email source.
EXPECTED RESULT
The correct APPEND command under said conditions should instead look something
like:
C: A04 APPEND "INBOX" (\Seen) "01-Jan-2010 12:34:56 +" {104666}
since "01-Jan-2010 12:34:56 +" is the internal date available in the
message headers.
SOFTWARE/OS VERSIONS
KMail Version: 5.12.3
Linux/KDE Plasma: Gentoo Linux
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
also present in:
KMail Version: 5.12.3
Linux/KDE Plasma: Debian Testing
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
ADDITIONAL INFORMATION
The above issue appears to affect multi-part messages such as those containing
HTML as well as PGP encrypted messages. As far as I could tell, it does not
seem to affect plain text messages, though it may need further verification.
WHY IS THIS A PROBLEM
Most mail clients (including KMail) will show the timestamp of the internal
Date header. However, some web-based clients (such as GMail, as a popular
example) store and index messages based on the timestamp provided as per the
IMAP APPEND command.
This can make migrated email messages show up with incorrect timestamps an in
the wrong order which can also mess up with conversation view grouping. Another
problem is if KMail's message filtering is used to automatically PGP encrypt
incoming messages which are IMAP APPEND-ed post-encryption to the mail server,
thereby resulting in the same problem as with migrated emails.
In contrast, other mail clients (e.g. Thunderbird) will use the internal
timestamp in every case, as per the RFC.
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Eoghann Walker changed: What|Removed |Added CC||eogh...@blackisle.org.uk --- Comment #2 from Eoghann Walker --- -- Information about the crash - Kontact crashes when clicking Settings > Configure Kontact - What I was doing when the application crashed: nothing out of the ordinary, just trying to open the settings - The crash can be reproduced every time. Kontact Version: 4:19.12.1+p18.04+git20200204.0022-0 Operating System: KDE neon Testing Edition KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 Kernel Version: 4.15.0-76-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 11.7 GiB of RAM Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff921f7f340 (LWP 7569))] Thread 50 (Thread 0x7ff7dd235700 (LWP 7697)): #0 0x7ff91a3c39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x562adab66d68) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff91a3c39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x562adab66d18, cond=0x562adab66d40) at pthread_cond_wait.c:502 #2 0x7ff91a3c39f3 in __pthread_cond_wait (cond=0x562adab66d40, mutex=0x562adab66d18) at pthread_cond_wait.c:655 #3 0x7ff8e8499a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7ff8e8499607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7ff91a3bd6db in start_thread (arg=0x7ff7dd235700) at pthread_create.c:463 #6 0x7ff91e89288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 49 (Thread 0x7ff7de199700 (LWP 7696)): #0 0x7ff91a3c39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ff8680cd868) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff91a3c39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7ff8680cd818, cond=0x7ff8680cd840) at pthread_cond_wait.c:502 #2 0x7ff91a3c39f3 in __pthread_cond_wait (cond=0x7ff8680cd840, mutex=0x7ff8680cd818) at pthread_cond_wait.c:655 #3 0x7ff8e8499a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7ff8e8499607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7ff91a3bd6db in start_thread (arg=0x7ff7de199700) at pthread_create.c:463 #6 0x7ff91e89288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 48 (Thread 0x7ff7de99a700 (LWP 7695)): #0 0x7ff91a3c39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x562ada85c338) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff91a3c39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x562ada85c2e8, cond=0x562ada85c310) at pthread_cond_wait.c:502 #2 0x7ff91a3c39f3 in __pthread_cond_wait (cond=0x562ada85c310, mutex=0x562ada85c2e8) at pthread_cond_wait.c:655 #3 0x7ff8e8499a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7ff8e8499607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7ff91a3bd6db in start_thread (arg=0x7ff7de99a700) at pthread_create.c:463 #6 0x7ff91e89288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 47 (Thread 0x7ff7df19b700 (LWP 7694)): #0 0x7ff91a3c39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x562ada748528) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff91a3c39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x562ada7484d8, cond=0x562ada748500) at pthread_cond_wait.c:502 #2 0x7ff91a3c39f3 in __pthread_cond_wait (cond=0x562ada748500, mutex=0x562ada7484d8) at pthread_cond_wait.c:655 #3 0x7ff8e8499a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7ff8e8499607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7ff91a3bd6db in start_thread (arg=0x7ff7df19b700) at pthread_create.c:463 #6 0x7ff91e89288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 46 (Thread 0x7ff800a2b700 (LWP 7678)): #0 0x7ff91a3c3ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff800a2a6f0, expected=0, futex_word=0x7ff800a2a8c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7ff91a3c3ed9 in __pthread_cond_wait_common (abstime=0x7ff800a2a790, mutex=0x7ff800a2a878, cond=0x7ff800a2a8a0) at pthread_cond_wait.c:533 #2 0x7ff91a3c3ed9 in __pthread_cond_timedwait (cond=0x7ff800a2a8a0, mutex=0x7ff800a2a878, abstime=0x7ff800a2a790) at pthread_cond_wait.c:667 #3 0x7ff90ee82146 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff90ee82aed in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff90ee82c82 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff90ee3b7a1 in () at
[kmail2] [Bug 411424] kmail crash
https://bugs.kde.org/show_bug.cgi?id=411424 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Christoph Feck --- Bug 413664 has a better backtrace. *** This bug has been marked as a duplicate of bug 413664 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 413664] Kontact/E-Mail crashed on reading new Emails in IMAP folder
https://bugs.kde.org/show_bug.cgi?id=413664 Christoph Feck changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #1 from Christoph Feck --- *** Bug 411424 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 417195] New: Kontact crashes when opening a special mail
https://bugs.kde.org/show_bug.cgi?id=417195 Bug ID: 417195 Summary: Kontact crashes when opening a special mail Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: On KMail I've got four E-Mail accounts but only the posteo.de account is affected and there one Mail (received twice, first at 14:01 o'clock and second at 14:03 o'clock today) When I click to one of these mails Kontact crashes immediatelly, every time I try to. The received mails are from no-re...@deutschepost.de The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b72833f00 (LWP 6934))] Thread 53 (Thread 0x7f49eaefd700 (LWP 7049)): #0 0x7f4b85b5dc2f in __GI___poll (fds=0x7f49e00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4b8420ea3e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4b8420eb73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4b861206c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4b860c763b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4b85f00a75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4b85f01cc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 52 (Thread 0x7f49eb7fe700 (LWP 7046)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec635338) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec6352e8, cond=0x55a7ec635310) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec635310, mutex=0x55a7ec6352e8) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 51 (Thread 0x7f49ebfff700 (LWP 7045)): #0 0x7f4b84b672c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a7ec53d498) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f4b84b672c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a7ec53d448, cond=0x55a7ec53d470) at pthread_cond_wait.c:508 #2 0x7f4b84b672c6 in __pthread_cond_wait (cond=0x55a7ec53d470, mutex=0x55a7ec53d448) at pthread_cond_wait.c:638 #3 0x7f4b6b2b591b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f4b6b2b553b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 50 (Thread 0x7f4a0c8f9700 (LWP 7043)): #0 0x7f4b84b676e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f4a0c8f8470, clockid=, expected=0, futex_word=0x7f4a0c8f85b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f4b84b676e0 in __pthread_cond_wait_common (abstime=0x7f4a0c8f8470, clockid=, mutex=0x7f4a0c8f8568, cond=0x7f4a0c8f8590) at pthread_cond_wait.c:520 #2 0x7f4b84b676e0 in __pthread_cond_timedwait (cond=0x7f4a0c8f8590, mutex=0x7f4a0c8f8568, abstime=0x7f4a0c8f8470) at pthread_cond_wait.c:656 #3 0x7f4b7e6ac10b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4b7e6acab2 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4b7e6acba6 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4b7e66e705 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4b7e670c6b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4b7e671258 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4b7e6aec75 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4b84b60669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f4b85b6a323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 49 (Thread 0x7f4a0d0fa700 (LWP 7041)): #0
[kmail2] [Bug 417184] New: Crash when deleting imported folder
https://bugs.kde.org/show_bug.cgi?id=417184 Bug ID: 417184 Summary: Crash when deleting imported folder Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christo...@krop.fr Target Milestone: --- Using master (a few days old): What I did: File / import messages and I chose "Import KMail Maildirs and Folder Structure" to import an old maildir folder. Import went mostly fine. Just an akonadiserver crash at the end of the process, however: After deleting the imported folders, KMail crashes: #5 0x7f39dd9b4aef in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1894 #6 0x7f39dd9b4aef in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffe42cdd100, msg=msg@entry=0x7f39ddca1ea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #7 0x7f39dd9b3f2f in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #8 0x7f39dcfd45ab in MessageList::Core::StorageModel::savePreSelectedMessage(unsigned long) (this=0x740df60, uniqueIdOfMessage=427330) at /data/kde/src/messagelib/messagelist/src/core/storagemodelbase.cpp:58 #9 0x7f39dcfec1fd in MessageList::Core::Widget::saveCurrentSelection() (this=0x199ce90) at /data/kde/src/messagelib/messagelist/src/core/widgetbase.cpp:328 #10 0x7f39dd028199 in MessageList::Pane::Private::setCurrentFolder(QModelIndex const&) (this=0x191cf60, etmIndex=...) at /data/kde/src/messagelib/messagelist/src/pane.cpp:490 #11 0x7f39dd029ef7 in MessageList::Pane::setCurrentFolder(Akonadi::Collection const&, QModelIndex const&, bool, MessageList::Core::PreSelectionMode, QString const&) (this=0x190dce0, collection=..., etmIndex=..., preSelectionMode=MessageList::Core::PreSelectNewestCentered, overrideLabel=...) at /data/kde/src/messagelib/messagelist/src/pane.cpp:742 #12 0x7f39defd1dba in KMMainWidget::slotShowSelectedFolderInPane() (this=0x153a1a0) at /data/kde/src/kmail/src/kmmainwidget.cpp:561 #13 0x7f39deff9094 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KMMainWidget::*)()>::call(void (KMMainWidget::*)(), KMMainWidget*, void**) (f=(void (KMMainWidget::*)(class KMMainWidget * const)) 0x7f39defd1d10 , o=0x153a1a0, arg=0x6ddf588) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #14 0x7f39deff9008 in QtPrivate::FunctionPointer::call, void>(void (KMMainWidget::*)(), KMMainWidget*, void**) (f=(void (KMMainWidget::*)(class KMMainWidget * const)) 0x7f39defd1d10 , o=0x153a1a0, arg=0x6ddf588) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #15 0x7f39deff8f35 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x8083090, r=0x153a1a0, a=0x6dd at /usr/include/qt5/QtCore/qobjectdefs_impl.h:414 #16 0x7f39ddbefa79 in QObject::event(QEvent*) (this=this@entry=0x153a1a0, e=e@entry=0x6ddf540) at kernel/qobject.cpp:1339 #17 0x7f39de70d565 in QWidget::event(QEvent*) (this=0x153a1a0, event=0x6ddf540) at kernel/qwidget.cpp:9092 #18 0x7f39de6cacaf in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x113d000, receiver=receiver@entry=0x153a1a0, e=e@entry=0x6ddf540) at kernel/qapplication.cpp:3684 -- You are receiving this mail because: You are the assignee for the bug.
