Version: (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages Hi, when I start the "miniprogram" for new mail, it does not show the new emails. I also restarted it after starting Kontact. I would expcet that the widgets shows the same new Emails, like Kontact/kmail shows. Best Regards Rico
Created attachment 33255 [details] example kubuntu kde4.2 here is an example
How did you installed that widget on the desktop ? Thanks
Hi, I did a right click on the desktop "add mini program, chose the right one. That's it. Maybe it has also something to do with kwallet or kontact auto start in genral. After each start up I get a message that kontact is already started. The question in the popup is then open or close. When I press open I have two instances when I press close, no one. Could it be that kontact has issues when it uses Kawallet? Maybe it causes side effects on the widget. Best Regards Rico
I asked how did you added that widget because that is an unofficial widget, so you should had installed it from another Ubuntu package or manually compiled it. You should check the blue information icon "(i)" for that widget in the "Add Widget" dialog to know where to report bugs. I'm closing this report because that miniwidget is not supported here (as the KDE developers didn't wrote it) Thanks
thanks for your fast response. no there was no further installation from my side (if it would be the case; I would let you know) it is just Kubuntu 9.04 Are you sure that is not official?
Actually it seems to be an offical widget, one from plasma addons. From the screenshot it seems to be the one I see being called "Posteingang" in German, which comes from this .desktop file: plasma-applet-incomingmsg.desktop That file says that the author is Christian Weilbach <dunsens at web dot de>
Hi, I'm noit 100% surte whether it is an plasma issue. I think it is caused by the issue on start up. (see comment 3) When i press open after the popup (kontact is already started) and close then one window Kontact crashes: Anwendung: Kontact (kontact), Signal SIGABRT Thread 1 (Thread 0xb48a4700 (LWP 3642)): [KCrash Handler] #6 0xb8036430 in __kernel_vsyscall () #7 0xb58e06d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb58e2098 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb58d95ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #10 0xb101d13c in KMKernel::self () at /build/buildd/kdepim-4.2.2/kmail/kmkernel.cpp:2118 #11 0xb10f538c in kmcrashHandler (sigId=6) at /build/buildd/kdepim-4.2.2/kmail/kmstartup.cpp:69 #12 0xb6dee17a in KCrash::defaultCrashHandler (sig=6) at /build/buildd/kde4libs-4.2.2/kdeui/util/kcrash.cpp:224 #13 <signal handler called> #14 0xb8036430 in __kernel_vsyscall () #15 0xb58e06d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #16 0xb58e2098 in abort () from /lib/tls/i686/cmov/libc.so.6 #17 0xb58d95ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #18 0xb101d13c in KMKernel::self () at /build/buildd/kdepim-4.2.2/kmail/kmkernel.cpp:2118 #19 0xb1107df7 in KMMainWidget::initializeFilterActions (this=0x9733968) at /build/buildd/kdepim-4.2.2/kmail/kmmainwidget.cpp:4761 #20 0xb157a9d6 in KMailPart::guiActivateEvent (this=0x969e4b8, e=0xbfc53908) at /build/buildd/kdepim-4.2.2/kmail/kmail_part.cpp:181 #21 0xb71b2dc4 in KParts::Part::customEvent (this=0x969e4b8, ev=0xbfc53908) at /build/buildd/kde4libs-4.2.2/kparts/part.cpp:321 #22 0xb5c983ff in QObject::event (this=0x969e4b8, e=0xbfc53908) at kernel/qobject.cpp:1149 #23 0xb6158f2c in QApplicationPrivate::notify_helper (this=0x9368ee0, receiver=0x969e4b8, e=0xbfc53908) at kernel/qapplication.cpp:4084 #24 0xb616122e in QApplication::notify (this=0xbfc539d8, receiver=0x969e4b8, e=0xbfc53908) at kernel/qapplication.cpp:3631 #25 0xb6d7d94d in KApplication::notify (this=0xbfc539d8, receiver=0x969e4b8, event=0xbfc53908) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307 #26 0xb5c87a3b in QCoreApplication::notifyInternal (this=0xbfc539d8, receiver=0x969e4b8, event=0xbfc53908) at kernel/qcoreapplication.cpp:602 #27 0xb71beaba in KParts::MainWindow::createGUI (this=0x94576a0, part=0x0) at /usr/include/qt4/QtCore/qcoreapplication.h:213 #28 0xb78f37d5 in ~MainWindow (this=0x94576a0) at /build/buildd/kdepim-4.2.2/kontact/src/mainwindow.cpp:256 #29 0x0804c0ae in main (argc=3, argv=0xbfc53cd4) at /usr/include/qt4/QtCore/qalgorithms.h:350
@Rico Zienke: your crash is a unrelated to this bug report. Please file a new report against Kontact using that backtrace. Do not forget to mention your KDE4 version and your Linux distribution. Thanks
Bug still present in KDE 4.4 beta 2, Qt 4.6.0. I don't know if it has anything to do with using KWallet or Kontact/Kmail autostart. I can reproduce the bug when there is unread mail in the mail account by doing: 1. add the widget 2. start kmail (the widget doesn't still notice kmail running) 3. restart plasma 4. now the widget notices it is running ("No new mail.", even if KMail has some unread messages) 5. check for mail (without kmail using kwallet or trying to open any wallet at all) 6. KMail says there are unread messages, the widget still shows "No new mail."
hmm, as i see the actual use case for this plasmoid is being misunderstood very often. i have simply written it for one purpose: to show me on my locked screen when new messaging data comes in, so i don't have to unlock my screensaver just to have a look for new instant messages or mails. the plasmoid is very basic and meant to be that way to not leak privacy information. it only reports mails which are new during the runtime of the applet, which is exactly what you want on a locked screen but makes no sense on the desktop. if you want better notifications about new mails you should ask the kmail devs to add notification support about new mails imo.
Then, this is not a bug (as the feature was not intended), but a wish. Changing. Regards
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham