[ktnef] [Bug 473691] KTnef 23.04.1 can not open winmail.dat, but Thunderbird is able to convert into text/plain
https://bugs.kde.org/show_bug.cgi?id=473691 --- Comment #1 from Elmar Stellnberger (AT/K) --- Neither would jtnef-2.1.0 from freeutils.net/source/jtnef/ do the trick: x=*.jar; LANG=C echo java -cp "${x// /:}" net.freeutils.tnef.TNEF ./winmail.dat processing TNEF file ./winmail.dat java.io.IOException: Invalid attribute level: 13 at net.freeutils.tnef.TNEFInputStream.readAttr(TNEFInputStream.java:155) at net.freeutils.tnef.Message.read(Message.java:68) at net.freeutils.tnef.Message.(Message.java:56) at net.freeutils.tnef.TNEF.extractContent(TNEF.java:49) at net.freeutils.tnef.TNEF.main(TNEF.java:134) Operation aborted. -- You are receiving this mail because: You are the assignee for the bug.
[ktnef] [Bug 473691] New: KTnef 23.04.1 can not open winmail.dat, but Thunderbird is able to convert into text/plain
https://bugs.kde.org/show_bug.cgi?id=473691 Bug ID: 473691 Summary: KTnef 23.04.1 can not open winmail.dat, but Thunderbird is able to convert into text/plain Classification: Applications Product: ktnef Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: estel...@elstel.org Target Milestone: --- used: ktnef-23.04.1-2.mga9, arch i686, Mageia 9 used: thunderbird-102.12.0-1.mga9, arch i686 used: tnef 1.4.18, commit 1810f3a 45459a2, arch i686, self-compiled kernel: 6.3.9-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Wed Jun 21 16:54:49 UTC 2023 i686 ktnef displays a GUI alert/message box that says "Opening file winmail.dat not possible" (original text: "Das Öffnen der Datei „winmail.dat“ ist nicht möglich."). KTnef will run and hold its main window open, but no file or content appear to be displayed, although it says "winmail.dat - KTnef" in the title bar. It is possible to make a "save message text to file" which results in an empty file, zero bytes long. Viewing as ritch text says "no rtf in this document" and opening ktnef without any command line parameter afterwards (i.e. without winmail.dat) the file that was opened last (or not) isn´t viewed under actual documents (which appears to be a list similar to last opened in libreoffice-writer). If you inspect winmail.dat with 'od' or 'vim -MR/:set wrap on', you don´t see more than a few SMTP-headers. If you attach the winmail.dat within a Thunderbird Email directly, it will be decoded into text/plain. Saving this text/plain as .eml and opening it with Thunderbird again, you get an empty Email with same or similar headers as the envelope had. The winmail.dat itself was an attachement inside an attached .eml (as you will often encounter; however in Σ a 3-time nest/wrap excluding the top-Email) and thus Thunderbird´s only offer about it was saving to disk (or on my other machine opening it with ktnef, which didn´t do the trick either). Here you can find the attachements: https://upload.elstel.info/corr/DKB-edr/ (ask-me42copy2this-report) Here is what the tnef command line program does (see at https://github.com/verdammelt/tnef/issues/47): > tnef --ignore-cruft -v [--list] -f winmail.dat WARNING: garbage at end of file (ignored) > no content extracted, no files listed -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 385841] New: Press DEL gives error message
https://bugs.kde.org/show_bug.cgi?id=385841 Bug ID: 385841 Summary: Press DEL gives error message Product: kontact Version: 5.6.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: rob...@iafrica.com Target Milestone: --- When I press DEL to move message Message list to waste bin, I get message to say that it is ambiguous and that I must resolve with "settings short cuts". There are not two allocations for DEL. So where is the problem? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 293963] Akonadi config reports "Invalid Password" whenever trying to add Google Calendar or Contacts resource
https://bugs.kde.org/show_bug.cgi?id=293963 Elmar changed: What|Removed |Added CC||elmar.rob...@gmail.com --- Comment #1 from Elmar --- I added a gmail calendar to my Kontact calendar. Everything seemed to work fine. But Kontact does not sync, and I get a message as well as an instruction to log a bug. I have removed the gmail calendar because the endless notifications are irritating - cannot find a way of switching them off. -- 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 306382] Changed .ics. Since then akonadi seems to be in a backup loop
https://bugs.kde.org/show_bug.cgi?id=306382 Elmar changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Elmar --- I deleted the calendars and that stopped this problem. -- 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 264861] Google calendar and contacts don't work
https://bugs.kde.org/show_bug.cgi?id=264861 Elmar changed: What|Removed |Added CC||elmar.rob...@gmail.com --- Comment #48 from Elmar --- Any chance this is going to be resolved soon? I switched from Thunderbird when I switched from Unity to KDE. What is odd, is that it seemed like I did see my Google calendar for a couple of days before it disappeared again. Maybe I was seeing things. I like the configurability of Kontact, but my business calender is sitting in Google, so It is a pain if I can only see it on my phone. -- 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 306382] New: Changed .ics. Since then akonadi seems to be in a backup loop
https://bugs.kde.org/show_bug.cgi?id=306382 Bug ID: 306382 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Changed .ics. Since then akonadi seems to be in a backup loop Classification: Unclassified OS: Linux Reporter: elmar.rob...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: ICal file resource Product: Akonadi I changed a number of calendars two days ago. Since then I get a notification like "...ics file ... as changed on disk. As a precaution, a backup of its previous contents has been created at ... " This has been running from the time that I start korganiser until I shut down (and in fact, my machine won't shut down, so I have to do a hard switch off.) I do not know how to disable this / stop it - I do not need the backup since the data was imported in the first place. I switched from ubuntu 12.04 to kubuntu 12.04 about a month ago because I could not stand the way Unity works. I tried kubuntu a number of years ago and liked korganiser, so I also moved from thunderbird to korganiser. -- 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 305924] New: KDE Kontact crash
https://bugs.kde.org/show_bug.cgi?id=305924 Bug ID: 305924 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KDE Kontact crash Classification: Unclassified OS: Linux Reporter: elmar.rob...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-29-generic-pae i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: moving a large folder to another (imported from Thunderbird then moved to Local Folder The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb2165980 (LWP 7414))] Thread 4 (Thread 0xafae1b40 (LWP 7415)): #0 0xb7741424 in __kernel_vsyscall () #1 0xb397096b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb60783dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb57f6263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb57f637f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb396cd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0xb606aace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xaf1c0b40 (LWP 7416)): #0 0xb7741424 in __kernel_vsyscall () #1 0xb605c380 in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0xb38a7a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb389a0ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb389a201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb63ba8e7 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb638650d in QEventLoop::processEvents (this=0xaf1c0270, flags=...) at kernel/qeventloop.cpp:149 #7 0xb63867a9 in QEventLoop::exec (this=0xaf1c0270, flags=...) at kernel/qeventloop.cpp:204 #8 0xb626f94c in QThread::exec (this=0x8e13210) at thread/qthread.cpp:501 #9 0xb626fa3b in QThread::run (this=0x8e13210) at thread/qthread.cpp:568 #10 0xb6272de0 in QThreadPrivate::start (arg=0x8e13210) at thread/qthread_unix.cpp:298 #11 0xb396cd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0xb606aace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xaba02b40 (LWP 7454)): #0 0xb36bedcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb62d1315 in do_gettime (frac=0xaba01fb0, sec=0xaba01fa8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb63bb226 in QTimerInfoList::updateCurrentTime (this=0xab102074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb63bb57a in QTimerInfoList::timerWait (this=0xab102074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb63b9e23 in timerSourcePrepareHelper (src=, timeout=0xaba020bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb63b9ebd in timerSourcePrepare (source=0xab102040, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb3899872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb3899faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb389a201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb63ba8e7 in QEventDispatcherGlib::processEvents (this=0xab100468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0xb638650d in QEventLoop::processEvents (this=0xaba02240, flags=...) at kernel/qeventloop.cpp:149 #12 0xb63867a9 in QEventLoop::exec (this=0xaba02240, flags=...) at kernel/qeventloop.cpp:204 #13 0xb626f94c in QThread::exec (this=0x992eac8) at thread/qthread.cpp:501 #14 0xb6363b5d in QInotifyFileSystemWatcherEngine::run (this=0x992eac8) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb6272de0 in QThreadPrivate::start (arg=0x992eac8) at thread/qthread_unix.cpp:298 #16 0xb396cd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0xb606aace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb2165980 (LWP 7414)): [KCrash Handler] #7 size (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:137 #8 QSortFilterProxyModelPrivate::proxy_to_source (this=0x9321040, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:370 #9 0xb6f3a343 in QSortFilterProxyModel::mapToSource (this=0x91c4010, proxyIndex=...) at itemviews/qsortfilterproxymodel.cpp:2502 #10 0xb6f3b62b in QSortFilterProxyModelPrivate::store_persistent_indexes (this=0x1) at itemviews/qsortfilterproxymodel.cpp:996 #11 0xb6f3c4c0 in QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged (this=0x9321040) at itemviews/qsortfilterproxymodel.cpp:1244 #12 0xb639e6b1 in QMetaObject::activate (sender=0x91
[Bug 258171] Annoyed by 'Nepomuk Indexing Disabled - Akonadi Agent' message
https://bugs.kde.org/show_bug.cgi?id=258171 --- Comment #66 from Elmar Baumann 2011-11-22 22:09:25 --- I activated the desktop search to get rid that message and defined an empty folder for indexing. Then I got 5 and more notifications, more than before, messages like "redland can't be found" etc. Always after starting KDE I'm distracted through (loud) notification sounds and messages. This can lead to ignore important messages in future. It can lead to say Goodbye to KDE to avoid "dirty hacks" like let rpm uninstalling Akonadi ignoring dependencies. These messages are "unpolite" and are ignoring some points like (ignored by most programs): * Don't tell only that an error occurred, tell how it can be fixed * Better: Don't let me make much afford to fix it, e.g. don't tell: Start abc and set there xyz, but present within the error message an option to display a dialog to set xyz * These error messagees are decoupled from their scope. If I don't use desktop search, that message is a bug. If e.g. KMail does not work correctly, KMail should display that message. Last but not least: The users using this bug reporting system are some of the most valuable persons whithin the software developing process. They spend much time to improve the software and having some knowledge: Most users don't know what a bug reporting system is, where to find it, how to use it or willed spent time to report bugs or how to do that in a useful way. And: Why should thousands spend much time to work around bugs and not one or a few devolopers to fix that bug. I know, bugfixing costs time, but in my opinion bug fixes should have top level priority and should be done before any other things like adding features. -- 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 258171] Annoyed by 'Nepomuk Indexing Disabled - Akonadi Agent' message
https://bugs.kde.org/show_bug.cgi?id=258171 --- Comment #64 from Elmar Baumann 2011-11-20 19:36:57 --- @Christophe: A bug report should remain if it's a bug, even if some reporters are not polite. That does speak against the reporters and not against the bug (it shows how angray these people are and should be an indicator for a developer to think about a fix, even if the "form" of the report is bad). I can't see a link like "this is a duplicate of bug xyz", so where is the other bug report for this bug? If it does not exist, I suggest, to reopen this bug, it's better not to have multiple bug id's for the same 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 258171] Annoyed by 'Nepomuk Indexing Disabled - Akonadi Agent' message
https://bugs.kde.org/show_bug.cgi?id=258171 Elmar Baumann changed: What|Removed |Added CC||e...@elmar-baumann.de --- Comment #61 from Elmar Baumann 2011-11-20 18:22:19 --- I'm surprised how the responsible persons are reacting to a bug that leads users at least to switch from the whole K desktop environment to another (and I'm considering that too). In my opinion it's even a bug in the notification system that I can't disable specialized messages. In other words, to disable the that annoying message, I have only the choice to do stupid workarounds (e.g. enabling nepomuk and let it index only one empty directory) or using another desktop. It's easy for the developers to say: That's "INVALID" in my opinion, but more than 60 comments and more than 300 votes shouldn't be ignored. It's also uncooperatively to other KDE developers who have done good work that will be ignored due switching to another desktop because the Akonadi developers are "too lazy" to program at least a short statement like that (I know, it will consume some time to implement that and it's more complex): if (displayError) { displayError(); } -- 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