[kmail2] [Bug 369245] KMail 5.3.1: Attachments are included as plain text in forwarded or replied mails
https://bugs.kde.org/show_bug.cgi?id=369245 Till Schäferchanged: What|Removed |Added Version|Git (master)|5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371544] New: Crash after closing a group of applications
https://bugs.kde.org/show_bug.cgi?id=371544 Bug ID: 371544 Summary: Crash after closing a group of applications Product: plasmashell Version: 5.8.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: till2.schae...@uni-dortmund.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.8.2) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.4.26-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I closed a group of okular entries by right clicking on the grouped entry in the task manager panel and selecting close. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1df3c1c7c0 (LWP 2438))] Thread 17 (Thread 0x7f1de06c0700 (LWP 2456)): #0 0x7f1dee5f03ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1df25f18f2 in poll (__timeout=-1, __nfds=1, __fds=0x7f1de06bfd00) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xb3e5b0, cond=cond@entry=0xb3e5f0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_conn.c:479 #3 0x7f1df25f36df in xcb_wait_for_event (c=0xb3e5b0) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_in.c:693 #4 0x7f1de2826e19 in QXcbEventReader::run (this=0xb4a5d0) at qxcbconnection.cpp:1337 #5 0x7f1deecad78c in QThreadPrivate::start (arg=0xb4a5d0) at thread/qthread_unix.cpp:344 #6 0x7f1dede01434 in start_thread (arg=0x7f1de06c0700) at pthread_create.c:334 #7 0x7f1dee5f950d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f1ddeaa8700 (LWP 2532)): #0 QMutex::lock (this=this@entry=0xb92300) at thread/qmutex.cpp:223 #1 0x7f1deee9d61b in QMutexLocker::QMutexLocker (m=0xb92300, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:137 #2 QThreadData::canWaitLocked (this=0xb922d0) at ../../include/QtCore/5.7.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #3 postEventSourcePrepare (s=0x7f1dd00012d0, timeout=timeout@entry=0x7f1ddeaa7c04) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7f1dea67c52d in g_main_context_prepare (context=context@entry=0x7f1dd990, priority=priority@entry=0x7f1ddeaa7c90) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3442 #5 0x7f1dea67cf18 in g_main_context_iterate (context=context@entry=0x7f1dd990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3820 #6 0x7f1dea67d0fc in g_main_context_iteration (context=0x7f1dd990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901 #7 0x7f1deee9d74c in QEventDispatcherGlib::processEvents (this=0x7f1dd8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #8 0x7f1deee50f1a in QEventLoop::exec (this=this@entry=0x7f1ddeaa7dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7f1deeca9204 in QThread::exec (this=this@entry=0x7f1df3dc1280 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #10 0x7f1df3d534b5 in QDBusConnectionManager::run (this=0x7f1df3dc1280 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #11 0x7f1deecad78c in QThreadPrivate::start (arg=0x7f1df3dc1280 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #12 0x7f1dede01434 in start_thread (arg=0x7f1ddeaa8700) at pthread_create.c:334 #13 0x7f1dee5f950d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f1ddd060700 (LWP 2575)): #0 g_main_context_prepare (context=context@entry=0x7f1dd4000990, priority=priority@entry=0x7f1ddd05fca0) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3507 #1 0x7f1dea67cf18 in g_main_context_iterate (context=context@entry=0x7f1dd4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3820 #2 0x7f1dea67d0fc in g_main_context_iteration (context=0x7f1dd4000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901 #3 0x7f1deee9d74c in QEventDispatcherGlib::processEvents (this=0x7f1dd40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f1deee50f1a in QEventLoop::exec (this=this@entry=0x7f1ddd05fde0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5
[kwin] [Bug 371323] Add GUI configuration option to disable/edit ModifierOnlyShortcuts
https://bugs.kde.org/show_bug.cgi?id=371323 Till Schäferchanged: What|Removed |Added Summary|Add configuration option to |Add GUI configuration |disable/edit|option to disable/edit |ModifierOnlyShortcuts |ModifierOnlyShortcuts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371323] Add configuration option to disable/edit ModifierOnlyShortcuts
https://bugs.kde.org/show_bug.cgi?id=371323 Till Schäferchanged: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #2 from Till Schäfer --- So why is this different from regular keys (from a user point of perspective, not the technically one)? Typically, KDE allows the configuration of shortcuts and it is nice to have them adjustable. The meta key is also destructive in games, when you accidentally hit the meta key and the whole game minimizes. -> i would like to keep this bug open as a wish... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371323] New: Add configuration option to disable/edit ModifierOnlyShortcuts
https://bugs.kde.org/show_bug.cgi?id=371323 Bug ID: 371323 Summary: Add configuration option to disable/edit ModifierOnlyShortcuts Product: kwin Version: 5.8.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: till2.schae...@uni-dortmund.de Starting with plasma 5.8, the kickoff menu is opening when pressing the meta button (only). This aligns with many other desktop environments and is therefore nice as a default. However, it should be configurable to enable or disable this feature as it is really annoying when working with many other meta+ shortcuts. For example, i have the habit to press the meta key in advance and then just cancel the meta+ shortcut, because i want to do something else. In this kickoff pops up and blocks my input from wherever i was working on. I need to press esc (meta only a second time is not working to close kickoff, opposed to regularly assigned shortcuts) to get my original focus back. -> Therefore: Please make this feature optional or let one configure the ModifierOnlyKeys such as regular shortcuts. The only workaround so far seems to use the workaround here: https://www.reddit.com/r/kde/comments/55udc1/how_do_i_stop_the_meta_key_from_opening_the/d8epzzj Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 346212] Kontact/KMail-5.3.1 ignores per contact settings about html and external resources synced over dav resource
https://bugs.kde.org/show_bug.cgi?id=346212 Till Schäferchanged: What|Removed |Added Version|unspecified |5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 --- Comment #13 from Till Schäfer--- *** Bug 370030 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370030] Digital Clock is too wide on smaller panels
https://bugs.kde.org/show_bug.cgi?id=370030 Till Schäferchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #4 from Till Schäfer --- sry for the spam *** This bug has been marked as a duplicate of bug 370156 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370030] Digital Clock is too wide on smaller panels
https://bugs.kde.org/show_bug.cgi?id=370030 Till Schäferchanged: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #3 from Till Schäfer --- up my fault .. .wrong direction -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 Till Schäferchanged: What|Removed |Added CC||bastian.beischer@rwth-aache ||n.de --- Comment #12 from Till Schäfer --- *** Bug 370030 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370030] Digital Clock is too wide on smaller panels
https://bugs.kde.org/show_bug.cgi?id=370030 Till Schäferchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||till2.schaefer@uni-dortmund ||.de --- Comment #2 from Till Schäfer --- *** This bug has been marked as a duplicate of bug 370156 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 Till Schäferchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 --- Comment #11 from Till Schäfer--- (In reply to Chris Holland from comment #9) > Found what caused the bug, it seems removing pixelSize: 1024 is causing the > jumpiness. > https://github.com/KDE/plasma-workspace/commit/ > 9016eaae22db317811f5fdae29bdeba594cf6310 i can confirm, that the reverse diff of D1974 fixes the problem here on top of plasma 5.8.0 on gentoo (qt 5.6.1, frameworks 2.26) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 --- Comment #10 from Till Schäfer--- Created attachment 101473 --> https://bugs.kde.org/attachment.cgi?id=101473=edit reverse diff of D1974 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #29 from Till Schäfer--- Interesting detail form Bug 367846: xapian-check .local/share/akonadi/search_db/emailContacts always crashes with xapian 1.4.x. However, for me, this check even crashes, when akonadi runs fine atop of Xapian 1.4.0 (an no search query folder exist) -> As Xapian 1.2.x seem to be working with akonadi -> Can someone with Xapian 1.2.x confirm that this crash does not occur? $ xapian-check emailContacts/ Cross-checking document lengths between the postlist and termlist tables would use more than 1GB of memory, so skipping that check docdata: blocksize=8K items=16458 firstunused=277 revision=913 levels=1 root=22 B-tree checked okay docdata table structure checked OK termlist: blocksize=8K items=16458 firstunused=349 revision=913 levels=1 root=194 B-tree checked okay xapian-check: Unknown exception -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Till Schäferchanged: What|Removed |Added CC||rodney.ba...@iinet.net.au --- Comment #28 from Till Schäfer --- *** Bug 367846 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Till Schäferchanged: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #15 from Till Schäfer --- *** This bug has been marked as a duplicate of bug 363741 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 --- Comment #2 from Till Schäfer--- Created attachment 101437 --> https://bugs.kde.org/attachment.cgi?id=101437=edit digital clock in plasma 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 --- Comment #1 from Till Schäfer--- Created attachment 101436 --> https://bugs.kde.org/attachment.cgi?id=101436=edit digital clock in plasma 5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] New: digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 Bug ID: 370156 Summary: digital clock font is tiny since plasma 5.8.0 Product: plasmashell Version: 5.8.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: till2.schae...@uni-dortmund.de the digital clock font size is significantly reduced since i have upgraded from plasma 5.7.5 to 5.8.0. Also the spacing seem unnaturally large. I have attached two screenshots form plasma 5.7.5 and 5.8.0 respectively. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 193337] multipage option doesn't work with pdf printer
https://bugs.kde.org/show_bug.cgi?id=193337 Till Schäferchanged: What|Removed |Added Version|unspecified |frameworks -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 342158] print multiple pages on one sheet into pdf not working
https://bugs.kde.org/show_bug.cgi?id=342158 Till Schäferchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Till Schäfer --- *** This bug has been marked as a duplicate of bug 193337 *** -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 193337] multipage option doesn't work with pdf printer
https://bugs.kde.org/show_bug.cgi?id=193337 Till Schäferchanged: What|Removed |Added CC||criss...@gmx.de --- Comment #24 from Till Schäfer --- *** Bug 342158 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 369421] New: Kde Menu Editor crash while clicking a folder
https://bugs.kde.org/show_bug.cgi?id=369421 Bug ID: 369421 Summary: Kde Menu Editor crash while clicking a folder Product: kmenuedit Version: 5.7.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: till2.schae...@uni-dortmund.de Application: kmenuedit (5.7.5) (Compiled from sources) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.6.4-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I have cut a custom folder inside the "Development" category. A message popped up, saying that i cant cut complete directories and that i can . After this I pastet the custom folter into itself and deleted the pasted folder afterwards. Finaly i copied a real entry and clicked the custom folder to paste it in there. While clicking on the custom folder the editor crashed. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffb123de840 (LWP 7400))] Thread 2 (Thread 0x7ffb0e733700 (LWP 7402)): #0 0x7ffb22fd63ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ffb1a3e9f2c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7ffb3020, timeout=-1, context=0x7ffb0990) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7ffb0990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7ffb1a3ea03c in g_main_context_iteration (context=0x7ffb0990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7ffb1fa5640c in QEventDispatcherGlib::processEvents (this=0x7ffb08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x7ffb1fa0812a in QEventLoop::exec (this=this@entry=0x7ffb0e732d50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7ffb1f85f674 in QThread::exec (this=this@entry=0x7ffb2367f240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #7 0x7ffb23612235 in QDBusConnectionManager::run (this=0x7ffb2367f240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #8 0x7ffb1f863e2c in QThreadPrivate::start (arg=0x7ffb2367f240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #9 0x7ffb1c109434 in start_thread (arg=0x7ffb0e733700) at pthread_create.c:334 #10 0x7ffb22fdf50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ffb123de840 (LWP 7400)): [KCrash Handler] #6 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:238 #7 0x7ffb1f8e2869 in memcpy (__len=65534, __src=0x7ffb210e2b30, __dest=) at /usr/include/bits/string3.h:53 #8 QString::QString (this=0x7ffe05442f40, unicode=0x7ffb210e2b30, size=) at tools/qstring.cpp:1521 #9 0x7ffb1f8e7755 in QString::left (this=this@entry=0x140d108, n=) at tools/qstring.cpp:4304 #10 0x7ffb20472d4b in QWidgetLineControl::internalSetText (this=this@entry=0x11496d0, txt=..., pos=pos@entry=-1, edited=edited@entry=false) at widgets/qwidgetlinecontrol.cpp:741 #11 0x7ffb203ddbe2 in QWidgetLineControl::setText (txt=..., this=0x11496d0) at ../../include/QtWidgets/5.6.1/QtWidgets/private/../../../../../src/widgets/widgets/qwidgetlinecontrol_p.h:235 #12 QLineEdit::setText (this=, text=...) at widgets/qlineedit.cpp:316 #13 0x7ffb232ae169 in BasicTab::setFolderInfo (this=0x1258760, folderInfo=0x140d0f0) at /var/tmp/portage/kde-plasma/kmenuedit-5.7.5/work/kmenuedit-5.7.5/basictab.cpp:299 #14 0x7ffb232c74dc in BasicTab::qt_static_metacall (_o=, _c=, _id=, _a=) at /var/tmp/portage/kde-plasma/kmenuedit-5.7.5/work/kmenuedit-5.7.5_build/moc_basictab.cpp:128 #15 0x7ffb1fa30a9c in QMetaObject::activate (sender=0x1149160, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe05443160) at kernel/qobject.cpp:3730 #16 0x7ffb1fa31647 in QMetaObject::activate (sender=, m=m@entry=0x7ffb234d49c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe05443160) at kernel/qobject.cpp:3595 #17 0x7ffb232c6e5f in TreeView::entrySelected (this=, _t1=0x140d0f0) at /var/tmp/portage/kde-plasma/kmenuedit-5.7.5/work/kmenuedit-5.7.5_build/moc_treeview.cpp:233 #18 0x7ffb1fa31102 in QtPrivate::QSlotObjectBase::call (a=0x7ffe054432a0, r=0x1149160, this=0x12cf910) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=0x1149160,
[kmail2] [Bug 313667] Kmail2 5.3.1: sent e-mail missing in 'Sent' folder after restoring unsaved composer content
https://bugs.kde.org/show_bug.cgi?id=313667 Till Schäferchanged: What|Removed |Added Version|5.2.1 |5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Till Schäferchanged: What|Removed |Added Version|4.12.2 |5.3.1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #35 from Till Schäfer --- still valid for 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 335091] Akonadiconsole hangs when using the debugger for a longer time
https://bugs.kde.org/show_bug.cgi?id=335091 Till Schäferchanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Version|4.13|5.3.1 Resolution|WAITINGFORINFO |--- --- Comment #4 from Till Schäfer --- still valid for 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=335654 --- Comment #13 from Till Schäfer--- (In reply to Christophe Giboudeaux from comment #12) > Done. Next time, please open a new bug report instead of hijacking an > unrelated one. Although i was not directly addressed: thought this is a accumulative bug reports for all kinds of missing versions? Should we go back to assigned in this case? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäferchanged: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäferchanged: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #8 from Till Schäfer --- today i also observed the bug again. therefore, the new nvidia-driver does not fix the problem, but makes it less likely. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369247] Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 --- Comment #2 from Till Schäfer--- sure, this is the example where I observed it first: 1. goto Settings -> Configure KMail -> Composer -> "Reply and forward using HTML if present" and change the setting to enabeld (lets assume it was disabled and we have enabled it now / it also works vice versa) and press OK. 2. goto Settings -> Configure Kontact -> Mail -> Composer -> "Reply and forward using HTML if present". The setting is still disabled. I have observed, that this is one way only. I.e. you need to change the components setting first and check the kontact setting afterwards. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369247] New: Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized
https://bugs.kde.org/show_bug.cgi?id=369247 Bug ID: 369247 Summary: Kontact 5.3.1: settings between Kontact and components (e.g. KMail) are not synchronized Product: kontact Version: GIT (master) Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: till2.schae...@uni-dortmund.de When running Kontact, there are two setting dialogs: 1. Settings -> Configure Kontact 2. Settings -> Configure (e.g. KMail) (2) represents a subset of the options provided by (1). If one configures a setting in one dialog, the settings are not synced to the other dialog. E.g. when setting an option in (1), clicking OK, and then entering (2), the old configuration (configuration state before the changes made in (1)) is shown in (2). independent of the dialog (1 or 2): the last applied configuration is always the used one. I.e. the (1) does not dominate (2) or vice versa. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369245] New: KMail 5.3.1: Attachments are included as plain text in forwarded or replied mails
https://bugs.kde.org/show_bug.cgi?id=369245 Bug ID: 369245 Summary: KMail 5.3.1: Attachments are included as plain text in forwarded or replied mails Product: kmail2 Version: Git (master) Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: till2.schae...@uni-dortmund.de For some (not all) mails with (binary) attachments, the attachments are included as plain text in forwarded or replied mails. A necessary condition seems to be, that the mail composer is using plain text. If i reply an e-mail in html format, everything works as expected. The configuration option "Reply or forward using HTML if present" therefore is a workaround for this bug. Reproducible: Always Steps to Reproduce: 1. Reply to or forward an email with an attachment in plain text format Actual Results: The binary content is embedded in the E-Mail text Expected Results: forward: the attachment stays an attachment reply: the attachment is removed here is an example header of a mail, that triggers the bug: Return-Path: Received: from unimail.uni-dortmund.de ([unix socket]) by unimail (Cyrus 2.5.9-8-g5134a9a. 0) with LMTPA; Sun, 11 Sep 2016 20:01:51 +0200 X-Sieve: CMU Sieve 2.4 Received: from esa4.itmc.tu-dortmund.de (esa4.itmc.tu-dortmund.de [129.217.131.14]) by unimail.uni-dortmund.de (8.16.0.19/8.16.0.19) with ESMTPS id u8BI1pDr009825 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for; Sun, 11 Sep 2016 20:01:51 +0200 (CEST) IronPort-PHdr: =?us-ascii?q?9a23=3AdeRkehYbwerxYpmMF1jZqfD/LSx+4OfEezUN459i?= =?us-ascii?q?sYplN5qZpcS9bnLW6fgltlLVR4KTs6sC0LuP9f6/EjVbsN7B6ClEK80UEUddyI?= =?us-ascii?q?0/pE8JOIa9E0r1LfrnPWQRPf9pcxtbxUy9KlVfA83kZlff8TWY5D8WHQjjZ0Iu?= =?us-ascii?q?frymUrDbg8n/7e2u4ZqbO1wO32vkJ+0tZ0zt/E2R7pBQ2to6bP5pi1PgmThhQ6?= =?us-ascii?q?xu32RmJFaezV7Xx/yb29pdyRlWoO8r7MVaUK/3LOwSRL1cCyk6YShuvJW4/S/5?= =?us-ascii?q?YyDKo1EVXl4blAFJHwnb7Q3rFter6mqp/tZ6jRWbOcm+Gaw1XTD4qbxgSBblhi?= =?us-ascii?q?odHyIktW3QkNB1kaRX5h6s8U9R2YnRNZucMPQ7dKTQcd8XRmdbdtlcXWpND9Dv?= =?us-ascii?q?J7ATBvYMaL4L57L2oEED+EHmCA=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0G/AgC7m9VXhw4P49SERwEBAQEBuViCe?= =?us-ascii?q?xeHcQQCAQIBAQIQAQEBHgmCegQDGM4i61Q?= X-IPAS-Result: =?us-ascii?q?A0G/AgC7m9VXhw4P49SERwEBAQEBuViCexeHcQQCAQIBAQI?= =?us-ascii?q?QAQEBHgmCegQDGM4i61Q?= X-IronPort-AV: E=Sophos;i="5.30,318,1470693600"; d="pdf'?rar'52?scan'52,208,217,52";a="158717687" Received: from mout.web.de ([212.227.15.14]) by esa4.itmc.tu-dortmund.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Sep 2016 20:01:21 +0200 Received: from [85.22.85.17] by 3capp-webde-bs64.server.lan (via HTTP); Sun, 11 Sep 2016 20:01:21 +0200 MIME-Version: 1.0 Message-ID: From: anonymized To: Till Subject: Ausdrucke Content-Type: multipart/mixed; boundary=rekcebs-7e59eea0-b75e-4746-893a-09eff6b08356 Date: Sun, 11 Sep 2016 20:01:21 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:eV0YsKLQFHFmkiHWW93ornkAYSqnMamggnrwh7RG9AV 1AZBhd8tyXAhMKH4T667OUyW/OoE+lBR4YRr/2+81ifm20ABQN FY/VnRZNpd7H2plx4/gm4PeAH3fFtvBR+KkeXTer/lgatPL2NI tANpAi87QSNCdjlbD1If3MZod0z0LI7cfSMRX3uN0eFk5U1xsD WaDTF74Pw/DjctgQrAK7PYsPU29ZELnCyGuyJCNCa/k29GmaSZ eSt7RybdE0fQPtwXCjSpunY/aAKfzlBm3WriR4d8J2EuiF5lEf Ckux0Q= X-UI-Out-Filterresults: notjunk:1;V01:K0:DCd7m6feAFo=:1naEPQauOMJQdJCN/xGmMg c1Xt+69XHV7bvPDGhkDofNxzn5bAQp7uI3LBTrZHt7cUc88O9XSaa+VidtLW+r1DSne9hjdsb YjZenuM9XfN9/iLf/4/i6OVri0xF/N7xTT3jV6RFq4WAsxANVJp2fkq5VcJ3GvWJ3Fb0hOHh8 D08BhFwRdKSe57fq8dX5bFumcmPL9ES7VAVqJpnjhwCG9FFN1dDxUPRHRq/YT2vZ1u6CjJWRp fIksvfkEtGS5Imzc6r/cI8kKxGbBoX6o2F6nENwEv/99bEhyNukZAdDANb9K4lM3wbMYKuqDy s+8qmAkBa+ia9tf53w1JthfTNm7jDS/dWz8zY1XWckQU1M3/DL9le8ZwGSeM8TtkFMlIetyhR 4Sxh3dxOnMQumUvomqy3ILypayF/m7KiEJG7BvGdXqlqPWGDBPbpMqb9NW3rj --rekcebs-7e59eea0-b75e-4746-893a-09eff6b08356 Content-Type: text/html; charset=UTF-8 Hi Till, anonymized --rekcebs-7e59eea0-b75e-4746-893a-09eff6b08356 Content-Type: application/force-download Content-Disposition: attachment; filename=Ausdrucke.rar Content-Transfer-Encoding: base64 UmFyIRoHAM+QcwAADQApsXQgkFAABHABALGXAQACExemwl23KkkdMysAIEF1c2Ry anonymized EEF1c2RydWNrZQDwqklLxD17AEAHAA== --rekcebs-7e59eea0-b75e-4746-893a-09eff6b08356-- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331801] Forward mail with attachment doubles size of mail
https://bugs.kde.org/show_bug.cgi?id=331801 Till Schäferchanged: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de Version|4.11.5 |4.14.10 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 340204] Korganizers 5.3.1 reminder is up to one minute late
https://bugs.kde.org/show_bug.cgi?id=340204 Till Schäferchanged: What|Removed |Added Version|unspecified |GIT (master) Summary|Korganizers 4.14.2 reminder |Korganizers 5.3.1 reminder |is up to one minute late|is up to one minute late --- Comment #1 from Till Schäfer --- still valid for version 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #31 from Till Schäfer--- (In reply to unknown32768 from comment #29) > I even tried the patch, but must have done > something wrong because then it wouldn't save my configuration changes; The patch of commend 9 is doing the job as a workaround for me. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 Till Schäferchanged: What|Removed |Added Version|2.9.9 |3.0.2 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)
https://bugs.kde.org/show_bug.cgi?id=297079 --- Comment #13 from Till Schäfer--- my fault with the okular example. If i select "open with -> other" and just type in "okular" it does not work, but if I select the desktop entry from the applications list it works. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)
https://bugs.kde.org/show_bug.cgi?id=297079 --- Comment #11 from Till Schäfer--- (In reply to Alex Bikadorov from comment #10) > Heck! Everything I tested (Okular, Gwenview, Clementine, ...) works just > fine. > > @Till > What is the program you have problems with? if have tried it with okular, kate and above described custom shell script -> so at least here it is independent of the type of application. > > @Davide > what do we do (as fallback)?: > 1. classic approach, one instance for each argument: ; > > 2. do not care if the application can't handle multiple files: > > > A shell script is an example where we can't know if its supports multiple > files or not, but we should expect it, so I prefer (2) i also prefer (2) in most cases. However, may (2) cause trouble for some applications in addition to just not opening the file correctly? I.e. if a second parameter is an output file? Though, I cannot find an example of such a case. Do you know what Dolphin is doing? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)
https://bugs.kde.org/show_bug.cgi?id=297079 --- Comment #8 from Till Schäfer--- I just created a simple script to write out the parameters and here is what the application receives regarding the parameter list with the current git version. I thought that the parameters might not be grouped correctly, but it seems that nothing at all is received by the application: Single File: 0: /home/till/temp/bla.sh 1: /home/till/temp/IMG_20160908_191124.jpg Multiple Files 0: /home/till/temp/bla.sh -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)
https://bugs.kde.org/show_bug.cgi?id=297079 --- Comment #7 from Till Schäfer--- it does not open any file anymore. Before: selection of multiple files caused only a single file to open. Now: Application is opened with no file. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)
https://bugs.kde.org/show_bug.cgi?id=297079 Till Schäferchanged: What|Removed |Added Version|2.4.0-beta3 "Single Step" |Git --- Comment #5 from Till Schäfer --- still valid for KF5 git version from today -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäferchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 Till Schäferchanged: What|Removed |Added Version|5.6.3 |5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362051] panel appears on the wrong screen/display after reboot
https://bugs.kde.org/show_bug.cgi?id=362051 --- Comment #4 from Till Schäfer--- for me this issue was resolved after upgrading form nvidia-drivers 361.28 to 367.44. With 361.28 it is nearly always reproducible. With 367.44 is have not seen it once after several reboots. i have currently installed the following other components: - frameworks 5.26 - qt 5.6.1 - plasma 5.7.5 - xorg 1.18.4 @Daniel Lichtenberger: are you using nvidia-driverss, too? If so, can you reproduce confirm the fix? In this case i would close the bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357527] Please update the bug tracker to current versions of Akonadi
https://bugs.kde.org/show_bug.cgi?id=357527 Till Schäferchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Till Schäferchanged: What|Removed |Added Version|16.04 |16.08 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362420] DAV Resource 16.08.0: Segfaults randomly
https://bugs.kde.org/show_bug.cgi?id=362420 Till Schäferchanged: What|Removed |Added Version|unspecified |16.08 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=335654 --- Comment #9 from Till Schäfer--- frameworks kio: https://phabricator.kde.org/T3747 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365199] plasma-pa OSD show speaker with different size if muted.
https://bugs.kde.org/show_bug.cgi?id=365199 Till Schäferchanged: What|Removed |Added Version|5.7.0 |5.7.5 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363024] Kontact 16.08.1: New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäferchanged: What|Removed |Added Summary|Kontact 16.04.0: New|Kontact 16.08.1: New |contact editor misses |contact editor misses |options to display messages |options to display messages |in HTML |in HTML -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363027] KMail2 5.3.1: Per folder HTML settings are not working
https://bugs.kde.org/show_bug.cgi?id=363027 Till Schäferchanged: What|Removed |Added Summary|KMail 16.04.0: Per folder |KMail2 5.3.1: Per folder |HTML settings are not |HTML settings are not |working |working Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #7 from Till Schäfer --- i have to re-open this as the per-folder settings again have no effect in kmail2 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 363024] Kontact 16.04.0: New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäferchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Till Schäfer --- confirmed by Laurent Montel in Bug 363027 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #26 from Till Schäfer--- i have re-triggered the bug by the following actions: * open Find Message * entering a search critera and press search * a message window popped up telling me that the folder is not completely index * i have pressed re-index folder after this, akonadi keeps crashing again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 337551] Filtering mails does not work
https://bugs.kde.org/show_bug.cgi?id=337551 Till Schäferchanged: What|Removed |Added Ever confirmed|0 |1 Version|4.13.2 |5.2.1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Till Schäfer --- still valid for 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 346212] Kontact/KMail-5.3.1 ignores per contact settings about html and external resources synced over dav resource
https://bugs.kde.org/show_bug.cgi?id=346212 Till Schäferchanged: What|Removed |Added Summary|Kontact/KMail-4.14.6|Kontact/KMail-5.3.1 ignores |ignores per contact |per contact settings about |settings about html and |html and external resources |external resources synced |synced over dav resource |over dav resource | --- Comment #1 from Till Schäfer --- still valid for 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 329961] PGP silently fails to encrypt mails for users with different encryption protocols (pgp/mime vs inline pgp)
https://bugs.kde.org/show_bug.cgi?id=329961 Till Schäferchanged: What|Removed |Added Version|4.12|5.2.1 --- Comment #2 from Till Schäfer --- still valid for 5.3.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313667] Kmail2 5.3.1: sent e-mail missing in 'Sent' folder after restoring unsaved composer content
https://bugs.kde.org/show_bug.cgi?id=313667 Till Schäferchanged: What|Removed |Added Summary|sent e-mail missing in |Kmail2 5.3.1: sent e-mail |'Sent' folder |missing in 'Sent' folder ||after restoring unsaved ||composer content -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 329964] Kmail2 5.3.1 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäferchanged: What|Removed |Added Version|5.2.1 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 329964] Kmail2 5.3.1 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäferchanged: What|Removed |Added Version|5.1.3 |5.2.1 Summary|Kmail2 does not show the|Kmail2 5.3.1 does not show |encryption symbol in|the encryption symbol in |message list for inline pgp |message list for inline pgp |mails |mails -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 368808] New: No Notification Settings for Plasma 5 based Klipper
https://bugs.kde.org/show_bug.cgi?id=368808 Bug ID: 368808 Summary: No Notification Settings for Plasma 5 based Klipper Product: klipper Version: 5.7.5 Platform: Gentoo Packages OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: till2.schae...@uni-dortmund.de In KDE4 Klipper showed a message when changing the clipboard by shortcut (e.g. next history item). It would be nice to re-add this feature to the Plasma 5 based Klipper as there is currently no feedback about the active klipper content. One need to remember exactly the number of steps/copy actions to get an old clipper entry. The notification settings should be configurable to adjust them to the individual needs (some people may not like the pop ups) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 316667] The klipper notifications since kde-4.10 are visually cut off
https://bugs.kde.org/show_bug.cgi?id=316667 Till Schäferchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Till Schäfer --- there are not clipper notification anymore in KDE 5 -> closing as wontfix -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 355426] KF5 based KDEPIM/Akonadi 16.04.02 - tags are duplicated on each tag editing
https://bugs.kde.org/show_bug.cgi?id=355426 Till Schäferchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Till Schäfer --- *** This bug has been marked as a duplicate of bug 357236 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 357236] Kontact 15.12.0: Categories are multiplied on using them for tasks or events
https://bugs.kde.org/show_bug.cgi?id=357236 --- Comment #5 from Till Schäfer--- *** Bug 355426 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #25 from Till Schäfer--- i got rid of the crashing by dumping my mysql database and let akonadi create a new one -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Till Schäferchanged: What|Removed |Added Summary|akonadi server 16.04.2: |akonadi server 16.08.1: |crashing every few seconds |crashing every few seconds -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362575] Cannot unsubscribe IMAP folder
https://bugs.kde.org/show_bug.cgi?id=362575 Till Schäferchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||till2.schaefer@uni-dortmund ||.de Version|5.1.3 |5.2.1 Ever confirmed|0 |1 --- Comment #1 from Till Schäfer --- i can confirm this bug. It is still present in version 5.3.0. The missing change is directly visible in the local description dialog. After unchecking some items, clicking ok, and re-opening the dialog, all unchecked items are checked again and the folder are never hidden. When turning on all debug output, i receive the message whenever i open the dialog: log_akonadicore: Connected to "Akonadi" , using protocol version 53 log_akonadicore: Server says: "Not Really IMAP server" -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=335654 Till Schäferchanged: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #8 from Till Schäfer --- (In reply to Denis Kurz from comment #7) > List of products: > * Akonadi > * akregator > * kdepim > * kmail2 > * kontact > * korgac > * korganizer > > List of versions > * 5.1 > * 5.1.1 > * 5.1.2 > * 5.1.3 > * 5.2.0 > * 5.2.1 > * 5.2.2 > * 5.2.3 > * 5.3.0 > * 5.3.1 > Their versioning seems to be mixed. The repository tags do align with the applications version scheme, e.g. https://quickgit.kde.org/?p=akonadi.git However, akonadictl -v gives me the 5.x.y scheme. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #24 from Till Schäfer--- still valid for 16.08.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362420] DAV Resource 16.08.0: Segfaults randomly
https://bugs.kde.org/show_bug.cgi?id=362420 Till Schäferchanged: What|Removed |Added Summary|DAV Resource 16.04.0: |DAV Resource 16.08.0: |Segfaults randomly |Segfaults randomly Version|16.04 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362420] DAV Resource 16.04.0: Segfaults randomly
https://bugs.kde.org/show_bug.cgi?id=362420 --- Comment #1 from Till Schäfer--- the bug is still valid on 16.08.0 (Frameworks 5.25), although the stack trace changed slightly: Application: akonadi_davgroupware_resource (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57b9ca37c0 (LWP 4953))] Thread 1 (Thread 0x7f57b9ca37c0 (LWP 4953)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/bits/atomic_base.h:500 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:96 #8 QBasicAtomicInteger::load (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:116 #9 QtPrivate::RefCount::isShared (this=) at /usr/include/qt5/QtCore/qrefcount.h:95 #10 QMap ::detach (this=) at /usr/include/qt5/QtCore/qmap.h:360 #11 QMap ::operator[] (akey=..., this=) at /usr/include/qt5/QtCore/qmap.h:658 #12 EtagCache::setEtag (this=this@entry=0x0, remoteId=..., etag=...) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/common/etagcache.cpp:38 #13 0x0045569d in DavGroupwareResource::onItemFetched (this=0x1a7abc0, job=, updateType=DavGroupwareResource::ItemUpdateAdd) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/resource/davgroupwareresource.cpp:959 #14 0x7f57d55ef882 in QtPrivate::QSlotObjectBase::call (a=0x7fff13f158e0, r=0x1a7abc0, this=0x1c82ad0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #15 QMetaObject::activate (sender=sender@entry=0x1cacf60, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f158e0) at kernel/qobject.cpp:3715 #16 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1cacf60, m=m@entry=0x7f57d6cee2e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f158e0) at kernel/qobject.cpp:3595 #17 0x7f57d6a98682 in KJob::result (this=this@entry=0x1cacf60, _t1=_t1@entry=0x1cacf60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0_build/src/lib/moc_kjob.cpp:568 #18 0x7f57d6a99da1 in KJob::finishJob (this=this@entry=0x1cacf60, emitResult=emitResult@entry=true) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:109 #19 0x7f57d6a99e2a in KJob::emitResult (this=this@entry=0x1cacf60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:293 #20 0x00421bf9 in DavItemFetchJob::davJobFinished (this=0x1cacf60, job=) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/common/davitemfetchjob.cpp:92 #21 0x7f57d55ef882 in QtPrivate::QSlotObjectBase::call (a=0x7fff13f15b50, r=0x1cacf60, this=0x1d06670) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #22 QMetaObject::activate (sender=sender@entry=0x1ca8a60, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f15b50) at kernel/qobject.cpp:3715 #23 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1ca8a60, m=m@entry=0x7f57d6cee2e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f15b50) at kernel/qobject.cpp:3595 #24 0x7f57d6a98682 in KJob::result (this=this@entry=0x1ca8a60, _t1=_t1@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0_build/src/lib/moc_kjob.cpp:568 #25 0x7f57d6a99da1 in KJob::finishJob (this=this@entry=0x1ca8a60, emitResult=emitResult@entry=true) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:109 #26 0x7f57d6a99e2a in KJob::emitResult (this=this@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:293 #27 0x7f57d7ebc7e2 in KIO::SimpleJob::slotFinished (this=this@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0/src/core/simplejob.cpp:230 #28 0x7f57d7ec5b86 in KIO::TransferJob::slotFinished (this=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0/src/core/transferjob.cpp:166 #29 0x7f57d7ec5311 in KIO::TransferJob::qt_static_metacall (_o=, _c=, _id=, _a=) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0_build/src/core/moc_transferjob.cpp:155 #30 0x7f57d55ef21c in QMetaObject::activate (sender=sender@entry=0x1a7b1f0, signalOffset=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3730 #31 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1a7b1f0, m=m@entry=0x7f57d8164180 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3595 #32 0x7f57d7e9df13 in
[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.
https://bugs.kde.org/show_bug.cgi?id=355441 Till Schäferchanged: What|Removed |Added Version|5.22.0 |5.24.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.
https://bugs.kde.org/show_bug.cgi?id=355441 --- Comment #14 from Till Schäfer--- ok, mod rewrite was my fault. It works with the following rule from Bug 362885 (which is a duplicate of this bug) RewriteEngine On RewriteRule ^(.*\.[iv]cs)/$ $1 [L,PT] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365618] system tray entries does not get removed after disabling them
https://bugs.kde.org/show_bug.cgi?id=365618 Till Schäferchanged: What|Removed |Added Version|5.7.1 |5.7.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365618] system tray entries does not get removed after disabling them while the widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365618 Till Schäferchanged: What|Removed |Added Summary|system tray entries does|system tray entries does |not get removed after |not get removed after |disabling them |disabling them while the ||widgets are locked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365618] system tray entries does not get removed after disabling them
https://bugs.kde.org/show_bug.cgi?id=365618 --- Comment #2 from Till Schäfer--- you are right: the condition to trigger this bug is that the widgets are locked Nevertheless the behavior is not consistent in several ways: - it is possible to add a new entry, while the widgets are locked, but it is not possible to remove the entry afterwards - the configuration dialog is not aware of the widget locking, i.e. it allows a modification while the widgets are locked. - usually, the locking only affects the widgets placement and not the widgets configuration (e.g. the folder view still allows the configuration of the folder path, etc) => I still think it should be fixed in the way, that the entry gets removed, even in the locked stat -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352645] kOrganizer 15.08.1-pre: Multiple issues with categories cause a huge mess and make using categories basically impossible
https://bugs.kde.org/show_bug.cgi?id=352645 --- Comment #17 from Till Schäfer--- https://phabricator.kde.org/D2423 https://phabricator.kde.org/D2433 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 333754] KOrganizer does not retain custom category colors
https://bugs.kde.org/show_bug.cgi?id=333754 --- Comment #55 from Till Schäfer--- https://phabricator.kde.org/D2434 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357670] KMail 16.04.1: Composer auto-completion fails on first try
https://bugs.kde.org/show_bug.cgi?id=357670 --- Comment #11 from Till Schäfer--- (In reply to andreas.sturmlechner from comment #10) > Good news from my system at least - since upgrading to 16.07.80 I could not > see the problem anymore. woohoo. same here, 16.07.80 fixed it for me.. @kdepim-team: did you change anything intentionally or are we hit by luck that some "race condition" does not occur anymore? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361092] Kontact-15.12.3 crashes while filling a BCC address in the composer
https://bugs.kde.org/show_bug.cgi?id=361092 --- Comment #2 from Till Schäfer--- I have not seen the bug for a longer period. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.
https://bugs.kde.org/show_bug.cgi?id=355441 --- Comment #13 from Till Schäfer--- -> also the mod_rewrite trick did not help me: I do not get a broken state anymore, but whenever i delete an item, the deletion will silently fail on the server side and after this fail there is no more synchronization going on at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 --- Comment #8 from Till Schäfer--- as shown in Bug 366360 this also happens, if you have a lot of folders in kmail and receive an e-mail in each of them. An unmentioned problem with this behavior is, that the close button is out of the screen, which is problematic for permanent messages. In this case one can only re-login to get rid of the notification. -> I would like to see a scrollable message popup in this case with limited message height. A sane maximum message height should also be smaller than the complete screen height, as it blocks other work flows until the message disappears (maybe 1/3 of the screen height or something similar) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366360] Notifications popup is so large it cannot be closed
https://bugs.kde.org/show_bug.cgi?id=366360 --- Comment #6 from Till Schäfer--- i will test this in a few hours (i am currently updating to 5.7.3 anyway an will apply the path during that upgrade) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 --- Comment #7 from Till Schäfer--- *** Bug 366360 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366360] Notifications popup is so large it cannot be closed
https://bugs.kde.org/show_bug.cgi?id=366360 Till Schäferchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #4 from Till Schäfer --- ups, i just saw that the proposed solution is also generic in the other bug.. sorry for the noise *** This bug has been marked as a duplicate of bug 361389 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366360] Notifications popup is so large it cannot be closed
https://bugs.kde.org/show_bug.cgi?id=366360 Till Schäferchanged: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #3 from Till Schäfer --- Isn't this bug more generic? I think the notification framework should take care of such situations and it should not rely on sane implementations of each individual application. The application developer might also not be able to know the screen resolution and the size and visual representation settings (e.g. font size) for the notification area -> i.e. the amount of information, which can be presented at a single message. => I would like to see a scrollable message window in this case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365621] search field in holiday calendar settings is not working
https://bugs.kde.org/show_bug.cgi?id=365621 Till Schäferchanged: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Till Schäfer --- with plasma 5.7.3 it seems to do search, but the search is case sensitive, which is suboptimal. (e.g. "Germany", but not "germany" will find the "de_de" entry). Furthermore it does not search for region codes, but only for names. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366360] Notifications popup is so large it cannot be closed
https://bugs.kde.org/show_bug.cgi?id=366360 --- Comment #1 from Till Schäfer--- Created attachment 100421 --> https://bugs.kde.org/attachment.cgi?id=100421=edit screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366360] New: Notifications popup is so large it cannot be closed
https://bugs.kde.org/show_bug.cgi?id=366360 Bug ID: 366360 Summary: Notifications popup is so large it cannot be closed Product: plasmashell Version: 5.7.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: till2.schae...@uni-dortmund.de CC: plasma-b...@kde.org Notification Popups can be larger than the screen. In this case the close button is out of the screen (and clickable) are. If the notification is scheduled to stay. There is no way to get rid of the notification, than re-logging in. I have attached an example screenshot with a popup message from kmail. Solution: If the notification is to large, it should add a scroll pane or something similar. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #16 from Till Schäfer--- by why does a mysql schema drop/create helps in this case? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 355426] KF5 based KDEPIM/Akonadi 16.04.02 - tags are duplicated on each tag editing
https://bugs.kde.org/show_bug.cgi?id=355426 Till Schäferchanged: What|Removed |Added Summary|KF5 based KDEPIM/Akonadi|KF5 based KDEPIM/Akonadi |15.12.03 - tags are |16.04.02 - tags are |duplicated on each tag |duplicated on each tag |editing |editing Version|unspecified |16.04 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 365210] Krusader (Git 2016-07-07): krusader tries to browse simple gzip files as archive
https://bugs.kde.org/show_bug.cgi?id=365210 --- Comment #2 from Till Schäfer--- hmm you are right, krarc:/path/to/file.ext.gz works as expected. I see two ways to handle this situation: Solution 1: Even if katepart can transparently view/edit gziped files: handle them as single file archives, because there exist other applications which cannot handle gziped files transparently. Furthermore, the shortcuts to view or edit a gzip file still work directly on the gzip file. It is therefore easy to edit the files directly with katepart (and only katepart / other applications which can handle gzip transparently are cut of). Solution 2: Alternatively, we must differentiate between the associated applications of the second order extension and mime type, e.g. .txt.gzip (text/plain; charset=us-ascii compressed-encoding=application/x-gzip; charset=binary) would open directly with kate and .mp3.gzip (audio/mpeg; charset=binary compressed-encoding=application/x-gzip; charset=binary) would trigger the krarc browsing as my associated player does not handle gzip files transparently. I do not know if there is an easy way to know if an application can handle gzip transparently. It might therefore be troublesome to implement this feature (but still: it would be pretty cool :-) ). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 365210] New: Krusader (Git 2016-07-07): krusader tries to browse simple gzip files as archive
https://bugs.kde.org/show_bug.cgi?id=365210 Bug ID: 365210 Summary: Krusader (Git 2016-07-07): krusader tries to browse simple gzip files as archive Product: krusader Version: Git Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: krarc Assignee: m...@fork.pl Reporter: till2.schae...@uni-dortmund.de Whenever i double click a gzip file (no gziped tar), i get the error: Error: Protocoll not supported by Krusader gzip:/path/to/file.ext.gz seems that the option to browse archives as folders introduced by this [1] commit tries to handle gziped files as archives. >From a user perspective, theses gziped files should be handled such as single file archive files. [1] https://quickgit.kde.org/?p=krusader.git=commit=d1459aebf7447709feae136848d33e070041118a Reproducible: Always Software used: Krusader git: commit d1459aebf7447709feae136848d33e070041118a kde-frameworks: 5.23 plasma: 5.7.0 qt: 5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365199] New: plasma-pa OSD show speaker with different size if muted.
https://bugs.kde.org/show_bug.cgi?id=365199 Bug ID: 365199 Summary: plasma-pa OSD show speaker with different size if muted. Product: plasma-pa Version: 5.7.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: till2.schae...@uni-dortmund.de CC: plasma-b...@kde.org The OSD of plasma-pa shows volume changes. If the device gets into muted state the volume indicator bar (on the bottom) gets replaced with a label "Audio Muted". This label seems to cause a resize of the OSD symbol on the top. The speaker symbol for the muted state is smaller that the speaker symbol in unmuted state. See the attached screencast for an example. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365199] plasma-pa OSD show speaker with different size if muted.
https://bugs.kde.org/show_bug.cgi?id=365199 --- Comment #1 from Till Schäfer--- Created attachment 99924 --> https://bugs.kde.org/attachment.cgi?id=99924=edit plasma pa volume change screencast -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365197] New: add a notification settings for volume change events
https://bugs.kde.org/show_bug.cgi?id=365197 Bug ID: 365197 Summary: add a notification settings for volume change events Product: plasma-pa Version: 5.7.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: till2.schae...@uni-dortmund.de CC: plasma-b...@kde.org KMix plays a sound and shows an OSD whenever the volume changes by "volume up/down". In contrast, plasma-pa only shows the OSD, but plays no sound. The sound is helpful to get a feedback about the actual loudness of the sound device (its sometimes hard to guess how loud X% might be), especially if one wants to configure the volume before (and not while) playing some media. As there are also peplle which may prefer a silent volume change, I would like to propose that plasma-pa adds a volume change notification event that can be configured individually. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 355437] no notification settings for kmix-4.6rc1 (kde apps 12.08.3) volume popup (changing volume)
https://bugs.kde.org/show_bug.cgi?id=355437 Till Schäferchanged: What|Removed |Added Summary|no notification settings|no notification settings |for kmix-4.6rc1 (kde apps |for kmix-4.6rc1 (kde apps |18.08.3) volume popup |12.08.3) volume popup |(changing volume) |(changing volume) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Till Schäferchanged: What|Removed |Added Summary|akonadi server 16.04.1: |akonadi server 16.04.2: |crashing every few seconds |crashing every few seconds -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357670] KMail 16.04.1: Composer auto-completion fails on first try
https://bugs.kde.org/show_bug.cgi?id=357670 Till Schäferchanged: What|Removed |Added Summary|KMail 16.04.0: Composer |KMail 16.04.1: Composer |auto-completion fails on|auto-completion fails on |first try |first try -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357670] KMail 16.04.0: Composer auto-completion fails on first try
https://bugs.kde.org/show_bug.cgi?id=357670 --- Comment #9 from Till Schäfer--- (In reply to andreas.sturmlechner from comment #8) > Upgraded to Qt-5.6.1 and the issue is still present. I made another > observation though: > > - Indeed "To:" field works fine > - "CC:" does show same behaviour as described in my above comment > - However "CC:" works fine if _at first_ you were using "To:", which is > often not happening when you reply to someone and put people into CC. I am also on qt 5.6.1, but i am still facing the problem, regardless of the field type (to, cc). However, i have also notices some very rare (looks random to me) cases, where the completion did work. Frameworks: 5.22 kde-apps 16.04.1 plasma 5.6.4 -- You are receiving this mail because: You are watching all bug changes.