[kmail2] [Bug 481135] New: Closing KMail window with system tray icon enabled doesn't always close the window
https://bugs.kde.org/show_bug.cgi?id=481135 Bug ID: 481135 Summary: Closing KMail window with system tray icon enabled doesn't always close the window Classification: Applications Product: kmail2 Version: 5.240.95 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: stefano.cro...@alice.it Target Milestone: --- SUMMARY In KF5, when the system tray icon is enabled in KMail, closing the window with Alt+F4 or with the X button on the title bar used to close the window, leaving only the system tray icon. However, with KF6 version of KMail, this only happens a few times (often only once) after the application has been launched. After that, closing the window minimizes it instead, leaving it on the task bar. When this starts to happen, there's no way to restore the correct behaviour except quitting KMail altogether (using the File/Quit menu entry). This doesn't seem to happen if closing the window by clicking on the KMail icon in the system tray. When the behaviour described above starts happening, clicking on the KMail icon in the system tray shows the window again, but it forget its maximized state. This doesn't happen when restoring it by clicking on the corresponding entry in the task. STEPS TO REPRODUCE 1. Launch KMail and ensure that the "enable system tray icon" option is checked 2. Close the KMail window using the X button on the title bar or the Alt+F4 shortcut. It may be necessary to display the window and repeat this a couple of times to trigger the bug OBSERVED RESULT KMail window is minimized and still visible in the task bar. When clicking on the system tray icon to show it again, the window is not maximized, even if it was maximized when I closed it EXPECTED RESULT KMail window gets closed and it disappear from the task bar. When clicking on its system tray icon, KMail window is restored keeping the previous maximized state. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Gentoo doesn't provide official packages for the KF6 version of KDE Gear, so I installed them using the Gentoo KDE overlay -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 392450] kontact 5.7.3 won't start after changing its locale
https://bugs.kde.org/show_bug.cgi?id=392450 Stefano changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Stefano --- It seems to work now. Version 5.21.3 (22.08.3) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 381538] Menu bar disappeared
https://bugs.kde.org/show_bug.cgi?id=381538 Stefano changed: What|Removed |Added Platform|Neon|OpenSUSE Version|unspecified |5.21.3 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Stefano --- I confirm this issue is still there on Kontact 5.21.3 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 417396] Kontact crashes opening settings.
https://bugs.kde.org/show_bug.cgi?id=417396 Stefano changed: What|Removed |Added CC||erist...@cryptolab.net -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 294502] KMail crashes when removing an attachement from a mail
https://bugs.kde.org/show_bug.cgi?id=294502 Stefano changed: What|Removed |Added CC||erist...@cryptolab.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 Stefano Crocco changed: What|Removed |Added CC||stefano.cro...@alice.it -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 407300] New: Sidebar's Components Icons are blurred when shown without text
https://bugs.kde.org/show_bug.cgi?id=407300 Bug ID: 407300 Summary: Sidebar's Components Icons are blurred when shown without text Product: kontact Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: erist...@cryptolab.net Target Milestone: --- Created attachment 119895 --> https://bugs.kde.org/attachment.cgi?id=119895=edit Screenshot SUMMARY The sidebar's icons looks really bad, enlarged and blurred, when shown without the underlying text. See included screenshot. STEPS TO REPRODUCE 1. Right click on kontact's sidebar and change between sizes and with or without text OBSERVED RESULT Without text, the icons appears at the wrong size and blurred. EXPECTED RESULT The icons should maintain the same size and crispness even when disabling the text labels. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #6 from Stefano --- Update: If I close kmail with the close button, the toolbar is hidden at the next launch, but not if I close it with the CTRL-Q shortcut. In both case, I miss the statusbar and I can't find how to restore it. Update 2: This issue doesn't occur when kmail is launched within kontact. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #4 from Stefano --- @dS810 of course, but when closing and reopening kmail, it will be disabled again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 --- Comment #2 from Stefano --- Another thing that I didn't noticed before, is that the status bar is vanished and I can't find how to make it visible again. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395752] New: kmail keeps hiding the toolbar upon restart
https://bugs.kde.org/show_bug.cgi?id=395752 Bug ID: 395752 Summary: kmail keeps hiding the toolbar upon restart Product: kmail2 Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: erist...@cryptolab.net Target Milestone: --- Created attachment 113511 --> https://bugs.kde.org/attachment.cgi?id=113511=edit kmail2rc diffs This started happening recently on my Arch Linux install. Plasma: 5.13.1 Frameworks: 5.47.0 Qt: 5.11.1 Steps to reproduce: - Launch kmail The toolbar is hidden - Enable the toolbar - Close kmail - Open kmail The toolbar is hidden again. Looking at kmail2rc I see four changes between launches. See attached diff. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394738] Akregator doesn't save hidden columns in feed list after updating to Qt 5.11
https://bugs.kde.org/show_bug.cgi?id=394738 --- Comment #4 from Stefano --- For me, this looks fixed in Archlinux with qt-5.11.1 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394738] Akregator doesn't save hidden columns in feed list after updating to Qt 5.11
https://bugs.kde.org/show_bug.cgi?id=394738 --- Comment #2 from Stefano --- After updating my Neon installation, I have the same issue there too. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 394738] New: Akregator doesn't save hidden columns in feed list after updating to Qt 5.11
https://bugs.kde.org/show_bug.cgi?id=394738 Bug ID: 394738 Summary: Akregator doesn't save hidden columns in feed list after updating to Qt 5.11 Product: akregator Version: 5.8.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: erist...@cryptolab.net Target Milestone: --- Created attachment 112902 --> https://bugs.kde.org/attachment.cgi?id=112902=edit Removing the columns, then starting akregator again After updating Qt to 5.11, in the feed list appeared two columns which I didn't enabled: Unread and Total. Even if I disable them, they return when launching akregator again. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 392450] kontact 5.7.3 won't start after changing its locale
https://bugs.kde.org/show_bug.cgi?id=392450 --- Comment #1 from Stefano <erist...@cryptolab.net> --- I don't even know where to look to restore to default its locale. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 392450] New: kontact 5.7.3 won't start after changing its locale
https://bugs.kde.org/show_bug.cgi?id=392450 Bug ID: 392450 Summary: kontact 5.7.3 won't start after changing its locale Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: erist...@cryptolab.net Target Milestone: --- I changed the application locale because I wanted to do some screenshots in English. I did it through the Help menu, the closed the application. Now, every time I start it, it crashes before showing any window. There isn't even a drkonqui crash window, just some info in the konsole: stefano@neon:~/.local/share$ kontact -v Icon theme "gnome" not found. kontact 5.7.3 stefano@neon:~/.local/share$ kontact Icon theme "gnome" not found. KSycoca unavailable. Kontact will be unable to find plugins. Received signal 6 #0 0x7f94b5fcda25 #1 0x7f94b4cb495b #2 0x7f94b5fcddbd #3 0x7f94c53874b0 #4 0x7f94c5387428 gsignal #5 0x7f94c538902a abort #6 0x7f94c5d4c311 QMessageLogger::fatal() #7 0x7f94c84a10e1 Kontact::MainWindow::waitForKSycoca() #8 0x7f94c84a7f18 Kontact::MainWindow::initObject() #9 0x7f94c84a83d6 Kontact::MainWindow::MainWindow() #10 0x0040527a #11 0x7f94c827eced KontactInterface::PimUniqueApplication::start() #12 0x0040437b #13 0x7f94c5372830 __libc_start_main #14 0x004049c9 _start r8: 0049 r9: 7f94c8a02900 r10: 0008 r11: 0206 r12: 7ffe810cd740 r13: r14: 7f94c5fe7dc0 r15: 7ffe810cdd60 di: 3b50 si: 3b50 bp: 7ffe810cd720 bx: 7ffe810cd730 dx: 0006 ax: cx: 7f94c5387428 sp: 7ffe810cd4f8 ip: 7f94c5387428 efl: 0206 cgf: 002b0033 erf: trp: msk: cr2: [end of stack trace] Calling _exit(1). Core file will not be generated. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 389945] Akregator segmentation fault on startup
https://bugs.kde.org/show_bug.cgi?id=389945 Stefano <erist...@cryptolab.net> changed: What|Removed |Added CC||erist...@cryptolab.net -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 389945] Akregator segmentation fault on startup
https://bugs.kde.org/show_bug.cgi?id=389945 --- Comment #1 from Stefano <erist...@cryptolab.net> --- Created attachment 110433 --> https://bugs.kde.org/attachment.cgi?id=110433=edit New crash information added by DrKonqi akregator (5.7.1) using Qt 5.9.3 - What I was doing when the application crashed: I tried to launch akregator from the application menu and konsole, but it crashed both times befor showing any window. -- Backtrace (Reduced): #9 0x7fb0dbb2061a in qobject_cast<Akregator::WebEngineFrame*> (object=0x1037f60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514 #10 Akregator::FrameManager::saveProperties (this=0xe76770, config=...) at /workspace/build/src/frame/framemanager.cpp:275 #11 0x7fb0a33add8f in Akregator::MainWidget::saveProperties (this=, config=...) at /workspace/build/src/mainwidget.cpp:1231 #12 0x7fb0a33a69fd in Akregator::Part::saveCrashProperties (this=0xd791c0) at /workspace/build/src/akregator_part.cpp:780 #13 0x7fb0a33a6a75 in Akregator::Part::slotAutoSave (this=) at /workspace/build/src/akregator_part.cpp:785 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 381538] Menu bar disappeared
https://bugs.kde.org/show_bug.cgi?id=381538 Stefano <erist...@cryptolab.net> changed: What|Removed |Added CC||erist...@cryptolab.net --- Comment #4 from Stefano <erist...@cryptolab.net> --- I can confirm the same behaviour. It happens every time I enable the global manu (in titlebar or panel). Every sub-applications I select in kontact, gets a MenuBar=Disabled entry in the rc file. When I return to the default in-application menubar, the menubar isn't restored and it's impossible to enable it again with C-m. I have to manually remove all the MenuBar=Disabled entries. The same happens with ksysguard. (Do you prefer that I open a separate bug report for ksysguard?) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376396] Kmail crashes when starting it
https://bugs.kde.org/show_bug.cgi?id=376396 --- Comment #1 from Stefano Carlesso <stefano.carle...@yahoo.it> --- Created attachment 104000 --> https://bugs.kde.org/attachment.cgi?id=104000=edit New crash information added by DrKonqi kmail (5.4.2) using Qt 5.7.1 - What I was doing when the application crashed: Starting Kmail both from the Plasma Application Menu and from the terminal result in the application closing unexpectedly. When Launching from the terminal, I get this message ``` $ kmail org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default. Could not find QtWebEngineProcess *** KMail got signal 6 (Exiting) *** Dead letters dumped. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 5983 KCrash: Arguments: /usr/bin/kmail KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1001/kdeinit5__0 [1] + Stopped (signal) kmail ``` - Custom settings of the application: I created a new user to test Kmail. Default settings. I haven't setup any mail account yet. -- Backtrace (Reduced): #6 0x7f8ccd08e428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f8ccd09002a in __GI_abort () at abort.c:89 #8 0x7f8ccda4f811 in QMessageLogger::fatal(char const*, ...) const (context=..., message=) at global/qlogging.cpp:1682 #9 0x7f8ccda4f811 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffdd880ef60, msg=msg@entry=0x7f8cbb8d60ad "Could not find %s") at global/qlogging.cpp:793 #10 0x7f8cb8171ea6 in WebEngineLibraryInfo::getPath(int) () at /workspace/build/src/core/web_engine_library_info.cpp:149 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376396] Kmail crashes when starting it
https://bugs.kde.org/show_bug.cgi?id=376396 Stefano Carlesso <stefano.carle...@yahoo.it> changed: What|Removed |Added CC||stefano.carle...@yahoo.it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376396] New: Kmail crashes when starting it
https://bugs.kde.org/show_bug.cgi?id=376396 Bug ID: 376396 Summary: Kmail crashes when starting it Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: stefano.carle...@yahoo.it Target Milestone: --- Application: kmail (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.4.0-62-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: Every time I start Kmail fom both the Plasma Application Menu and the terminal, it crashes. When starting from terminal, I get this message. ``` ste@pegasus (~): kmail Pass a valid window to KWallet::Wallet::openWallet(). org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default. Could not find QtWebEngineProcess *** KMail got signal 6 (Exiting) *** Dead letters dumped. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 4885 KCrash: Arguments: /usr/bin/kmail KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped kmail ``` - Custom settings of the application: I've setup two accounts: Yahoo Mail and GMX.com both using the IMAP protocol. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f4ab0ea00 (LWP 4741))] Thread 6 (Thread 0x7f0f2700 (LWP 4750)): #0 0x7f0f6ee82929 in g_main_context_prepare (context=context@entry=0x7f0f28000990, priority=priority@entry=0x7f0f2fffea80) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3453 #1 0x7f0f6ee832bb in g_main_context_iterate (context=context@entry=0x7f0f28000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3820 #2 0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f28000990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #3 0x7f0f7af5475b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0f280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0f7aeff0ba in QEventLoop::exec(QFlags) (this=this@entry=0x7f0f2fffebc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f0f7ad2ef64 in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f0f7ad33b48 in QThreadPrivate::start(void*) (arg=0x1aa7370) at thread/qthread_unix.cpp:368 #7 0x7f0f70bdc6ba in start_thread (arg=0x7f0f2700) at pthread_create.c:333 #8 0x7f0f7a42a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f0f3ce4c700 (LWP 4748)): #0 0x7f0f6ee82da0 in g_main_context_check (context=context@entry=0x7f0f34000990, max_priority=2147483647, fds=fds@entry=0x7f0f34003020, n_fds=n_fds@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3673 #1 0x7f0f6ee83330 in g_main_context_iterate (context=context@entry=0x7f0f34000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837 #2 0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f34000990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #3 0x7f0f7af5475b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f0f340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0f7aeff0ba in QEventLoop::exec(QFlags) (this=this@entry=0x7f0f3ce4bbc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f0f7ad2ef64 in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f0f7ad33b48 in QThreadPrivate::start(void*) (arg=0x1a95910) at thread/qthread_unix.cpp:368 #7 0x7f0f70bdc6ba in start_thread (arg=0x7f0f3ce4c700) at pthread_create.c:333 #8 0x7f0f7a42a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f0f3d6c6700 (LWP 4747)): #0 0x7f0f7a41eb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0f6ee8338c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f0f30002e70, timeout=, context=0x7f0f3990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f0f6ee8338c in g_main_context_iterate (context=context@entry=0x7f0f3990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f3990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4
[kmail2] [Bug 332249] Quick filter does not search body of emails never opened in kmail.
https://bugs.kde.org/show_bug.cgi?id=332249 --- Comment #10 from Stefano <stava...@unina.it> --- This bug is not present anymore, I believe it can be marked as resolved. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 332249] Quick filter does not search body of emails never opened in kmail.
https://bugs.kde.org/show_bug.cgi?id=332249 Stefano stava...@unina.it changed: What|Removed |Added CC||stava...@unina.it --- Comment #8 from Stefano stava...@unina.it --- I also use imap disconnected and suffer from the same issue (quick filter does not return all the results it should). Indeed, the Inbox folder is partially indexed: from Properties-Maintenance I see that only 10.933 items out of 34.253 have been indexed. Is there a way to force the indexing of all the emails in a folder? Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 289832] kmail show wrong mail
https://bugs.kde.org/show_bug.cgi?id=289832 --- Comment #2 from Stefano stavallo unina it 2012-02-01 08:33:28 --- This problem is solved since the first RC. Reporter might close this bug. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 289832] kmail show wrong mail
https://bugs.kde.org/show_bug.cgi?id=289832 Stefano stava...@unina.it changed: What|Removed |Added CC||stava...@unina.it --- Comment #1 from Stefano stavallo unina it 2011-12-27 10:24:48 --- I have the same problem. I am using kontact 4.7.95 and disconnected IMAP. After deleting a message, everything is messed up: when clicking on mails, sometimes no content is shown, sometimes the content of a different email is shown. This is with a fresh new account (deleted .kde4, .config and .local). On another computer, 4.8beta2 works fine. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 281087] New: kmail crash on starting
https://bugs.kde.org/show_bug.cgi?id=281087 Summary: kmail crash on starting Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefanol...@starpeoplesrl.it Application: kontact (4.4.8) KDE Platform Version: 4.5.3 (KDE 4.5.3) Qt Version: 4.7.0 Operating System: Linux 2.6.32-25-generic i686 Distribution: Ubuntu 10.04.3 LTS -- Information about the crash: i can't open kmail because it crash immediatly The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb78c4730 (LWP 9706))] Thread 2 (Thread 0xb0bb8b70 (LWP 9719)): #0 0x00fdd422 in __kernel_vsyscall () #1 0x00c12b86 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x084574eb in g_poll () from /lib/libglib-2.0.so.0 #3 0x0844a0ac in ?? () from /lib/libglib-2.0.so.0 #4 0x0844a4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x06c8b82f in QEventDispatcherGlib::processEvents (this=0xa05ce50, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #6 0x06c5ba99 in QEventLoop::processEvents (this=0xb0bb8270, flags=) at kernel/qeventloop.cpp:149 #7 0x06c5bf1a in QEventLoop::exec (this=0xb0bb8270, flags=...) at kernel/qeventloop.cpp:201 #8 0x06b58c5e in QThread::exec (this=0x96ed3e0) at thread/qthread.cpp:490 #9 0x06c3a9ab in QInotifyFileSystemWatcherEngine::run (this=0x96ed3e0) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x06b5bf39 in QThreadPrivate::start (arg=0x96ed3e0) at thread/qthread_unix.cpp:266 #11 0x00ccb96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0x00c20a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb78c4730 (LWP 9706)): [KCrash Handler] #7 0x014b6c37 in KHTMLPart::findFrameParent (this=0x0, callingPart=0x0, f=..., childFrame=0xbfdd161c) at ../../khtml/khtml_part.cpp:5188 #8 0x014b6e54 in KHTMLPart::findFrame (this=0x0, f=...) at ../../khtml/khtml_part.cpp:5218 #9 0x015b03d7 in DOM::HTMLFrameElementImpl::ensureUniqueName (this=0xa0db8f0) at ../../khtml/html/html_baseimpl.cpp:277 #10 0x015b0b9c in DOM::HTMLIFrameElementImpl::parseAttribute (this=0xa0db8f0, attr=0xa0db0e4) at ../../khtml/html/html_baseimpl.cpp:748 #11 0x01556584 in DOM::ElementImpl::setAttributeMap (this=0xa0db8f8, list=0xa0db0b8) at ../../khtml/xml/dom_elementimpl.cpp:586 #12 0x0158cd91 in khtml::KHTMLParser::parseToken (this=0xa0995a0, t=0xa09b9fc) at ../../khtml/html/htmlparser.cpp:278 #13 0x0158d653 in khtml::HTMLTokenizer::processToken (this=0xa09b9e8) at ../../khtml/html/htmltokenizer.cpp:2040 #14 0x015951ae in khtml::HTMLTokenizer::parseTag (this=0xa09b9e8, src=...) at ../../khtml/html/htmltokenizer.cpp:1501 #15 0x01596b91 in khtml::HTMLTokenizer::write (this=0xa09b9e8, str=..., appendData=false) at ../../khtml/html/htmltokenizer.cpp:1798 #16 0x01539609 in DOM::DocumentImpl::write (this=0xa096fe0, text=...) at ../../khtml/xml/dom_docimpl.cpp:1688 #17 0x015397cb in DOM::DocumentImpl::write (this=0xa096fe0, text=...) at ../../khtml/xml/dom_docimpl.cpp:1677 #18 0x017b421e in DOM::HTMLDocument::write (this=0xbfdd1aa0, text=...) at ../../khtml/dom/html_document.cpp:218 #19 0xb3413258 in KMail::HTMLQuoteColorer::process (this=0xbfdd1b00, htmlSource=...) at ../../kmail/htmlquotecolorer.cpp:37 #20 0xb32690a4 in KMail::ObjectTreeParser::processTextHtmlSubtype (this=0xbfdd1cd0, curNode=0x9cc5a18) at ../../kmail/objecttreeparser.cpp:1016 #21 0xb32858bb in process (this=0xa095388, otp=0xbfdd1cd0, node=0x9cc5a18, result=...) at ../../kmail/bodypartformatter.cpp:107 #22 0xb3278a6b in KMail::ObjectTreeParser::parseObjectTree (this=0xbfdd1cd0, node=0x9cc5a18) at ../../kmail/objecttreeparser.cpp:318 #23 0xb3278f47 in KMail::ObjectTreeParser::stdChildHandling (this=0xbfdd1f30, child=0x9cc5a18) at ../../kmail/objecttreeparser.cpp:1278 #24 0xb3279148 in KMail::ObjectTreeParser::processMultiPartAlternativeSubtype (this=0xbfdd1f30, node=0x9cc5838) at ../../kmail/objecttreeparser.cpp:1325 #25 0xb328577b in process (this=0xa093420, otp=0xbfdd1f30, node=0x9cc5838, result=...) at ../../kmail/bodypartformatter.cpp:119 #26 0xb3278a6b in KMail::ObjectTreeParser::parseObjectTree (this=0xbfdd1f30, node=0x9cc5838) at ../../kmail/objecttreeparser.cpp:318 #27 0xb30d5aa9 in KMReaderWin::parseMsg (this=0x9add7b8, aMsg=0xa066698) at ../../kmail/kmreaderwin.cpp:1612 #28 0xb30c64b3 in KMReaderWin::displayMessage (this=0x9add7b8) at ../../kmail/kmreaderwin.cpp:1536 #29 0xb30c669d in KMReaderWin::updateReaderWin (this=0x9add7b8) at ../../kmail/kmreaderwin.cpp:1479 #30 0xb30d9424 in KMReaderWin::qt_metacall (this=0x9add7b8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfdd22cc) at ./kmreaderwin.moc:179 #31 0x06c62d4a in QMetaObject::metacall (object=0x9add7b8, cl=7536737, idx=33, argv=0xbfdd22cc) at
[Bug 278446] New: Random KMail crash when downloading mail
https://bugs.kde.org/show_bug.cgi?id=278446 Summary: Random KMail crash when downloading mail Product: kmail2 Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Application: kmail (2.1.96) KDE Platform Version: 4.6.95 (4.7 RC2) Qt Version: 4.7.3 Operating System: Linux 2.6.39-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: KMail was sitting in system tray and automatically downloading mail from a POP account when it suddenly crashed The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fea0c6af760 (LWP 2953))] Thread 2 (Thread 0x7fe9f4ac3700 (LWP 3277)): #0 0x7fea077ef49c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe9fe6444bd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fe9fe6445b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fea077eabda in start_thread () from /lib64/libpthread.so.0 #4 0x7fea0996f0bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fea0c6af760 (LWP 2953)): [KCrash Handler] #6 operator!= (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qbasicatomic.h:75 #7 detach (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qmap.h:202 #8 remove (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qmap.h:660 #9 KPIM::ProgressItem::removeChild (this=0x5dbf868, kiddo=value optimized out) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/progressmanager.cpp:72 #10 0x7fea037fe08f in KPIM::ProgressItem::setComplete (this=0x5d58800) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/progressmanager.cpp:57 #11 0x7fea037ff97b in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x5e25440, instance=...) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/agentprogressmonitor.cpp:87 #12 0x7fea037ffbaa in KPIM::AgentProgressMonitor::qt_metacall (this=0x1d5b7d0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff50202af0) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95_build/libkdepim/agentprogressmonitor.moc:78 #13 0x7fea0a2c964f in QMetaObject::activate (sender=0xc58a80, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3278 #14 0x7fea05dae905 in Akonadi::AgentManager::instanceStatusChanged (this=0xb20020, _t1=value optimized out) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanager.moc:177 #15 0x7fea05db4700 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x9cfc60, identifier=value optimized out, status=0, msg=...) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95/akonadi/agentmanager.cpp:129 #16 0x7fea05db4ee6 in Akonadi::AgentManager::qt_metacall (this=0xc58a80, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff50202ca0) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanager.moc:131 #17 0x7fea0a2c964f in QMetaObject::activate (sender=0xc662a0, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3278 #18 0x7fea05ec35bb in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=0xb20020, _t1=value optimized out, _t2=0, _t3=value optimized out) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanagerinterface.moc:285 #19 0x7fea05ec3b8f in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall (this=0xc662a0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff502033e0) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanagerinterface.moc:167 #20 0x7fea07a26879 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:941 #21 0x7fea07a3063f in QDBusCallDeliveryEvent::placeMetaCall (this=0x7fea000a, object=0x20) at qdbusintegrator_p.h:103 #22 0x7fea0a2c389e in QObject::event (this=0xc662a0, e=0xb20020) at kernel/qobject.cpp:1217 #23 0x7fea0a7aa69c in QApplicationPrivate::notify_helper (this=0xae5ba0, receiver=0xc662a0, e=0x5935ff0) at kernel/qapplication.cpp:4462 #24 0x7fea0a7afa3d in QApplication::notify
[Bug 243826] KMail2 does not complete the initial synchronization of a disconnected imap account
https://bugs.kde.org/show_bug.cgi?id=243826 Stefano stava...@unina.it changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #2 from Stefano stavallo unina it 2011-07-14 07:58:55 --- Closing this bug because the issue is no longer present in KMail 2.0.95. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 277454] New: new messages in ignored thread sometimes not marked as ignored
https://bugs.kde.org/show_bug.cgi?id=277454 Summary: new messages in ignored thread sometimes not marked as ignored Product: kmail2 Version: 2.0.95 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 2.0.95 OS:Linux If there's a thread marked as ignored, when I download new mail, any new messages belonging to it should be marked as ignored as well. Usually this happens. Sometimes, however, the new messages, while being correctly inserted in the thread, are not marked as ignored. When this happens, the thread seems to loose its ignored status, since any message later added to it aren't marked as ignored. When this happens, I have to toggle the ignored status on the thread twice to get it back to the current status: the first time, the thread becomes not ignored, the second time it becomes correctly ignored again Reproducible: Sometimes Steps to Reproduce: Mark a thread as ignored, then download new mail containing messages which belong to the ignored thread Actual Results: Sometimes, the new messages in the thread are not marked as ignored Expected Results: The new messages in the thread should be marked as ignored -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Stefano Crocco stefano.cro...@alice.it changed: What|Removed |Added CC||stefano.cro...@alice.it --- Comment #1 from Stefano Crocco stefano crocco alice it 2011-06-20 17:47:31 --- The same is happening to me with a resource of type VCard directory. I'm using KDE 4.7 beta 1 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 274028] New: Crash on delete
https://bugs.kde.org/show_bug.cgi?id=274028 Summary: Crash on delete Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s.g...@softime.it Application: kmail (1.13.5) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.0 Operating System: Linux 2.6.35-29-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: I was deleting emails from an Imap account with 500+ emails. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f672b5f6820 (LWP 1955))] Thread 3 (Thread 0x7f6706dc8700 (LWP 3998)): #0 0x7f671fb18f90 in ?? () from /lib/libglib-2.0.so.0 #1 0x7f671fb1945c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #2 0x7f67288e51e6 in QEventDispatcherGlib::processEvents (this=0x2f2fc50, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417 #3 0x7f67288b7a02 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #4 0x7f67288b7dec in QEventLoop::exec (this=0x7f6706dc7cf0, flags=) at kernel/qeventloop.cpp:201 #5 0x7f67287c22fd in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #6 0x7f67288975f8 in QInotifyFileSystemWatcherEngine::run (this=0x2f2f240) at io/qfilesystemwatcher_inotify.cpp:248 #7 0x7f67287c527e in QThreadPrivate::start (arg=0x2f2f240) at thread/qthread_unix.cpp:266 #8 0x7f6725b75971 in start_thread (arg=value optimized out) at pthread_create.c:304 #9 0x7f6727f9792d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7f670431c700 (LWP 10651)): #0 0x7f671fb18b61 in g_main_context_prepare () from /lib/libglib-2.0.so.0 #1 0x7f671fb18e78 in ?? () from /lib/libglib-2.0.so.0 #2 0x7f671fb1945c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7f67288e51e6 in QEventDispatcherGlib::processEvents (this=0x3afefb0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417 #4 0x7f67288b7a02 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7f67288b7dec in QEventLoop::exec (this=0x7f670431bcf0, flags=) at kernel/qeventloop.cpp:201 #6 0x7f67287c22fd in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #7 0x7f67288975f8 in QInotifyFileSystemWatcherEngine::run (this=0x3abe090) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f67287c527e in QThreadPrivate::start (arg=0x3abe090) at thread/qthread_unix.cpp:266 #9 0x7f6725b75971 in start_thread (arg=value optimized out) at pthread_create.c:304 #10 0x7f6727f9792d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f672b5f6820 (LWP 1955)): [KCrash Handler] #6 ref (this=0x801ecc0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QList (this=0x801ecc0) at /usr/include/qt4/QtCore/qlist.h:118 #8 KMail::FolderJob::msgList (this=0x801ecc0) at ../../kmail/folderjob.cpp:120 #9 0x7f6729f7baca in KMAcctImap::ignoreJobsForMessage (this=0x2652c90, msg=value optimized out) at ../../kmail/kmacctimap.cpp:217 #10 0x7f672a0917d7 in KMMoveCommand::execute (this=0x851ca10) at ../../kmail/kmcommands.cpp:2208 #11 0x7f672a08082a in KMCommand::slotPostTransfer (this=0x851ca10, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:295 #12 0x7f672a08cb13 in KMCommand::qt_metacall (this=0x851ca10, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fffee69e780) at ./kmcommands.moc:93 #13 0x7f672a08cdc0 in KMMoveCommand::qt_metacall (this=0x7fffee69e380, _c=134343872, _id=174, _a=0x274b0) at ./kmcommands.moc:1971 #14 0x7f67288d0b27 in QMetaObject::activate (sender=0x851ca10, m=value optimized out, local_signal_index=value optimized out, argv=0x274b0) at kernel/qobject.cpp:3280 #15 0x7f672a07d9ce in KMCommand::messagesTransfered (this=0x7fffee69e380, _t1=KMCommand::OK) at ./kmcommands.moc:108 #16 0x7f672a0924ec in KMCommand::transferSelectedMsgs (this=0x851ca10) at ../../kmail/kmcommands.cpp:393 #17 0x7f672a092708 in KMCommand::slotStart (this=0x851ca10) at ../../kmail/kmcommands.cpp:287 #18 0x7f672a08caf6 in KMCommand::qt_metacall (this=0x851ca10, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x3cddb10) at ./kmcommands.moc:92 #19 0x7f672a08cdc0 in KMMoveCommand::qt_metacall (this=0x7fffee69e380, _c=134343872, _id=174, _a=0x274b0) at ./kmcommands.moc:1971 #20 0x7f67288cabde in QObject::event (this=0x851ca10, e=0x7fffee69e380) at kernel/qobject.cpp:1219 #21 0x7f6728da3fdc in QApplicationPrivate::notify_helper
[Bug 257977] New: messages in threads marked as ignored are treated as unread
https://bugs.kde.org/show_bug.cgi?id=257977 Summary: messages in threads marked as ignored are treated as unread Product: kmail2 Version: 2.0.89 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 2.0.89 OS:Linux If there's a thread containing more than one message, and some of them are unread, marking the whole thread as ignored doesn't make the unread messages read like it did in KMail 1. Now the unread messsages in the ignored thread are listed in the unread column in the folder list and in the message list even when the filter is set to Unread. If I select the messages in the message list after marking the thread as ignored seems to correctly mark them as read, but as soon as the folder is synced again (which happens the next time mail is checked) they're again marked as unread. The same happens using the Mark all mail as read or Mark thread as read menu entries Reproducible: Always OS: Linux (i686) release 2.6.36-gentoo Compiler: i686-pc-linux-gnu-gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 255969] New: KMail crashed on first run
https://bugs.kde.org/show_bug.cgi?id=255969 Summary: KMail crashed on first run Product: kmail Version: 1.13.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s.g...@softime.it Application: kmail (1.13.5) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-23-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: Just powered up the pc and tried to open Kmail. It happens everytime I open kmail. To run it I must press close and restart than it starts The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:727 #7 KIO::Slave::protocol (this=0x0) at ../../kio/kio/slave.cpp:181 #8 0x7fe030b9a8a9 in KIO::SchedulerPrivate::assignJobToSlave (this=0x132ee70, slave=0x0, job=0x132db90) at ../../kio/kio/scheduler.cpp:1205 #9 0x7fe0362acc0a in KMail::SearchJob::searchCompleteFolder (this=0x1408ab0) at ../../kmail/searchjob.cpp:95 #10 0x7fe0360cf168 in KMFolderImap::search (this=0x13075a0, pattern=0x1248590) at ../../kmail/kmfolderimap.cpp:2408 #11 0x7fe03621378d in KMSearch::slotProcessNextBatch (this=0x12c20d0) at ../../kmail/kmfoldersearch.cpp:272 #12 0x7fe0362138e0 in KMSearch::qt_metacall (this=0x12c20d0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff780b4e50) at ./kmfoldersearch.moc:85 #13 0x7fe034a5ab27 in QMetaObject::activate (sender=0x1337c90, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3280 #14 0x7fe034a548f9 in QObject::event (this=0x1337c90, e=0x0) at kernel/qobject.cpp:1183 #15 0x7fe034f2dfdc in QApplicationPrivate::notify_helper (this=0xfaf5d0, receiver=0x1337c90, e=0x7fff780b55a0) at kernel/qapplication.cpp:4396 #16 0x7fe034f33aed in QApplication::notify (this=0x7fff780b5a10, receiver=0x1337c90, e=0x7fff780b55a0) at kernel/qapplication.cpp:4277 #17 0x7fe0370d6156 in KApplication::notify (this=0x7fff780b5a10, receiver=0x1337c90, event=0x7fff780b55a0) at ../../kdeui/kernel/kapplication.cpp:310 #18 0x7fe034a42cdc in QCoreApplication::notifyInternal (this=0x7fff780b5a10, receiver=0x1337c90, event=0x7fff780b55a0) at kernel/qcoreapplication.cpp:732 #19 0x7fe034a726f2 in sendEvent (this=0xfb2ef0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #20 QTimerInfoList::activateTimers (this=0xfb2ef0) at kernel/qeventdispatcher_unix.cpp:602 #21 0x7fe034a6f4a4 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #22 0x7fe02b1cc342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x7fe02b1d02a8 in ?? () from /lib/libglib-2.0.so.0 #24 0x7fe02b1d045c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x7fe034a6f193 in QEventDispatcherGlib::processEvents (this=0xf6d8a0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415 #26 0x7fe034fe0a4e in QGuiEventDispatcherGlib::processEvents (this=0x7fff780b4ae0, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #27 0x7fe034a41a02 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #28 0x7fe034a41dec in QEventLoop::exec (this=0x7fff780b5840, flags=) at kernel/qeventloop.cpp:201 #29 0x7fe034a45ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #30 0x00403212 in main (argc=value optimized out, argv=value optimized out) at ../../kmail/main.cpp:156 This bug may be a duplicate of or related to bug 234367. Possible duplicates by query: bug 255400, bug 252023, bug 246617, bug 245452, bug 242570. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 252830] New: Email address is not well-formed in the message list
https://bugs.kde.org/show_bug.cgi?id=252830 Summary: Email address is not well-formed in the message list Product: kmail Version: 1.13.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: message list AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.bartale...@gmail.com Version: 1.13.5 (using KDE 4.5.1) OS:Linux Normally kmail/kontact shows a short sender address in the message list (e.g. John Doe) If there are many JD's mailing, you cannot distinguish them unless you check tooltips or open every email Discussed here: http://forum.kde.org/viewtopic.php?f=20t=90578p=171933#p171933 It would be better to use a different style, like other email clients do (e.g. John Doe john@example.com) Reproducible: Always -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 243826] New: KMail2 does not complete the initial synchronization of a disconnected imap account
https://bugs.kde.org/show_bug.cgi?id=243826 Summary: KMail2 does not complete the initial synchronization of a disconnected imap account Product: KMail 2 Version: 2.0 beta1 Platform: Archlinux Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stava...@unina.it Version: 2.0 beta1 (using Devel) OS:Linux I have around 20 folders in my emai account, where the Inbox folder has ~25k emails (occupying ~6GB) while the other folders contain less messages (100 on average). I did not use the migrator, as I started with a newly created user. I also disabled nepomuk in the system settings. Using the wizard that appears on the first launch of kmail, I tried to create a disconnected imap account (by checking download messages for offline use). The akonadi imap resource started synchronizing a folder with 400 messages (occupying 45MB) but never completed the synchronization. I tried three times with no success (every time deleting .kde4, .local, .config). Suddenly, the akonadi imap resource became idle and since then there was no progress. Clicking on such folder to view the message list does not show any message in the folder, despite the .local/share/akonadi/db_data folder had grown up to 4-5 GB. After relaunching kmail, I got an error message saying that akonadi was unable to start (with many errors in the log) and kmail closed. Reproducible: Always Steps to Reproduce: Start with a fresh kde account, launch kmail and try to create a disconnected imap account. Actual Results: The creation of the disconnected imap account fails (it seems it will never end) Expected Results: The creation of the disconnected imap account terminates successfully -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 243829] New: KMail2 takes all the cpu and too much time to process and group messages in an imap folder
https://bugs.kde.org/show_bug.cgi?id=243829 Summary: KMail2 takes all the cpu and too much time to process and group messages in an imap folder Product: KMail 2 Version: 2.0 beta1 Platform: Archlinux Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stava...@unina.it Version: 2.0 beta1 (using Devel) OS:Linux I have around 20 folders in my emai account, where the Inbox folder has ~25k emails (occupying ~6GB) while the other folders contain less messages (100 on average). I did not use the migrator, as I started with a newly created user. I also disabled nepomuk in the system settings. After launching kmail, I tried (by using the wizard) to create an online imap account (thus by not checking download messages for offline use). The synchronization was successful and now I can see all the emails in my folders. However, there are two annoying issues: - processing and grouping emails is very slow and takes all my cpu. For instance, processing and grouping threads for my inbox takes around 10 seconds, while with kmail 4.4 (and disconnected imap account) took ~1 second. - deleting messages in kmail does not delete emails from the imap server. Indeed, after some time, deleted messages re-appear in my folders. Reproducible: Always Steps to Reproduce: Create an online imap account and use kmail2 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241404] New: Kmail crashes clicking on cancel while downloading the text of the message after selecting reply to all
https://bugs.kde.org/show_bug.cgi?id=241404 Summary: Kmail crashes clicking on cancel while downloading the text of the message after selecting reply to all Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: guand...@gmail.com Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic-pae i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Kmail crashes clicking on cancel while downloading the text of the message after selecting reply to all. It seems that download hags for some unknown reason and clicking on cancels triggers the crash. I do not know if the same apply to a simple reply (not to all). The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb379d990 (LWP 4044))] Thread 2 (Thread 0xaca5ab70 (LWP 4071)): #0 0xb435be16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1 #1 0xb6e7c6fb in ?? () from /usr/lib/libQtCore.so.4 #2 0xb6e81825 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb6e8186a in ?? () from /usr/lib/libQtCore.so.4 #4 0xb6e7f818 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb6e7f8a5 in ?? () from /usr/lib/libQtCore.so.4 #6 0xb42ccaca in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0xb42ccee9 in ?? () from /lib/libglib-2.0.so.0 #8 0xb42cd4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0xb6e7f60f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #10 0xb6e52059 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #11 0xb6e524aa in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #12 0xb6d4e5a8 in QThread::exec() () from /usr/lib/libQtCore.so.4 #13 0xb6e31c1b in ?? () from /usr/lib/libQtCore.so.4 #14 0xb6d5132e in ?? () from /usr/lib/libQtCore.so.4 #15 0xb45ba96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #16 0xb60cfa4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb379d990 (LWP 4044)): [KCrash Handler] #6 0xb004d946 in KMCommand::slotTransferCancelled() () from /usr/lib/libkmailprivate.so.4 #7 0xb00587c3 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #8 0xb00591f2 in KMReplyToAllCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #9 0xb6e58c9a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #10 0xb6e673d5 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #11 0xb7303d67 in KDialog::cancelClicked() () from /usr/lib/libkdeui.so.5 #12 0xb7306348 in KDialog::slotButtonClicked(int) () from /usr/lib/libkdeui.so.5 #13 0xb7308559 in KDialog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5 #14 0xb732a46a in KProgressDialog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5 #15 0xb6e58c9a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #16 0xb6e673d5 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb6e6cb13 in QSignalMapper::mapped(int) () from /usr/lib/libQtCore.so.4 #18 0xb6e6dd8d in QSignalMapper::map(QObject*) () from /usr/lib/libQtCore.so.4 #19 0xb6e6df6e in QSignalMapper::map() () from /usr/lib/libQtCore.so.4 #20 0xb6e6e03b in QSignalMapper::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #21 0xb6e58c9a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb6e673d5 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #23 0xb6ace479 in QAbstractButton::clicked(bool) () from /usr/lib/libQtGui.so.4 #24 0xb67adea9 in ?? () from /usr/lib/libQtGui.so.4 #25 0xb67aecf4 in ?? () from /usr/lib/libQtGui.so.4 #26 0xb67aefae in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #27 0xb64017f8 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #28 0xb67add4e in QAbstractButton::event(QEvent*) () from /usr/lib/libQtGui.so.4 #29 0xb68581f2 in QPushButton::event(QEvent*) () from /usr/lib/libQtGui.so.4 #30 0xb63a34dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #31 0xb63aa9f7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #32 0xb73a4f2a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #33 0xb6e53a3b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from
[Bug 169702] Switching between multiple identities does not update signature when using Output of Command
https://bugs.kde.org/show_bug.cgi?id=169702 Stefano pietranera+kdeb...@gmail.com changed: What|Removed |Added CC||pietranera+kdeb...@gmail.co ||m --- Comment #6 from Stefano pietranera+kdebugs gmail com 2010-02-18 18:46:37 --- Hi, I am using Debian testing/unstable (Squeeze/Sid) with KDE 4.3.4 and KMail 1.12.4. I am using three (3) identities, two of them have a file as signature and the third one - that is *not* the default one - has the output of a script (basically it is fortune). When I start a new email with the default identity, the right signature (from file) appears, but when I switch to the identity whose signature is the command output and switch back to one of the other two identities there is no mean to obtain the right signatures. It seems to me that the script execution breaks somehow the signature event. I cannot say if this is a regression since I started to use this feature with KMail 1.12.4. Also, I believe that bugs 211492 and 226045 are a copy of this one. Thank you. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169702] Switching between multiple identities does not update signature when using Output of Command
https://bugs.kde.org/show_bug.cgi?id=169702 Stefano pietranera+kdeb...@gmail.com changed: What|Removed |Added CC|pietranera+kdeb...@gmail.co | |m | -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593 Stefano Crocco stefano.cro...@alice.it changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #3 from Stefano Crocco stefano crocco alice it 2009-07-17 17:13:19 --- The crash has disappeared some time ago. Sorry for not closing this bug sooner. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 189696] Kmail doesn't synchronize marks of read messages with Imap and labels (gmail)
https://bugs.kde.org/show_bug.cgi?id=189696 --- Comment #1 from Stefano Ferri ferriste gmail com 2009-04-20 10:35:24 --- I forgot to say that read messages in the subfolder are automatically marked as read in the general inbox only after the next imap syncronization, but not on the fly if I open the inbox with a mouse click. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 189696] New: Kmail doesn't synchronize marks of read messages with Imap and labels (gmail)
https://bugs.kde.org/show_bug.cgi?id=189696 Summary: Kmail doesn't synchronize marks of read messages with Imap and labels (gmail) Product: kmail Version: 1.11.2 Platform: Slackware Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ferri...@gmail.com Version: 1.11.2 (using KDE 4.2.2) OS:Linux Installed from:Slackware Packages I use gmail with Imap, and I've created a set of labels to manage various kind of e-mails that I'm receiving. In example, I've set up a kde label to organize e-mails coming from a kde mailing list. Gmail can shows these labels as separate folders. Kmail, rightly, shows a folder for each label, i.e. one called kde in the folderlist. When a new e-mail arrives, the unread emails count is showed both in the general Inbox folder and in the kde folder. Let us suppose I've received a new e-mail: now I read it opening the general inbox, and then, if I open the kde folder, I can see it marked as read. But the inverse path doesn't work: if I read this email in the kde folder for the first time, when I open the inbox, I see it as unread. This is a problem of kmail, because I've checked through the webmail that the message is correctly marked as read. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] New: Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593 Summary: Pressing ESC while fetching mail causes a crash Product: kmail Version: 1.11.90 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 1.11.90 (using 4.2.67 (KDE 4.2.67 (KDE 4.3 = 20090318)), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.28-gentoo-r3 While fetching message, if I press Esc to stop the operation, KMail crashes. Using the button near the progress bar to do the same, instead, works. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593
--- Comment #1 from Stefano Crocco stefano crocco alice it 2009-03-19
13:11:14 ---
Here's the backtrace for the crash:
Application: KMail (kmail), signal SIGSEGV
Thread 1 (Thread 0xb44b2700 (LWP 2757)):
[KCrash Handler]
#6 0xb72aafab in KPIM::ProgressItem::cancel (this=0x2f86c381) at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim/libkdepim/progressmanager.cpp:83
#7 0xb72ab360 in KPIM::ProgressManager::slotAbortAll (this=0x868bb90) at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim/libkdepim/progressmanager.cpp:240
#8 0xb72ab45e in KPIM::ProgressManager::qt_metacall (this=0x868bb90,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf81297c)
at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim_build/libkdepim/progressmanager.moc:219
#9 0xb65e49c1 in QMetaObject::activate (sender=0x868b7a8,
from_signal_index=value optimized out, to_signal_index=6, argv=0xbf81297c) at
kernel/qobject.cpp:3057
#10 0xb65e4cd0 in QMetaObject::activate (sender=0x868b7a8, m=0xb635c208,
from_local_signal_index=1, to_local_signal_index=2, argv=0xbf81297c) at
kernel/qobject.cpp:3154
#11 0xb5cd7393 in QAction::triggered (this=0x868b7a8, _t1=false) at
.moc/release-shared/moc_qaction.cpp:236
#12 0xb5cd8492 in QAction::activate (this=0x868b7a8, event=QAction::Trigger) at
kernel/qaction.cpp:1160
#13 0xb5cda533 in QAction::event (this=0x868b7a8, e=0xbf812d84) at
kernel/qaction.cpp:1079
#14 0xb7d7cb9d in KAction::event (this=0x868b7a8, event=0xbf812d84) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/actions/kaction.cpp:88
#15 0xb5cdc4db in QApplicationPrivate::notify_helper (this=0x8077900,
receiver=0x868b7a8, e=0xbf812d84) at kernel/qapplication.cpp:4084
#16 0xb5ce3822 in QApplication::notify (this=0xbf813bf8, receiver=0x868b7a8,
e=0xbf812d84) at kernel/qapplication.cpp:3631
#17 0xb7e55d55 in KApplication::notify (this=0xbf813bf8, receiver=0x868b7a8,
event=0xbf812d84) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:307
#18 0xb65d35c2 in QCoreApplication::notifyInternal (this=0xbf813bf8,
receiver=0x868b7a8, event=0xbf812d84) at kernel/qcoreapplication.cpp:598
#19 0xb5d0cc7f in QShortcutMap::dispatchEvent (this=0x80779a0, e=0xbf8130fc) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 0xb5d0e75e in QShortcutMap::tryShortcutEvent (this=0x80779a0, o=0x883ce48,
e=0xbf8130fc) at kernel/qshortcutmap.cpp:369
#21 0xb5ce4b3e in QApplication::notify (this=0xbf813bf8, receiver=0x883ce48,
e=0xbf8130fc) at kernel/qapplication.cpp:3673
#22 0xb7e55d55 in KApplication::notify (this=0xbf813bf8, receiver=0x883ce48,
event=0xbf8130fc) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:307
#23 0xb65d35c2 in QCoreApplication::notifyInternal (this=0xbf813bf8,
receiver=0x883ce48, event=0xbf8130fc) at kernel/qcoreapplication.cpp:598
#24 0xb5cdd807 in qt_sendSpontaneousEvent (receiver=0x883ce48, event=0x868bb90)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#25 0xb5d5f6fd in QKeyMapper::sendKeyEvent (keyWidget=0x883ce48, grab=false,
type=QEvent::KeyPress, code=16777216, modifiers={i = -1082051652},
te...@0xbf8133e8, autorepeat=value optimized out,
count=1, nativeScanCode=9, nativeVirtualKey=65307, nativeModifiers=16) at
kernel/qkeymapper_x11.cpp:1675
#26 0xb5d6145e in QKeyMapperPrivate::translateKeyEvent (this=0x80e71d8,
keyWidget=0x883ce48, event=0xbf8138ac, grab=129) at
kernel/qkeymapper_x11.cpp:1645
#27 0xb5d3da64 in QApplication::x11ProcessEvent (this=0xbf813bf8,
event=0xbf8138ac) at kernel/qapplication_x11.cpp:3436
#28 0xb5d62b50 in x11EventSourceDispatch (s=0x807a308, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0xb4aef3b5 in IA__g_main_context_dispatch (context=0x8079890) at
gmain.c:2144
#30 0xb4af2667 in g_main_context_iterate (context=0x8079890, block=1,
dispatch=1, self=0x80771d0) at gmain.c:2778
#31 0xb4af2808 in IA__g_main_context_iteration (context=0x8079890, may_block=1)
at gmain.c:2841
#32 0xb65f83f4 in QEventDispatcherGlib::processEvents (this=0x804fc18, flags={i
= -1082049944}) at kernel/qeventdispatcher_glib.cpp:323
#33 0xb5d623cb in QGuiEventDispatcherGlib::processEvents (this=0x804fc18,
flags={i = -1082049896}) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb65d2000 in QEventLoop::processEvents (this=0xbf813b00, flags={i =
-1082049832}) at kernel/qeventloop.cpp:149
#35 0xb65d21a6 in QEventLoop::exec (this=0xbf813b00, flags={i = -1082049784})
at kernel/qeventloop.cpp:196
#36 0xb65d406e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#37 0xb5cdc387 in QApplication::exec () at kernel/qapplication.cpp:3553
#38 0x0804a9b7 in main (argc=) at
/var/tmp/paludis/kde-base-kmail-scm/work/kmail/kmail/main.cpp:146
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug
[Bug 172362] New: external editor program opened needlessly
http://bugs.kde.org/show_bug.cgi?id=172362 Summary: external editor program opened needlessly Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using Devel) Installed from:Compiled sources I think this is the same bug as bug 48841 but, since that was for another version of KMail, I decided to create a new one. Sorry if I should have done otherwise. Using an external editor in the composer, if I press keys like Ctrl, Shift or Alt (alone), the external editor is launched, even if it shouldn't. I noticed it when I pressed Ctrl+Enter to send the mail and got the The external editor is still running. message box, but it happens for all keys (of course, the focus should be in the message widget, not in the From, To, Subject or other widgets). -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171268] New: disabling word wrapping in composer window only for some lines
http://bugs.kde.org/show_bug.cgi?id=171268 Summary: disabling word wrapping in composer window only for some lines Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using Devel) Installed from:Compiled sources It would be nice to have the ability to turn off word wrapping for only some lines in the composer window. This feature would be very useful, for example, when sending e-mails containing some kind of source code: if word wrapping is on, then long lines of code will be split in two lines, maybe producing broken code. Turning off word wrapping for the whole e-mail solves this problem but forces the user to manually insert line breaks, if he wants to avoid long lines in the parts of the message which aren't source code. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
